On 3/1/2025 at 12:35 PM, xST4R said:

Hello, is there an up-to-date guide on how to get GluetunVPN working with Mullvad? (port forwarding is no longer available). I would also like to use only WireGuard as a connection.

That's the setup I have. As far as I remember I just followed the setup steps outlined in Github? I set it up a couple of months ago as an absolute beginner.

 

Unfortunately this forum is dead as there's hardly any activity and questions go unanswered.

 

Edit: I can share my setup if you have any specific questions.

Edited March 16, 20251 yr by helgrimm

Hi,

 

I wonder why my GluetunVPN docker always autostarts, even though it's not set to start automatically. Why might that be?

On 3/15/2025 at 4:49 PM, helgrimm said:

That's the setup I have. As far as I remember I just followed the setup steps outlined in Github? I set it up a couple of months ago as an absolute beginner.

 

Unfortunately this forum is dead as there's hardly any activity and questions go unanswered.

 

Edit: I can share my setup if you have any specific questions.

Would absolute dream, if you could share your config.

Evening folks,

 

Hi Folks,

 

Following SpaceinvaderOne's recent video I decided to install GluetunVPN a few days ago. Since then i managed to get my *arr's, qBittorrent and Firefox. I still had an issue reaching my Usenet Indexer but this was on hold until i got SABnzbd to connect properly.

While I was trouble shooting I accidentally attempted to add ports for SABnzbd in GluetunVPN while SABnzbd was still in bridge mode. I got an error along the lines of GluetunVPN needed complete access to ports. It was only at this point that i remembered my error. I returned to the Docker page and GluetunVPN was no longer there. It is available through Apps but when I reinstall all my previous settings are lost so I have to start again from scratch.

This seems strange behaviour so before starting again I thought I would post here.

 

I did manage to download diagnostics once I noticed that GluetunVPN was gone and have attache here in case that is useful.

 

chestnut-diagnostics-20250515-1921.zip

6 minutes ago, njg said:

Evening folks,

 

Hi Folks,

 

Following SpaceinvaderOne's recent video I decided to install GluetunVPN a few days ago. Since then i managed to get my *arr's, qBittorrent and Firefox. I still had an issue reaching my Usenet Indexer but this was on hold until i got SABnzbd to connect properly.

While I was trouble shooting I accidentally attempted to add ports for SABnzbd in GluetunVPN while SABnzbd was still in bridge mode. I got an error along the lines of GluetunVPN needed complete access to ports. It was only at this point that i remembered my error. I returned to the Docker page and GluetunVPN was no longer there. It is available through Apps but when I reinstall all my previous settings are lost so I have to start again from scratch.

This seems strange behaviour so before starting again I thought I would post here.

 

I did manage to download diagnostics once I noticed that GluetunVPN was gone and have attache here in case that is useful.

 

chestnut-diagnostics-20250515-1921.zip 233.8 kB · 0 downloads

 

Hi,

 

If you go to your Docker tab, then select 'Add Container' down bottom left of the screen (under your last active container), you should be able to select your GluetunVPN config from the 'Template' drop down list.

 

Hope that helps.

That is fantastic. Never noticed that button before.

Everyday being a school day and all.

 

Thank you so much.

55 minutes ago, unraid888 said:

It is available through Apps but when I reinstall all my previous settings are lost so I have to start again from scratch.

Did you look for it in Previous Apps on the Apps page? That is the usual way to reinstall with the same settings. Previous Apps uses those same templates.

Any idea why containers using gluetun will randomly stop working and require a restart to get it to work again, only for it to stop working again later?

3 hours ago, Abhi said:

Any idea why containers using gluetun will randomly stop working and require a restart to get it to work again, only for it to stop working again later?

 

You really need to mention all circumstances to actually get help, like which containers, otherwise it is like asking why is there no beer... but...

 

https://github.com/qdm12/gluetun/issues/1407#issuecomment-2870017373

On 5/19/2025 at 5:54 PM, Samsonight said:

 

You really need to mention all circumstances to actually get help, like which containers, otherwise it is like asking why is there no beer... but...

 

https://github.com/qdm12/gluetun/issues/1407#issuecomment-2870017373

The idea is the same but it happens to any containers I attach gluetun to.

I'd love to mention all circumstances, but really thats all I know. Randomly the docker will just stop working, I'd assume as it has something to do with healthchecks?

I set that on qbit, but what about sabnzbd?

Edited May 23, 20251 yr by Abhi

Fix WebUI button in Unraid when using container:GluetunVPN

If you're running Docker containers in Unraid using network_mode: container:GluetunVPN and wondering why the WebUI button is missing or opens about:blank#blocked — here's the fix.

🛠️ Steps:

1. Go to Docker tab in Unraid

2. Click Edit on your container

3. Switch to Advanced View (top right corner)

4. Locate the WebUI field

5. Change the value to: http://YOUR_IP:PORT (Use your actual local IP and the container’s WebUI port)

6. Click Apply

✅ Now the WebUI button will show up and correctly open the app interface.

📦 Tested with: Brave, qBittorrent, Tor Browser (behind GluetunVPN)
🔐 Still fully routed through VPN — just restores local access to the UI.

Quick Question on this GluetunVPN image...why, when you select Wireguard as protocol does it continue to not let you submit because it wants an openvpn username and password?

I ended up removing the entire option for OpenVPN and obviously, this causes the entire container to barf on itself. To be honest, I think you should remove most of the options from the container and have documentation on how to add them in for each provider instead of having the WALLL OF TEXT gretting for the container.

Edited June 22, 20251 yr by devnet

11 hours ago, devnet said:

Quick Question on this GluetunVPN image...why, when you select Wireguard as protocol does it continue to not let you submit because it wants an openvpn username and password?

The OpenVPN user and password variables being required is a setting in the template for the unRAID CA store, not the container itself. I only maintain the template for the CA store and not the Gluetun app or it's container. I have modified the template so these variables are no longer marked as required.

11 hours ago, devnet said:

I ended up removing the entire option for OpenVPN and obviously, this causes the entire container to barf on itself. To be honest, I think you should remove most of the options from the container and have documentation on how to add them in for each provider instead of having the WALLL OF TEXT gretting for the container.

As with any of the containers installed through the CA store, you can always remove and add and variables or settings to customize it to your own liking and preferences. The included variables were originally chosen after seeking input from a number of users and what the most common in-use variables were. Every user has their own use-cases, preferences, and opinions. I try to accommodate where it makes sense, but cannot please everyone while also maintaining a stable work/family/hobby/life balance. I would love to allow for this to make up even a portion of my 50-60 hour work week, but alas, both my employer and family would likely frown upon that...

As for documentation, the Gluetun dev has an excellent wiki that is kept as up to date as possible (URL included below). I recommend everyone using the app check it out, as it has many more options, configuration settings, and information that are not included in the template I attempt to maintain in my ever-decreasing free time.

7.1.4 running latest GlueTunVPN PR release.

How and why is GluetunVPN starting itself as soon as array starts? It's the only Docker I have ever seen this symptom. Autostart is 100% set to off and it still starts on it's own.

I'll be honest. I only installed roughly a month ago and I had disabled all docker starts due to a licensing issue I ran into a couple of days ago. That is when I noticed this.

13 hours ago, SkepticalOptimist said:

7.1.4 running latest GlueTunVPN PR release.

How and why is GluetunVPN starting itself as soon as array starts? It's the only Docker I have ever seen this symptom. Autostart is 100% set to off and it still starts on it's own.

I'll be honest. I only installed roughly a month ago and I had disabled all docker starts due to a licensing issue I ran into a couple of days ago. That is when I noticed this.

Take a look at the ‘Extra Parameters:’ within the docket configuration (you’ll need to enable advanced view to see this). From recollection there’s a restart tag set in here, which you can remove.

On 7/11/2025 at 2:25 AM, johnyb said:

Take a look at the ‘Extra Parameters:’ within the docket configuration (you’ll need to enable advanced view to see this). From recollection there’s a restart tag set in here, which you can remove.

I saw that and figured that may be it. But, had to ask as I wasn't' 100% sure and don't want to break it. Thanks for responding.

Hi all, I’ve been having an issue with gluetun and am unsure where I’m going wrong.

I was following SpaceInvaderOne’s video both for general setup and also enabling the container as a tailscale exit node. I wanted to have a couple of containers tunneling to different VPN locations to give a few options for VPNs while still being connected to tailscale (I don’t use Mullavad). Initial setup of one container went well, and then I tried to set up a second instance of it to connect to a different server. I edited the config folder and tailscale states folder to have a different path from the original containers (ie gluetun2). Initial setup of that one also seemed to work as I expected.

A few hours later, I was able to use internet on containers running through the second instance’s network, but it was not actually connected to the VPN and was showing my home IP. I thought by design something like that wasn’t really possible, so I’m pretty confused.

When I checked the logs, I was in a prompt to login to tailscale just like you get on initial setup. This tries to add itself as a new node. Restarting the container seems to fix the issue for a bit, but then it happens again.

I’m not really sure which of these factors are actually relevant, so wanted to be as detailed as possible. Happy to provide any additional information that would be helpful. Thanks!

does anyone know, how to configure GlutenVPN with NORDVPN, to use the special servers like double vpn or obfuscated?

23 hours ago, th3d4rk said:

does anyone know, how to configure GlutenVPN with NORDVPN, to use the special servers like double vpn or obfuscated?

No. This is why I stopped trying to use it. I couldn't even get wireguard through Nordvpn to work. I went back to openvpn and ditched my plans for a gluetun container.

Edited July 17, 2025Jul 17 by devnet

Trying to install ddns-updater to support deSEC as DuckDNS seems to be having some downtime. I keep getting an error:

'''

Running version latest built on 2024-12-24T09:20:36.130Z (commit 78f3061)

🔧 Need help? ☕ Discussion? https://github.com/qdm12/ddns-updater/discussions/new/choose
🐛 Bug? ✨ New feature? https://github.com/qdm12/ddns-updater/issues/new/choose
💻 Email? [email protected]
💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12
2025-08-19T15:10:22-04:00 INFO Settings summary:
├── HTTP client
| └── Timeout: 10s
├── Update
| ├── Period: 5m0s
| └── Cooldown: 5m0s
├── Public IP fetching
| ├── HTTP enabled: yes
| ├── HTTP IP providers
| | └── all
| ├── HTTP IPv4 providers
| | └── all
| ├── HTTP IPv6 providers
| | └── all
| ├── DNS enabled: yes
| ├── DNS timeout: 3s
| └── DNS over TLS providers
| └── all
├── Resolver: use Go default resolver
├── Server
| ├── Listening address: :8000
| └── Root URL: /
├── Health
| └── Server listening address: 127.0.0.1:9999
├── Paths
| ├── Data directory: /updater/data
| ├── Config file: /updater/data/config.json
| └── Umask: system default
├── Backup: disabled
└── Logger
├── Level: info
└── Caller: hidden
2025-08-19T15:10:22-04:00 INFO reading JSON config from file /updater/data/config.json
2025-08-19T15:10:22-04:00 INFO file not found, creating an empty settings file
2025-08-19T15:10:22-04:00 ERROR cannot write configuration to file: open /updater/data/config.json: permission denied
2025-08-19T15:10:22-04:00 INFO Shutdown successful

'''

The only mod to the template is to add my TZ. The install exits and leaves no files or folders in Appdata. Anybody seeing this?

Latest Gluetun update broke my ProtonVPN setup. Not sure what the change was (where even are the update notes for these incremental gluetun container changes?)

Rolling back to qmcgaw/gluetun:v3.40.0 fixed it.

Edited November 13, 2025Nov 13 by Tinqer

2 hours ago, Tinqer said:

Latest Gluetun update broke my ProtonVPN setup. Not sure what the change was (where even are the update notes for these incremental gluetun container changes?)

Rolling back to qmcgaw/gluetun:v3.40.0 fixed it.

I'm am not sure on what changes were made in the latest set of commits. I don't think there is a changelog from the dev on commit level changes but you can look at the notes for each of the commits here:

https://github.com/qdm12/gluetun/commits/master/

Or there is the master changelog for major/minor releases here:

https://github.com/qdm12/gluetun/releases

Using the :latest tag is always risky and it is usually recommended to use a tag for the latest stable release instead.

On 11/13/2025 at 5:31 PM, Tinqer said:

Latest Gluetun update broke my ProtonVPN setup. Not sure what the change was (where even are the update notes for these incremental gluetun container changes?)

Rolling back to qmcgaw/gluetun:v3.40.0 fixed it.

I can confirm this is busted as of today's build. It is indicating the password is missing for Proton. (when it has not been changed for over 5 months) I'll try rolling back as well.

https://github.com/qdm12/gluetun/issues/2992

Edited November 18, 2025Nov 18 by goldbondx

Gluetun was working great routing Prowlarr and Qbitorrent traffic. Both those apps are not working anymore. I can get out to the Internet on Firefox when I use Gluetun as a proxy. Is this a recent update issue? If so, what is the working previous version?

FYI: After Glutun update this weekend, all my dependent dockers failed to connect. I had to change each dependent to "bridge" connection save/rebuild, then reset the connection through Glutun. After this silly "reset", all was normal again. Not sure what happened or if this was truly an update related thing. Just thought I'd put this note here in case anyone else has a similar issue.