Reach bitcoin server from outside

[Shevek]

I want to know, how to configure my host computer (Debian) in which I run bitcoin, to be reached externally.

Actually,

Code:

$ telnet my.host.address 8332

is useless.

[xlcus]

Don't use telnet. It's unencrypted and your password is sent in plain text.  User SSH instead.  Open port 22 on your router/firewall and redirect it to your Debian box.  Then connect in using either SSH from a Unix box, or PuTTY from a Windows box

[Shevek]

Don't use telnet. It's unencrypted and your password is sent in plain text.  User SSH instead.  Open port 22 on your router/firewall and redirect it to your Debian box.  Then connect in using either SSH from a Unix box, or PuTTY from a Windows box

I use "telnet" as a simple way to test if bitcoin is alive from outside. I don't really want to manage bitcoin with "telnet". The goal is to use a real bitcoin client in the future.

[xlcus]

Ah sorry, I thought you were wanting to connect in to a command prompt to control your client.

[InstaGx]

I want to know, how to configure my host computer (Debian) in which I run bitcoin, to be reached externally.

Actually,

Code:

$ telnet my.host.address 8332

is useless.

As you didn't provide much information I'll just list all the possible errors in your method.

• Bitcoin isn't running as a server/daemon
• bitcoin.conf file uses whitelisting of IPs or is forbidding remote access
• You're using the wrong port when trying to connect (maybe try default port 8333?)
• You're trying to reach the server from outside the local network and haven't configured NAT and/or firewall exceptions in the router

[Shevek]

Thanks a lot for your feedback!

I want to know, how to configure my host computer (Debian) in which I run bitcoin, to be reached externally.

As you didn't provide much information I'll just list all the possible errors in your method.

• Bitcoin isn't running as a server/daemon
• You're using the wrong port when trying to connect (maybe try default port 8333?)

No. It's ok. Locally, I can "telnet" and "http" to localhost:8332 (with nonsense result, but it proves the daemon is listening).

• You're trying to reach the server from outside the local network and haven't configured NAT and/or firewall exceptions in the router

The server has public address, with no NAT device. Perhaps I should take a peek to "iptables", but I think ports over 1024 are visible by default...

• bitcoin.conf file uses whitelisting of IPs or is forbidding remote access

Only rcpuser and rcppassword are on bitcoin.conf.

But this is worth to investigate: the options in bitcoin.conf I'll quickly go to the wiki to dig out the matter.

Thanks again!