can't enable upnp via diginode-setup

[ZuneTracks]

I've been trying to enable uPnP via diginode-setup and every time I set it up, it doesn't stay on. After the services start back up and the dashboard comes on, it says uPnP is off, and my peer count is stuck at 10. Do I need to run diginode-setup as sudo to make it stick? Also this is on the latest version of diginode tools, and my system is a raspberry pi 5 bookworm with all the latest updates to it.

[saltedlolly]

I will need to look into this. It's possible there is a bug. I admit I never use upnn, and to be honest I don't recommend using it. It can be very temperamental depending on your router. I would forward ports manually if I were you.

[ZuneTracks]

I will need to look into this. It's possible there is a bug. I admit I never use upnn, and to be honest I don't recommend using it. It can be very temperamental depending on your router. I would forward ports manually if I were you.

yeah I agree with you on port forwarding. The issue is that my router only lets me forward 12024 to a single device...yeah it's that limited, lol. I'm running multiple nodes with my main one being my Windows server, and then my RPi 5 running diginode tools. This weekend I'm moving to a new internet provider and will be using my own netgear router instead of this modem/router combo that AT&T gave me (which the 5Ghz band just flakes out constantly on anyway)...so I might be able to set up a DMZ and just throw both my server and my diginode in there and call it a day.

[saltedlolly]

for the additional nodes you could manually edit digibyte.conf to change the port for mainnet. e.g. 12034, 12044 etc. I have two diginodes on my local network and this is how I do it.

if using diginode tools, just run diginode --dgbconf to edit the conf file. Change the port= value in the [main] section. Then restart the node with diginode --dgbrestart

(make UPnP port forwarding is turned off first)

[ZuneTracks]

for the additional nodes you could manually edit digibyte.conf to change the port for mainnet. e.g. 12034, 12044 etc. I have two diginodes on my local network and this is how I do it.

if using diginode tools, just run diginode --dgbconf to edit the conf file. Change the port= value in the [main] section. Then restart the node with diginode --dgbrestart

(make UPnP port forwarding is turned off first)

I'll give that a shot on my windows server. I just updated the conf with the parameters and its loading blocks now, so we'll see. Thank you for the reminder...can't believe I didn't even think to use a different port!

[ZuneTracks]

Just by way of updating this issue, I did change ports on my windows server where I'm running DGB Core as well, however I never got any incoming connections. I'm considering just removing DGB Core from that server since I have diginode up and running anyway as my default node.

With that said, I still can't get uPnP to enable via diginode-setup. The dashboard still says it is not on when it restarts.