Bitcoin Forum
May 09, 2024, 04:33:22 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: troubles getting bitcoind to listen on an external ip .15BTC BOUNTY!  (Read 891 times)
joelnet (OP)
Newbie
*
Offline Offline

Activity: 49
Merit: 0


View Profile
March 12, 2014, 04:30:58 AM
Last edit: March 12, 2014, 10:13:57 AM by joelnet
 #1

0.15 BTC bounty for the first user that solves my problem!

OS:    Ubuntu 12.04.4 LTS (VPS)

I followed the directions here: https://en.bitcoin.it/wiki/Enabling_SSL_on_original_client_daemon

my bitcoin.config:

Code:
daemon=1
rpcuser=<rpcuser>
rpcpassword=<rpcpass>
rpcallow=<remote machine>
rpcport=11111
rpcssl=1

Though I'm not seeing bitcoin listening on any external interface.

Code:
~$ netstat -nap|grep bitcoind|grep LISTEN

tcp        0      0 0.0.0.0:9333            0.0.0.0:*               LISTEN      12323/bitcoind
tcp        0      0 127.0.0.1:11111         0.0.0.0:*               LISTEN      12323/bitcoind
tcp6       0      0 :::9333                 :::*                    LISTEN      12323/bitcoind
tcp6       0      0 ::1:11111               :::*                    LISTEN      12323/bitcoind


Do I need to add something to iptables?

Is there something I'm missing here?
1715272402
Hero Member
*
Offline Offline

Posts: 1715272402

View Profile Personal Message (Offline)

Ignore
1715272402
Reply with quote  #2

1715272402
Report to moderator
1715272402
Hero Member
*
Offline Offline

Posts: 1715272402

View Profile Personal Message (Offline)

Ignore
1715272402
Reply with quote  #2

1715272402
Report to moderator
"If you don't want people to know you're a scumbag then don't be a scumbag." -- margaritahuyan
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715272402
Hero Member
*
Offline Offline

Posts: 1715272402

View Profile Personal Message (Offline)

Ignore
1715272402
Reply with quote  #2

1715272402
Report to moderator
1715272402
Hero Member
*
Offline Offline

Posts: 1715272402

View Profile Personal Message (Offline)

Ignore
1715272402
Reply with quote  #2

1715272402
Report to moderator
1715272402
Hero Member
*
Offline Offline

Posts: 1715272402

View Profile Personal Message (Offline)

Ignore
1715272402
Reply with quote  #2

1715272402
Report to moderator
BookLover
Hero Member
*****
Offline Offline

Activity: 533
Merit: 500


^Bitcoin Library of Congress.


View Profile
March 12, 2014, 03:13:05 PM
 #2

Have you tried using the standard port? (8332)

joelnet (OP)
Newbie
*
Offline Offline

Activity: 49
Merit: 0


View Profile
March 12, 2014, 06:45:11 PM
 #3

Have you tried using the standard port? (8332)

I have.  Same results.  It binds to 127.0.0.1:8332 and does not bind to the external interface.
joelnet (OP)
Newbie
*
Offline Offline

Activity: 49
Merit: 0


View Profile
March 12, 2014, 06:56:58 PM
 #4

Okay I solved it!  I had

rpcallow=<remote machine>

when it should have been

rpcallowip=<remote machine>
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!