Author

Topic: bitcoind not listening on port 8333 (Read 921 times)

hero member
Activity: 686
Merit: 502
July 05, 2016, 02:47:45 PM
#7
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
legendary
Activity: 1008
Merit: 1000
★YoBit.Net★ 350+ Coins Exchange & Dice
July 05, 2016, 02:01:33 PM
#6
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
hero member
Activity: 686
Merit: 502
July 04, 2016, 10:01:28 AM
#5
also make sure you haven't added the below to bitcoin.conf

Quote
rpcallowip=

this stopped it listening for me.
staff
Activity: 3458
Merit: 6793
Just writing some code
July 04, 2016, 09:34:30 AM
#4
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
sr. member
Activity: 338
Merit: 253
July 04, 2016, 07:46:04 AM
#3
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

copper member
Activity: 1498
Merit: 1528
No I dont escrow anymore.
July 04, 2016, 12:54:27 AM
#2
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.
sr. member
Activity: 338
Merit: 253
July 04, 2016, 12:18:46 AM
#1
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?
Jump to: