Bitcoin Forum

Bitcoin => Bitcoin Technical Support => Topic started by: Satayasat on July 19, 2022, 09:24:24 PM



Title: No valid UPnP IGDs found in debug log
Post by: Satayasat on July 19, 2022, 09:24:24 PM
Hello,

I am getting this message in my debug.log, and am not sure what it means or if I should do anything about it? My node seems to be working fine and I can connect to it via my Sparrow wallet. TIA


Title: Re: No valid UPnP IGDs found in debug log
Post by: NeuroticFish on July 19, 2022, 09:36:45 PM
I think that this means that you cannot receive inbound connections, hence your node helps only with the outbound connections it makes.
I am not sure if I am right and I am not sure I can explain it better, so I leave that to others.
Edit: sorry, I was wrong here, see @NotATether post below.

For your own use this is not a problem.

However, you may find this useful/informative: https://bitcointalk.org/index.php?topic=2135851.0


Title: Re: No valid UPnP IGDs found in debug log
Post by: Satayasat on July 19, 2022, 09:53:05 PM
Thanks for the reply. I did read through that thread you shared prior to posting but it didn't really answer my question. I do have upnp=1 in my configuration file and I think it is related to this, but I am not sure what any of it means tbh.


Title: Re: No valid UPnP IGDs found in debug log
Post by: Satayasat on July 19, 2022, 11:36:21 PM
I just deleted the upnp=1 from the bitcoin.conf and rebooted the node, now that error script no longer appears. I was following a guide from bitcoin magagazine on setting up Sparrow with your node that includes that line and it's not necessary since I'm not using upnp.


Title: Re: No valid UPnP IGDs found in debug log
Post by: nc50lc on July 20, 2022, 03:00:25 AM
I just deleted the upnp=1 from the bitcoin.conf and rebooted the node, now that error script no longer appears. I was following a guide from bitcoin magagazine on setting up Sparrow with your node that includes that line and it's not necessary since I'm not using upnp.
By enabling UPnP in bitcoin's config, you'll have to enable UPnP in your router as well for it to work.
Although that's not necessary if you're using port forwarding or not aiming for inbound connections.


Title: Re: No valid UPnP IGDs found in debug log
Post by: NotATether on July 20, 2022, 05:44:46 AM
I think that this means that you cannot receive inbound connections, hence your node helps only with the outbound connections it makes.

No, according to the source code at src/mapport.cpp (where the error message is actually printed), it just means that there was no UPnP router connected to the computer - in other words, OP's router does not support UPnP or its auto port-mapping feature.


Title: Re: No valid UPnP IGDs found in debug log
Post by: DaveF on July 20, 2022, 11:37:20 AM
If at all possible if you are not using your own router you should not rely on UPNP anyway.

https://bitcointalk.org/index.php?topic=5402188.msg60340726#msg60340726

If you need a port open do it yourself, because if / when your provider closes it you will have to do it anyway. And if you need it open and something else has to change to do it then it can be a scramble to replace their router with yours and so on.

-Dave


Title: Re: No valid UPnP IGDs found in debug log
Post by: Satayasat on July 20, 2022, 01:27:41 PM
Thanks folks for the feedback. My router does support UPnP but I don't use it (for reasons some of you shared) and it is turned off. Deleting the upnp=1 in my config file solved the issue and the node is no longer looking for a upnp igd.