Deluge Announces Wrong Port to Tracker After Port is Changed
Posted: Sat Jun 14, 2025 2:26 am
Hi,
Deluge 2.1.1
libtorrent 2.0.10.0
I believe Deluge is passing stale IP:Port info to libtorrent and/or the trackers.
Currently one of the trackers I use is reporting that it has the wrong port for me despite receiving announces since the port has been changed.
Incoming Port is set to 39619.
The tracker reports an old port of 55526.
Additionally, the "ltConfig" plugin shows that libtorrent has the wrong port (55526).
Restarting deluge, sending an announce and then checking the tracker then shows the correct port. It also then shows correct in ltConfig. So it seems like there is some sort of caching / failure to update.
Any guidance would be appreciated.
Deluge 2.1.1
libtorrent 2.0.10.0
I believe Deluge is passing stale IP:Port info to libtorrent and/or the trackers.
Currently one of the trackers I use is reporting that it has the wrong port for me despite receiving announces since the port has been changed.
Incoming Port is set to 39619.
The tracker reports an old port of 55526.
Additionally, the "ltConfig" plugin shows that libtorrent has the wrong port (55526).
Restarting deluge, sending an announce and then checking the tracker then shows the correct port. It also then shows correct in ltConfig. So it seems like there is some sort of caching / failure to update.
Any guidance would be appreciated.