From bb11117755f92244ee76ef277270f8ab62d82c9d Mon Sep 17 00:00:00 2001 From: Chaz Larson Date: Mon, 25 Nov 2024 12:29:22 -0600 Subject: [PATCH] Update gluetun.md --- docs/apps/gluetun.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/apps/gluetun.md b/docs/apps/gluetun.md index 1ab3eee02..b0ca2f119 100644 --- a/docs/apps/gluetun.md +++ b/docs/apps/gluetun.md @@ -101,6 +101,9 @@ gluetun2_docker_networks_alias_custom: plex2_docker_network_mode_default: "container:gluetun2" plex2_auth_token_proxy: "http://gluetun2:8888" ``` + +Once you have made these changes to the inventory, run the relevant plex tags to apply the changes [i.e. `sb install plex` or `sb install plex1 plex2 plex3`]. + !!! caution When routing Plex through Gluetun, you must access Plex between containers at `http://gluetun:32400` where you would previously use the Plex container name. @@ -129,6 +132,8 @@ Depending on if the role in question supports instances or not there will be two For example, to route `jackett` through Gluetun, the entry would be `jackett_docker_network_mode: "container:gluetun"`. +Once you have made these changes to the inventory, run the relevant tags to apply the changes [i.e. `sb install qbittorrent` or `sb install jackett sonarr radarr`]. + !!! caution While multiple containers may be routed through a single Gluetun instance, you must manually ensure there are no port clashes as all port binds for the connected containers will be through the Gluetun container and must have unique ports inside that container.