ShipkaChalk · February 14, 2026 15:30 · Sep 16, 2024 · Sep 9, 2024 · Aug 26, 2024 · Aug 26, 2024
diff --git a/gistfile1.md b/gistfile1.md
@@ -4,7 +4,7 @@ And no not all of us are using it for nefarious means, sometimes people don't ha
 
 Why docker? I prefer it as it keeps items separated and cleaned. It also allows for quickly moving configurations around from server to server if need be.
 
-1. Get yourself a VPS. ( If your VPS has a built in firewall like IONOS, then you need to allow through the ports specified in the VPS docker compose)
+1. Get yourself a VPS. ( If your VPS has a built in firewall like IONOS (but don't use Ionos), then you need to allow through the ports specified in the VPS docker compose)
 3. Install docker ( Do not use snap, follow their offical directions otherwise you may have docker related issues. )
 4. Create this `docker-compose.yml`
 

diff --git a/gistfile1.md b/gistfile1.md
@@ -140,7 +140,15 @@ services:
 
 And that should be it! Bring it up with `docker compose up` and visit VPS:32400 and you’ll see your plex container. Finally make sure to manually specify port `32400` (Or which ever port you used in docker for plex) in the plex remote access settings.
 
-Trouble Shooting
+
+## Ionos
+Don't use it, they limit UDP rates so it drastically drops your speed.
+You can do a quick speed test by running the following:
+
+`docker run -it --network container:wireguard gists/speedtest-cli speedtest`
+
+
+## Trouble Shooting
 <details>
 <summary>Follow the steps below in order, post a comment saying where you get to if it fails. ( Like 2.a ) </summary>
 <br>

diff --git a/gistfile1.md b/gistfile1.md
@@ -4,9 +4,9 @@ And no not all of us are using it for nefarious means, sometimes people don't ha
 
 Why docker? I prefer it as it keeps items separated and cleaned. It also allows for quickly moving configurations around from server to server if need be.
 
-1. Get yourself a VPS
-2. Install docker ( Do not use snap, follow their offical directions otherwise you may have docker related issues. )
-3. Create this `docker-compose.yml`
+1. Get yourself a VPS. ( If your VPS has a built in firewall like IONOS, then you need to allow through the ports specified in the VPS docker compose)
+3. Install docker ( Do not use snap, follow their offical directions otherwise you may have docker related issues. )
+4. Create this `docker-compose.yml`
 
 ```yaml
 version: '3'

diff --git a/gistfile1.md b/gistfile1.md
@@ -5,7 +5,7 @@ And no not all of us are using it for nefarious means, sometimes people don't ha
 Why docker? I prefer it as it keeps items separated and cleaned. It also allows for quickly moving configurations around from server to server if need be.
 
 1. Get yourself a VPS
-2. Install docker
+2. Install docker ( Do not use snap, follow their offical directions otherwise you may have docker related issues. )
 3. Create this `docker-compose.yml`
 
 ```yaml

diff --git a/gistfile1.md b/gistfile1.md
@@ -94,7 +94,7 @@ PresharedKey =
 Endpoint = END POINT OF VPS:51820
 AllowedIPs = 0.0.0.0/0 # You might want to remove the  , ::/0 if you have issues using IPv6
 ```
-
+*IPV6 ISSUES* Remove the ", ::/0" in the allowed IPS
 
 1. Create the `docker-compose.yml` 
 2. Make sure your volumes in plex line up and the volumes for the wireguard line up.

diff --git a/gistfile1.md b/gistfile1.md
@@ -138,7 +138,7 @@ services:
 
 ```
 
-And that should be it! Bring it up with `docker compose up` and visit VPS:32400 and you’ll see your plex container.
+And that should be it! Bring it up with `docker compose up` and visit VPS:32400 and you’ll see your plex container. Finally make sure to manually specify port `32400` (Or which ever port you used in docker for plex) in the plex remote access settings.
 
 Trouble Shooting
 <details>

diff --git a/gistfile1.md b/gistfile1.md
@@ -149,18 +149,24 @@ exec into the containers on Hetzner.
 
 docker exec -it plex /bin/bash
 
+  1. 
 a. Do curl localhost:32400 you should see some html coming back. If it's not plex isn't up.
 b. Do curl icanhazip.com to make sure it's returning the VPS ip. If it's not then your wireguard tunnel is not connected.
 c. Do curl 8.8.8.8 this should return active pings. If it does not there is not internet connection at all.
 
+
+  2.
 Repeat this for
 
 docker exec -it wireguard /bin/bash
+
 
 a. Do curl localhost:32400 you should see some html coming back. If it's not then the plex container is not connected to the wireguard container.
 b. Do curl icanhazip.com to make sure it's returning the VPS ip. If it's not then your wireguard tunnel is not connected.
 c. Do curl 8.8.8.8 this should return active pings. If it does not there is not internet connection at all.
 
+
+  3.
 Then on the VPS
 
 docker exec -it wireguard /bin/bash
@@ -169,11 +175,13 @@ a. curl icanhazip.com to make sure that wireguard container is reaching the outs
 b. Do curl 8.8.8.8 this should return active pings. If it does not there is not internet connection at all.
 c. curl localhost:32400 you should see the plex html. If you don't then you need to make sure you've done the forward ports part on the Hetzner.
 
+  4.
 On the VPS
 a. Outside of the docker instance, do wg show look to see if the peer has connected.
 
 b. curl localhost:32400, you should see the plex html. If you don't then you need to forward the ports on the wg0.conf of the VPS.
 
+  5.
 On your home machine:
 a. Visit VPS:32400 you should get to plex, if you do not then on the VPS it's self you need to open the ports or make sure ufw etc is not blocking them.
 </details>
diff --git a/gistfile1.md b/gistfile1.md
@@ -138,4 +138,42 @@ services:
 
 ```
 
-And that should be it! Bring it up with `docker compose up` and visit VPS:32400 and you’ll see your plex container.
+And that should be it! Bring it up with `docker compose up` and visit VPS:32400 and you’ll see your plex container.
+
+Trouble Shooting
+<details>
+<summary>Follow the steps below in order, post a comment saying where you get to if it fails. ( Like 2.a ) </summary>
+<br>
+
+exec into the containers on Hetzner.
+
+docker exec -it plex /bin/bash
+
+a. Do curl localhost:32400 you should see some html coming back. If it's not plex isn't up.
+b. Do curl icanhazip.com to make sure it's returning the VPS ip. If it's not then your wireguard tunnel is not connected.
+c. Do curl 8.8.8.8 this should return active pings. If it does not there is not internet connection at all.
+
+Repeat this for
+
+docker exec -it wireguard /bin/bash
+
+a. Do curl localhost:32400 you should see some html coming back. If it's not then the plex container is not connected to the wireguard container.
+b. Do curl icanhazip.com to make sure it's returning the VPS ip. If it's not then your wireguard tunnel is not connected.
+c. Do curl 8.8.8.8 this should return active pings. If it does not there is not internet connection at all.
+
+Then on the VPS
+
+docker exec -it wireguard /bin/bash
+
+a. curl icanhazip.com to make sure that wireguard container is reaching the outside world you should see the VPS ip.
+b. Do curl 8.8.8.8 this should return active pings. If it does not there is not internet connection at all.
+c. curl localhost:32400 you should see the plex html. If you don't then you need to make sure you've done the forward ports part on the Hetzner.
+
+On the VPS
+a. Outside of the docker instance, do wg show look to see if the peer has connected.
+
+b. curl localhost:32400, you should see the plex html. If you don't then you need to forward the ports on the wg0.conf of the VPS.
+
+On your home machine:
+a. Visit VPS:32400 you should get to plex, if you do not then on the VPS it's self you need to open the ports or make sure ufw etc is not blocking them.
+</details>
diff --git a/gistfile1.md b/gistfile1.md
@@ -92,9 +92,10 @@ PreDown = FORWARDEDPORT=32400; iptables -D INPUT -i wg0 -p udp --dport $FORWARDE
 PublicKey = 
 PresharedKey = 
 Endpoint = END POINT OF VPS:51820
-AllowedIPs = 0.0.0.0/0
+AllowedIPs = 0.0.0.0/0 # You might want to remove the  , ::/0 if you have issues using IPv6
 ```
 
+
 1. Create the `docker-compose.yml` 
 2. Make sure your volumes in plex line up and the volumes for the wireguard line up.
 

diff --git a/gistfile1.md b/gistfile1.md
@@ -41,6 +41,7 @@ services:
 1. Bring the docker container up once.
 2. Stop the container
 3. Update the main config `wg0.conf` so that under [Interface] but before [Peer] you include:
+4. Update the --to-destination X.X.X.X to point to the Ip of the peer below.
 
 ```
 [Interface]

diff --git a/gistfile1.md b/gistfile1.md
@@ -23,7 +23,7 @@ services:
       - TZ=Etc/UTC
       - SERVERURL=111.111.111.111 # Replace with your server's public domain or IP
       - SERVERPORT=51820
-      - PEERS=plexServer # Replace with peer names
+      - PEERS=plexServer # Replace with peer names, this is chosen by you. Do not use any special characters like _
       - PEERDNS=9.9.9.9
       - INTERNAL_SUBNET=10.13.13.0
       - LOG_CONFS=true

diff --git a/gistfile1.md b/gistfile1.md
@@ -24,7 +24,7 @@ services:
       - SERVERURL=111.111.111.111 # Replace with your server's public domain or IP
       - SERVERPORT=51820
       - PEERS=plexServer # Replace with peer names
-      - PEERDNS=auto
+      - PEERDNS=9.9.9.9
       - INTERNAL_SUBNET=10.13.13.0
       - LOG_CONFS=true
     ports:

diff --git a/gistfile1.md b/gistfile1.md
@@ -2,6 +2,8 @@ Hey, here is how you can route all plex traffic via wireguard out of another VPS
 
 And no not all of us are using it for nefarious means, sometimes people don't have room for a home server.
 
+Why docker? I prefer it as it keeps items separated and cleaned. It also allows for quickly moving configurations around from server to server if need be.
+
 1. Get yourself a VPS
 2. Install docker
 3. Create this `docker-compose.yml`

diff --git a/gistfile1.md b/gistfile1.md
@@ -48,12 +48,12 @@ etc...
 PostUp = iptables -A FORWARD -i %i -j ACCEPT
 PostUp = iptables -A FORWARD -o %i -j ACCEPT
 PostUp = iptables -t nat -A POSTROUTING -o eth+ -j MASQUERADE
-PostUp = iptables -t nat -A PREROUTING -p tcp --dport 32400 -j DNAT --to-destination 10.13.13.2
+PostUp = iptables -t nat -A PREROUTING -p tcp --dport 32400 -j DNAT --to-destination 10.13.13.2 # IP Of peer below
 
 PostDown = iptables -D FORWARD -i %i -j ACCEPT
 PostDown = iptables -D FORWARD -o %i -j ACCEPT
 PostDown = iptables -t nat -D POSTROUTING -o eth+ -j MASQUERADE
-PostDown = iptables -t nat -A PREROUTING -p tcp --dport 32400 -j DNAT --to-destination 10.13.13.2
+PostDown = iptables -t nat -A PREROUTING -p tcp --dport 32400 -j DNAT --to-destination 10.13.13.2 # IP Of peer below
 
 [Peer]
 

diff --git a/gistfile1.md b/gistfile1.md
@@ -60,11 +60,10 @@ PostDown = iptables -t nat -A PREROUTING -p tcp --dport 32400 -j DNAT --to-desti
 ```
 
 1. Update the 10.13.13.2 in the above to be the IP of your peer_plexServer. This will forward port traffic from 32400 to that internal peer.
-2. 
-3 Visit `/root/wireguard/config` and find the `.conf` file for the `plexServer` peer.
-4 Copy that information down.
-5. Bring the container back up with `docker cmpose up`
-6. You're done for the VPS!
+2. Visit `/root/wireguard/config` and find the `.conf` file for the `plexServer` peer.
+3. Copy that information down.
+4. Bring the container back up with `docker cmpose up`
+5. You're done for the VPS!
 
 On the hetzner server
 

diff --git a/gistfile1.md b/gistfile1.md
@@ -60,10 +60,11 @@ PostDown = iptables -t nat -A PREROUTING -p tcp --dport 32400 -j DNAT --to-desti
 ```
 
 1. Update the 10.13.13.2 in the above to be the IP of your peer_plexServer. This will forward port traffic from 32400 to that internal peer.
-8 Visit `/root/wireguard/config` and find the `.conf` file for the `plexServer` peer.
-9 Copy that information down.
-2. Bring the container back up with `docker cmpose up`
-3. You're done for the VPS!
+2. 
+3 Visit `/root/wireguard/config` and find the `.conf` file for the `plexServer` peer.
+4 Copy that information down.
+5. Bring the container back up with `docker cmpose up`
+6. You're done for the VPS!
 
 On the hetzner server
 

diff --git a/gistfile1.txt → gistfile1.md b/gistfile1.txt → gistfile1.md
diff --git a/gistfile1.txt b/gistfile1.txt
@@ -0,0 +1,137 @@
+Hey, here is how you can route all plex traffic via wireguard out of another VPS, this can be used for any container but was inspired by the recent Hetzner block Plex put in place.
+
+And no not all of us are using it for nefarious means, sometimes people don't have room for a home server.
+
+1. Get yourself a VPS
+2. Install docker
+3. Create this `docker-compose.yml`
+
+```yaml
+version: '3'
+services:
+  wireguard:
+    image: linuxserver/wireguard
+    container_name: wireguard
+    cap_add:
+      - NET_ADMIN
+      - SYS_MODULE
+    environment:
+      - PUID=1000
+      - PGID=1000
+      - TZ=Etc/UTC
+      - SERVERURL=111.111.111.111 # Replace with your server's public domain or IP
+      - SERVERPORT=51820
+      - PEERS=plexServer # Replace with peer names
+      - PEERDNS=auto
+      - INTERNAL_SUBNET=10.13.13.0
+      - LOG_CONFS=true
+    ports:
+      - "51820:51820/udp"
+      - "32400:32400"
+    volumes:
+      - /root/wireguard/config:/config
+    sysctls:
+      - net.ipv4.conf.all.src_valid_mark=1
+    restart: unless-stopped
+
+```
+
+1. Bring the docker container up once.
+2. Stop the container
+3. Update the main config `wg0.conf` so that under [Interface] but before [Peer] you include:
+
+```
+[Interface]
+Address = ...
+etc...
+
+PostUp = iptables -A FORWARD -i %i -j ACCEPT
+PostUp = iptables -A FORWARD -o %i -j ACCEPT
+PostUp = iptables -t nat -A POSTROUTING -o eth+ -j MASQUERADE
+PostUp = iptables -t nat -A PREROUTING -p tcp --dport 32400 -j DNAT --to-destination 10.13.13.2
+
+PostDown = iptables -D FORWARD -i %i -j ACCEPT
+PostDown = iptables -D FORWARD -o %i -j ACCEPT
+PostDown = iptables -t nat -D POSTROUTING -o eth+ -j MASQUERADE
+PostDown = iptables -t nat -A PREROUTING -p tcp --dport 32400 -j DNAT --to-destination 10.13.13.2
+
+[Peer]
+
+```
+
+1. Update the 10.13.13.2 in the above to be the IP of your peer_plexServer. This will forward port traffic from 32400 to that internal peer.
+8 Visit `/root/wireguard/config` and find the `.conf` file for the `plexServer` peer.
+9 Copy that information down.
+2. Bring the container back up with `docker cmpose up`
+3. You're done for the VPS!
+
+On the hetzner server
+
+1. Install docker
+2. Create a directory to hold the goods, in the below I created /home/shipka/PlexWireguard
+3. Create `/home/shipka/PlexWireguard/wireguard-client/wg_confs/wg0.conf`
+
+This file will be what is generated by the VPS you just need to add in the `PostUp`, `PreDown` , `PostUp`  and `PreDown` 
+
+```jsx
+[Interface]
+Address = 10.13.13.2
+PrivateKey = 
+ListenPort = 51820
+DNS = 10.13.13.1
+
+PostUp = iptables -t nat -A POSTROUTING -o wg+ -j MASQUERADE
+PreDown = iptables -t nat -D POSTROUTING -o wg+ -j MASQUERADE
+PostUp = FORWARDEDPORT=32400; iptables -A INPUT -i wg0 -p udp --dport $FORWARDEDPORT -j ACCEPT; iptables -A INPUT -i wg0 -p tcp --dport $FORWARDEDPORT -j ACCEPT;
+PreDown = FORWARDEDPORT=32400; iptables -D INPUT -i wg0 -p udp --dport $FORWARDEDPORT -j ACCEPT; iptables -D INPUT -i wg0 -p tcp --dport $FORWARDEDPORT -j ACCEPT;
+
+[Peer]
+PublicKey = 
+PresharedKey = 
+Endpoint = END POINT OF VPS:51820
+AllowedIPs = 0.0.0.0/0
+```
+
+1. Create the `docker-compose.yml` 
+2. Make sure your volumes in plex line up and the volumes for the wireguard line up.
+
+```yaml
+services:
+  wireguard:
+    image: lscr.io/linuxserver/wireguard
+    container_name: wireguard
+    cap_add:
+      - NET_ADMIN
+      - SYS_MODULE
+    environment:
+      - PUID=1000
+      - PGID=1000
+      - TZ=Etc/UTC
+    volumes:
+      - /home/shipka/PlexWireGuard/wireguard-client:/config
+      - /lib/modules:/lib/modules
+    sysctls:
+      - net.ipv4.conf.all.src_valid_mark=1
+    ports:
+      - 32400:32400
+    restart: unless-stopped
+
+  plex:
+    image: linuxserver/plex
+    container_name: plex
+    environment:
+      - PUID=1000
+      - PGID=1000
+      - TZ=Etc/UTC
+      - VERSION=docker
+      - PLEX_CLAIM= #lasts 4 minutes get from plex.tv/claim
+    volumes:
+      - /home/shipka/PlexWireGuard/config:/config
+      - /data/tv:/tv
+      - /data/downloaded:/movies
+    network_mode: service:wireguard
+    restart: unless-stopped
+
+```
+
+And that should be it! Bring it up with `docker compose up` and visit VPS:32400 and you’ll see your plex container.
No results found