bitcoind not listening on port 8333

[Blinken]

I installed bitcoind and it downloaded the whole blockchain and is fully synced, but is not listening for connections on port 8333, so it is not a full node. How do I make it accept inbound connections?

[shorena]

I installed bitcoind and it downloaded the whole blockchain and is fully synced, but is not listening for connections on port 8333, so it is not a full node. How do I make it accept inbound connections?

Its still a full node. Unless you set a proxy or use -conect its looking for inbound connections by default. Did you open the port on your firewall and forward it on your router (if needed). If you can rule out the firewall, make it explicitly list with -listen.

[Blinken]

Well, its not listening by default even though it says in the documentation it is supposed to.

Did this change in a recent version?

I started it as a daemon, ie:

bitcoind -daemon

[achow101]

Check your firewalls especially your router. UPNP (which allowed automatic firewall port forwarding) was disabled in recent versions due to a vulnerability in UPNP. Now you will have to manually forward port 8333

[icanscript]

also make sure you haven't added the below to bitcoin.conf

rpcallowip=

this stopped it listening for me.

[helloeverybody]

Im going to go for you needing to port forward that port. I ran my node for ages before realising i wasnt even actually getting connections when i checked to try and see my node. I simply port forwarded port 8333 and now i can see myself online. Rookie mistake =p

[icanscript]

Im going to go for you needing to port forward that port. I ran my node for ages before realising i wasnt even actually getting connections when i checked to try and see my node. I simply port forwarded port 8333 and now i can see myself online. Rookie mistake =p

you should be able to check by going to command prompt -> typing "netstat -a" if its listening on 8333 and and not connectable from outside the network then the above suggestion is correct