11
votes
Accepted
What does Bitcoin Core use port 8334 for?
It is used for incoming Tor connections.
See here and here for more info.
You can use -bind=127.0.0.1:XXXX=onion to use port XXXX instead.
- 11.9k
6
votes
Allowing Incoming Connection on Bitcoin Core
I had the same problem. The port was open, but the test at bitnodes.21.co would fail. However after my Bitcoin client downloaded the entire BlockChain everything worked. I used about 144 hours to ...
- 61
6
votes
Accepted
What is the benefit of opening port 8333 to a client?
If you don't want to, you don't have to open ports at all. You'll still have a full node, it will just have fewer connections. Full nodes usually make 8 outgoing connections and can have many more ...
- 6,344
5
votes
Accepted
How to change RPC port for bitcoind? (rpcport=xxx in bitcoin.conf doesn't work)
Found the solution: rpcport needs to be in the [test] section
Please update your original config file to read:
testnet=1
server=1
daemon=1
txindex=1
rpcuser=XXXXXXXXXXXXXXXXXXXXXXX
rpcpassword=...
- 672
3
votes
Port Forwarding for Bitcoin Core in order to allow incoming connections?
External host is the IP of the host connecting to you. If you want to allow anyone to connect, you can just put 0.0.0.0.
- 8,946
2
votes
Accepted
Does port 8333 need to be opened as TCP_OUT or TCP_IN?
Port 8333 is only relevant for inbound connections. Opening it allows other nodes to start talking with your node.
That said, a Bitcoin node can fully participate in the network even if you don't ...
- 892
2
votes
How does the Bitcoin p2p network work? Does it need port forwarding?
Nodes that participate in the Bitcoin network run a computer program such as this one: https://github.com/bitcoin/bitcoin, which dictates how everything works.
To answer your more specific questions:
...
- 54
2
votes
Accepted
Access REST endpoint of Bitcoin-qt from another computer on the local network
The rest interface uses the RPC options for setup. You can use the -rpcbind option to bind the interface to a different address and port, and set the -rpcallowip. Note that this will also affect the ...
- 71.6k
2
votes
Accepted
Port 9735 for both MAINNET and TESTNET
I don't know what the design decisions were that led to this, or their rationale, but:
Particularly if you run a MAINNET node and a TESTNET node on the same machine, how would the host know which ...
- 108k
2
votes
confirm bitcoin node on bitnodes.io
Nord VPN does not support port forwarding: https://support.nordvpn.com/FAQ/1047408432/Do-you-offer-port-forwarding.htm
- 111
2
votes
Accepted
Do I have to open port 8333 for incoming connections?
No, you will not have any problems receiving, sending, or validating transactions.
The only difference is that all your connections willl be made by your node, from your node to others. There won't be ...
- 108k
1
vote
Accepted
For running a lightning node and getting maximum exposure, should I forward port 8333 also (for bitcoin)? Or only 9735 (lightning)?
Maybe some lightning implementations scan for bitcoin nodes and then look for lightning capability on top?
I'm not aware of any Lightning implementations that do this. The Lightning P2P network is a ...
- 15.7k
1
vote
I am trying to get past Binding RPC on address 1 port 8332 failed
Whenever a service has failed to bind to a high numbered port I have always found it was because another application was already bound to that port. I have always discovered the culprit using netstat -...
- 28k
1
vote
Using BTCPay Server along with a web server in a single machine
No, you can't specify port numbers in DNS records.
It must be the reverse proxy which listens on ports 80 and 443 (not BTCPay Server). The reverse proxy should pass traffic to BTCPay Server or your ...
- 309
1
vote
Port 8333 closed, fwd on Router OK, firewall port open, full-node not reachable
First, check your router opens that port too and redirects that port to you computer.
Then check CGNAT. If the external IP address your router shows isn't the same as you find when you search for "...
- 10.2k
1
vote
Accepted
Change port 8333 to other. (Running multiple docker instances)
Yes you can and the node will still sync and push transaction data.
Most of the nodes are behind NAT and not reachable anyway from the internet.
These nodes are initiating connection against random ...
- 528
1
vote
Accepted
The result of bitcoin-cli getpeerinfo command
so, I checked my router whether the port number(48302, 44660) is opened or not but, no any port is currently open.
They don't appear open because those ports are not always open listening for ...
- 71.6k
1
vote
How to change RPC port for bitcoind? (rpcport=xxx in bitcoin.conf doesn't work)
It looks like a bug: I've also replicated the same behaviour on my machine using the current version, Bitcoin Core Daemon version v0.17.99.0-g2945492424934fa360f86b116184ee8e34f19d0a freshly ...
- 672
1
vote
Port 8333 and Issues to have a connection
You are conflating the two ports that Bitcoin Core opens and uses.
There is the Bitcoin network port. That is port 8333 by default. You DO NOT want to try to connect to that as it is used for the ...
- 71.6k
1
vote
Allowing Incoming Connection on Bitcoin Core
I had the same problem after following all of the usual steps. I waited and it still didn't work. I had to change my computer's firewall (in the Inbound Rules) for the Bitcoin Core (highlighted one ...
- 143
Only top scored, non community-wiki answers of a minimum length are eligible