Can't accept incoming connections; I've tried everything. Help?

[somatic]

Here's what I've done so far:

• Forwarded post 8333 on my router to my mining server
• Opened the firewall on for bitcoin-qt (this happens right away when you install it anyway)
• Opened ports 8332 and 8333 in the windows firewall
• Opened ports 8332 and 8333 in windows services (by clicking the advanced tab in the firewall... dunno what it does but I tried it anyway)
• Added the line "port=8333" in bitcoin.conf

But I still only have 8 connections, all outgoing. I'm out of ideas. Any help would be greatly appreciated.

[grue]

have you checked using https://getaddr.bitnodes.io/ ?

[Bernard Lerring]

Have you edited "maxconnections=" in bitcoin.conf? Set it to 12 and you should have the first 8 as outgoing connections, with the last 4 as incoming.

[grue]

Have you edited "maxconnections=" in bitcoin.conf? Set it to 12 and you should have the first 8 as outgoing connections, with the last 4 as incoming.

default is 125, so that shouldn't be the problem.

[CryptInvest]

Maybe the problem in the firmware of the router? Try changing the router or firmware.

[Justin00]

Did you try turn off windows firewall ? I know you said you put an exemption in, but try turning it off.

btw how are you verifiying which direction the connections are ? using netstat ?

[spin]

My ISP had a default setting where they blocked (some) incoming connections to me.  I had to log into my account with them and disable this security "feature".  I guess it makes sense for 95% of their customers.  Your ISP might also be doing something like this.

[Justin00]

My parents ISP do the same thing and you have to opt-in to allow inbound services. Kind of annoying until you figure it out.
Seems pretty rare, but yeah good suggestion

My ISP had a default setting where they blocked (some) incoming connections to me.  I had to log into my account with them and disable this security "feature".  I guess it makes sense for 95% of their customers.  Your ISP might also be doing something like this.

[Bernard Lerring]

have you checked using https://getaddr.bitnodes.io/ ?

How do I find my own node on that site?

I know the 8333 bit, which I've got forwarded, but which IP do I use? Just the public IP that comes up when I google "what is my IP address"?

[somatic]

I feel really stupid, and thanks for the replies, but I think it's because I switched to a new coin with connections coming in on new ports. I will update if this is the case. Thanks, I don't usually get replies to my tech issues so I didn't check this thread for days 

[Bernard Lerring]

I still can't check the getaddr.bitnodes.io site with my public address:8333.

It comes up with address not connected. I know I've got outgoing connections because my ethernet monitor sometimes sends at 150Kb/s without anything running and I've got 12 connections.

Is there something wrong with that site?

[spin]

I still can't check the getaddr.bitnodes.io site with my public address:8333.

It comes up with address not connected. I know I've got outgoing connections because my ethernet monitor sometimes sends at 150Kb/s without anything running and I've got 12 connections.

Is there something wrong with that site?

Your node probably hasn't been connected long enough as you only have 12 connections.  Though, if you have more than 8 it means the network can see you. bitnodes.io will find you eventually but it's a random process.  If your IP address changes frequently (as the case for many when if they frequently reconnect to their DSL or whatever) you may not be found.  Also if your IP has changed while bitcoind was running, it continues to advertise the old IP and will be limited to 8.

[zvs]

I still can't check the getaddr.bitnodes.io site with my public address:8333.

It comes up with address not connected. I know I've got outgoing connections because my ethernet monitor sometimes sends at 150Kb/s without anything running and I've got 12 connections.

Is there something wrong with that site?

If it can't access your address, then it's not listed as a valid node..

i.e. it's full, nobody else can connect, including getaddr

ed: this  is with the assumption that you did what the fellow up above said to, and set to maxconnections 12. 

[Bernard Lerring]

Yeah, I've got maxconnections=12 set up in my .conf file to avoid hammering my upload bandwidth.

I'll check it again later when I'm home.

I suggest that upload throttling is included in 0.9.2.2.

[Bernard Lerring]

The website getaddr.bitnodes.io worked after a restart and only 8 connections! It must be currently connectable because my maxconnections=12 haven't been saturated yet, so the site can currently connect to me.



I'll try again in a bit when I've got 12 connections. Currently on 9. 

[Bernard Lerring]

Yup, now that my active connections are all used the website can't connect to me:



I understand how this works a little bit more now. 

[zvs]

if you're using windows 7, use netlimiter 

www.netlimiter.com


netlimiter 4 may still be free too, im not sure.  that works with windows 8