Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Tracker not reflecting the correct Incoming Port detected via script/Deluge Web UI #420

Open
neocharles opened this issue Dec 19, 2024 · 0 comments

Comments

@neocharles
Copy link

I have noticed that if I restart the docker container, and check the online tracker I am using to verify connectivity, that it winds up showing the new IP address that PIA has provided to me, but shows the old Port # that was assigned prior to the reboot for the port forwarding.

If I right click on the torrent, and choose "update tracker", then it begins to reflect the new port #.

I am uncertain if this is a sign that the tracker is being updated initially on boot prior to the script executing to update the incoming port number, or if this is a sign of some other issue taking place / some setting I may need to adjust somewhere. I wouldn't want to have to go and manually update any of the torrents which are being seeded each time the container may reboot and/or any time the VPN connection drops and reconnects.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant