kevindckr

Members
  • Posts

    3
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

kevindckr's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I did not have these parameters set, only the "extra" Port variables. After setting these it seems to be working better.. Though, what is the difference between adding the ports to VPN_INPUT_PORTS versus VPN_OUTPUT_PORTS. I see that you have 9117 (Jackett WebUI) as an input port but not output, but you also have 8686 (lidarr WebUI) as an output but not input. Why the difference for a WebUI port?
  2. XPost from General Support I have followed Spaceinvader One's video describing how to route the network traffic of one container through another on my Unraid 6.9.1 installation. Specifically, I have routed my binhex-jackett container traffic through my binhex-delugevpn network. To do so I first edited the jackett setup Network type from "Bridge" to "None" Added Extra Parameters: '--net:container:binhex-deluge' Then edited the delugevpn setup Added new port utilizing jacket's (9117, 9117, TCP) Utilizing Spaceinvader One's trick to view the container's IP with `curl ifconfig.io` I can confirm that both containers share the same IP address. I can also view the logs of each container and both are running normally (based on what I have viewed in the log outputs before). I have also performed the same steps to route another container's, netdata, traffic through the delugevpn container to see if it is just an issue with jackett. I can also confirm that it shares the same IP address and the logs "look fine". Though for either container if I navigate to my server's IP address with the specific port for a given routed container, the WebUI still does not load. Interestingly. While the Web UI for jackett does not load, after it has failed it seems to have resolved to the '/UI/Dashboard' Though, I have visited the Web UI prior to implementing these changes, so I assume that is just cached in my browser... But, this does not happen when attempting to navigate to netdata's address. My only other guess is that I need to edit delugevpn's "Connection Manager" to allow for a new/another connection from the containers?.. I have tried a few seemingly logical connection settings to no avail. Potentially, should I disable 'STRICT_PORT_FORWARDING' in the container setup? I assume this is related to the IP tables of the container and does not have much to do with the described situation though..
  3. I have followed Spaceinvader One's video describing how to route the network traffic of one container through another on my Unraid 6.9.1 installation. Specifically, I have routed my binhex-jackett container traffic through my binhex-delugevpn network. To do so I first edited the jackett setup Network type from "Bridge" to "None" Added Extra Parameters: '--net:container:binhex-deluge' Then edited the delugevpn setup Added new port utilizing jacket's (9117, 9117, TCP) Utilizing Spaceinvader One's trick to view the container's IP with `curl ifconfig.io` I can confirm that both containers share the same IP address. I can also view the logs of each container and both are running normally (based on what I have viewed in the log outputs before). I have also performed the same steps to route another container's, netdata, traffic through the delugevpn container to see if it is just an issue with jackett. I can also confirm that it shares the same IP address and the logs "look fine". Though for either container if I navigate to my server's IP address with the specific port for a given routed container, the WebUI still does not load. Interestingly. While the Web UI for jackett does not load, after it has failed it seems to have resolved to the '/UI/Dashboard' Though, I have visited the Web UI prior to implementing these changes, so I assume that is just cached in my browser... But, this does not happen when attempting to navigate to netdata's address. My only other guess is that I need to edit delugevpn's "Connection Manager" to allow for a new/another connection from the containers?.. I have tried a few seemingly logical connection settings to no avail.