Bitcoin Forum
May 28, 2024, 12:25:53 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Port 8333 open, but not accepting connections  (Read 1172 times)
gt200 (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
April 19, 2016, 10:57:59 AM
Last edit: April 19, 2016, 11:18:16 AM by gt200
 #1

Bitcoin Core v0.12.1 64-bit, OS X 10.7.5

Steady 8 active (outbound) connections.

I used http://www.subnetonline.com/pages/network-tools/online-port-scanner.php to check that port 8333 is open (and port forwarded to the bitcoin workstation).

https://bitnodes.21.co *sometimes* says reachable, and sometimes unreachable, about a 50% chance of each.  (Huh?)

Debug window shows steady 8 outbound peers - when I hit Check Node at https://bitnodes.21.co I can sometimes see an inbound connection from e.g. 136.243.139.96 but it looks like my bitcoind is not responding.

Any advice warmly welcomed.

Should I post my IP here?

Thanks

Edit: this is the Debug Window during https://bitnodes.21.co "Check Node": http://s27.postimg.org/fyz95883n/Untitled.png
shorena
Copper Member
Legendary
*
Offline Offline

Activity: 1498
Merit: 1520


No I dont escrow anymore.


View Profile WWW
April 19, 2016, 12:22:27 PM
 #2

still syncing?

Im not really here, its just your imagination.
cr1776
Legendary
*
Offline Offline

Activity: 4046
Merit: 1303


View Profile
April 19, 2016, 12:41:07 PM
 #3

Is the Bitcoin node on a static ip locally?

It does look like it is still syncing from that screenshot.
gt200 (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
April 19, 2016, 02:38:58 PM
 #4

Thanks for the responses.

Yes, it is still syncing.

The IP is "reasonably" static Smiley  Dynamic, but hasn't changed for more than a week.

unholycactus
Legendary
*
Offline Offline

Activity: 1078
Merit: 1024



View Profile WWW
April 19, 2016, 03:04:32 PM
 #5

Thanks for the responses.

Yes, it is still syncing.

The IP is "reasonably" static Smiley  Dynamic, but hasn't changed for more than a week.



It's a very bad idea to post your IP in a public space.
You should wait till it finishes syncing before making sure it works.
shorena
Copper Member
Legendary
*
Offline Offline

Activity: 1498
Merit: 1520


No I dont escrow anymore.


View Profile WWW
April 19, 2016, 04:08:39 PM
 #6

-snip-
It's a very bad idea to post your IP in a public space.
You should wait till it finishes syncing before making sure it works.

All IPs are public, its the internet.

Thanks for the responses.

Yes, it is still syncing.
-snip-

Its normal that the number of connections is low during sync or even at first when your IP is not widely known by other nodes. It will grow over time, but dont expect too much from a dynamic IP (even though it only changes once a week/month).

Im not really here, its just your imagination.
cr1776
Legendary
*
Offline Offline

Activity: 4046
Merit: 1303


View Profile
April 19, 2016, 05:45:38 PM
Last edit: April 19, 2016, 08:47:25 PM by cr1776
 #7

Is the Bitcoin node on a static ip locally?

It does look like it is still syncing from that screenshot.
Thanks for the responses.

Yes, it is still syncing.

The IP is "reasonably" static Smiley  Dynamic, but hasn't changed for more than a week.


If your local IP changing every week, that could be one of the problems because if you are port forwarding to a local IP that is changing then the port forwarding/DMZ setting wouldn't be working if your local IP changes. You should probably set a static IP on the local network (turn off DHCP) and then port forward to that local static IP at the router.



gt200 (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
April 19, 2016, 10:36:42 PM
 #8

Thanks all, will be patient!  Cheers
shorena
Copper Member
Legendary
*
Offline Offline

Activity: 1498
Merit: 1520


No I dont escrow anymore.


View Profile WWW
April 21, 2016, 12:12:49 PM
 #9

Thanks all, will be patient!  Cheers

If you want, you can send me your IP via PM. I will try to connect with my home node and let you know if it worked.

Im not really here, its just your imagination.
gt200 (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
April 23, 2016, 01:02:59 AM
 #10

So 2 days later and it is still struggling to sync, but getting close.  404621 blocks now.

Meanwhile I don't understand why I have so many nodes connected which are sending, but not identifying themselves.  I'm receiving blocks, because the count is slowly increasing.  Sorry if this should be a separate question.

http://s31.postimg.org/ksh5bo0az/Untitled.png
gt200 (OP)
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
April 24, 2016, 12:30:55 AM
 #11

For anyone following my path Arne Saknussemm-style, patience is all.  Once the blockchain finished syncing (took about 8 days) now all inbound and outbound connections are working fine.  So maybe the core accepts connections, but doesn't respond to them, if the inbound height is greater.
shorena
Copper Member
Legendary
*
Offline Offline

Activity: 1498
Merit: 1520


No I dont escrow anymore.


View Profile WWW
April 24, 2016, 09:26:31 AM
 #12

For anyone following my path Arne Saknussemm-style, patience is all.  Once the blockchain finished syncing (took about 8 days) now all inbound and outbound connections are working fine.  So maybe the core accepts connections, but doesn't respond to them, if the inbound height is greater.

Great, still odd that it took so long. Probably best to turn the firewall back on now.

Im not really here, its just your imagination.
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!