Title: Reach bitcoin server from outside Post by: Shevek on June 16, 2011, 10:00:56 PM 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. Title: Re: Reach bitcoin server from outside Post by: xlcus on June 16, 2011, 10:36:20 PM 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
Title: Re: Reach bitcoin server from outside Post by: Shevek on June 17, 2011, 06:00:54 AM 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. Title: Re: Reach bitcoin server from outside Post by: xlcus on June 18, 2011, 02:31:55 PM Ah sorry, I thought you were wanting to connect in to a command prompt to control your client.
Title: Re: Reach bitcoin server from outside Post by: InstaGx on June 20, 2011, 02:07:51 PM 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.
Title: Re: Reach bitcoin server from outside Post by: Shevek on June 20, 2011, 03:00:51 PM 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.
No. It's ok. Locally, I can "telnet" and "http" to localhost:8332 (with nonsense result, but it proves the daemon is listening).
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...
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! |