November 4, 2025Nov 4 I recently noticed some odd port assignments shown on my main docker page for containers that route their network via another container. Here is a quick example where my Jackett container routes via my Deluge VPN container, which is 192.168.70.xx, and when I access Jackett it is 192.168.70.xx:jackett_port as expected. So, why is jackett showing mappings for 192.168.90.xx a subnet that isn't part of the equation here. I think long before I moved to running Jackett via deluge it was on that subnet, but I guess I never really noticed that they haven't 'gone away' after the change.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.