Bitcoin Forum
December 07, 2016, 08:12:12 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Reach bitcoin server from outside  (Read 1053 times)
Shevek
Sr. Member
****
Offline Offline

Activity: 252



View Profile
June 16, 2011, 10:00:56 PM
 #1

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.

Proposals for improving bitcoin are like asses: everybody has one
1SheveKuPHpzpLqSvPSavik9wnC51voBa
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481141532
Hero Member
*
Offline Offline

Posts: 1481141532

View Profile Personal Message (Offline)

Ignore
1481141532
Reply with quote  #2

1481141532
Report to moderator
1481141532
Hero Member
*
Offline Offline

Posts: 1481141532

View Profile Personal Message (Offline)

Ignore
1481141532
Reply with quote  #2

1481141532
Report to moderator
1481141532
Hero Member
*
Offline Offline

Posts: 1481141532

View Profile Personal Message (Offline)

Ignore
1481141532
Reply with quote  #2

1481141532
Report to moderator
xlcus
Hero Member
*****
Offline Offline

Activity: 518



View Profile
June 16, 2011, 10:36:20 PM
 #2

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

Faircoin, the coin of the fair economy
Check https://www.fair.coop The Earth cooperative to create a new economic system, based in global fairness
Shevek
Sr. Member
****
Offline Offline

Activity: 252



View Profile
June 17, 2011, 06:00:54 AM
 #3

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.

Proposals for improving bitcoin are like asses: everybody has one
1SheveKuPHpzpLqSvPSavik9wnC51voBa
xlcus
Hero Member
*****
Offline Offline

Activity: 518



View Profile
June 18, 2011, 02:31:55 PM
 #4

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

Faircoin, the coin of the fair economy
Check https://www.fair.coop The Earth cooperative to create a new economic system, based in global fairness
InstaGx
Member
**
Offline Offline

Activity: 70



View Profile
June 20, 2011, 02:07:51 PM
 #5

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

Buy High - Sell Low
Shevek
Sr. Member
****
Offline Offline

Activity: 252



View Profile
June 20, 2011, 03:00:51 PM
 #6

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!

Proposals for improving bitcoin are like asses: everybody has one
1SheveKuPHpzpLqSvPSavik9wnC51voBa
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!