Monero-gui: No incoming connections - check firewalls/routers allow port

Created on 29 Oct 2018  路  4Comments  路  Source: monero-project/monero-gui

OS: Windows 10
GUI version: Monero GUI v0.13.0.3

I have successfully synchronised daemon and wallet blocks are now syncing:
2018-10-29 4

However, while wallet blocks sync I am having the below notification when running Monero GUI:
2018-10-29 10:31:29.394 [P2P3] WARN global src/p2p/net_node.inl:1338 No incoming connections - check firewalls/routers allow port 18080

Screenshot:
2018-10-29 1

I am using Windows Defender and I have allowed the port as requested (18080) - and whitelisted Monero GUI.

Screenshot (Port):
2018-10-29 2

Screenshot (Whitelist):
2018-10-29 3

Thanks for any advice, which would be greatly appreciated.

Most helpful comment

Opening port 18080 allows incoming P2P connections. Like @dEBRUYNE-1 mentioned; your daemon works fine without port forwarding. Personally I sometimes get this error - I ignore it.

As for actually configuring your router to forward port 18080 to the machine on your local network; try to find some guides and/or your router's manual concerning port forwarding. In addition: Windows can block these requests so make sure the Windows firewall allows such connections (TCP and UDP).

From the screenshot you posted I can give some insight:

Service: other
External host: (leave empty if you can)
External port: 18080
Internal host: (the IP address of your machine on your local network; it will start with 192.168.1...
Internal port: 18080

Protocol should probably be UDP (?) but if you can, choose 'Both' from the dropdown menu. print_cn will help you verify your incoming connections are working.

All 4 comments

First note that the GUI (and the integrated daemon (monerod)) will still function properly without any incoming connections. Now, to open port 18080 properly, you have to forward / open it in your router too.

Thanks 馃憤 Are you able to assist with what I need to fill in here:

2018-10-30

Opening port 18080 allows incoming P2P connections. Like @dEBRUYNE-1 mentioned; your daemon works fine without port forwarding. Personally I sometimes get this error - I ignore it.

As for actually configuring your router to forward port 18080 to the machine on your local network; try to find some guides and/or your router's manual concerning port forwarding. In addition: Windows can block these requests so make sure the Windows firewall allows such connections (TCP and UDP).

From the screenshot you posted I can give some insight:

Service: other
External host: (leave empty if you can)
External port: 18080
Internal host: (the IP address of your machine on your local network; it will start with 192.168.1...
Internal port: 18080

Protocol should probably be UDP (?) but if you can, choose 'Both' from the dropdown menu. print_cn will help you verify your incoming connections are working.

Thanks so much for the help! It seems to be working.

Was this page helpful?
4 / 5 - 1 ratings