You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: