Port 8333 open, but not accepting connections

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: gt200 on April 23, 2016, 07:30:55 PM

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.

gt200

newbie

Activity: 5

Merit: 0

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.

gt200

newbie

Activity: 5

Merit: 0

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

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: gt200 on April 19, 2016, 05:36:42 PM

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.

gt200

newbie

Activity: 5

Merit: 0

Thanks all, will be patient! Cheers

cr1776

legendary

Activity: 4228

Merit: 1313

Quote from: gt200 on April 19, 2016, 09:38:58 AM

Quote from: cr1776 on April 19, 2016, 07:41:07 AM

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

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.

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: unholycactus on April 19, 2016, 10:04:32 AM

-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.

Quote from: gt200 on April 19, 2016, 09:38:58 AM

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).

unholycactus

legendary

Activity: 1078

Merit: 1024

Quote from: gt200 on April 19, 2016, 09:38:58 AM

Thanks for the responses.

Yes, it is still syncing.

The IP is "reasonably" static

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.

gt200

newbie

Activity: 5

Merit: 0

Thanks for the responses.

Yes, it is still syncing.

The IP is "reasonably" static

Dynamic, but hasn't changed for more than a week.

cr1776

legendary

Activity: 4228

Merit: 1313

Is the Bitcoin node on a static ip locally?

It does look like it is still syncing from that screenshot.

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

still syncing?

gt200

newbie

Activity: 5

Merit: 0

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

Topic: Port 8333 open, but not accepting connections (Read 1190 times)