Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[SUPPORT] DiamondPrecisionComputing - ALL IMAGES AND FILES

Featured Replies

16 hours ago, Tobîîas said:

how can i use it on firefox?
when I start via the WebUI, do I get nothing?

Yes, you get no visible change. The VPN is transparent and always on for Firefox in this case, since all network traffic is routed via Gluetun. If you get no errors and internet works in your Firefox container, it should be working.

 

You can verify for example via https://ip.me. If the IP it shows in your containered Firefox differs from what you get on another computer on your network (or your Unraid box, you can also do curl ip.me via Unraid console/ssh for the same effect), then your VPN is working. The IP your Firefox container shows via ip.me should also match your VPN configuration.

  • Replies 357
  • Views 119.6k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • biggiesize
    biggiesize

    Dockers Available so far:   ddns-updater Product Owner: QMCGAW Product Support: https://github.com/qdm12/ddns-updater/issues/new/choose GluetunVPN

  • Hello everyone,   I'm the author/maintainer of gluetun (and others). I usually don't participate here due to lack of time and got plenty to answer on github already, but I was emailed saying

  • Hello again, I wrote https://github.com/qdm12/gluetun/discussions/1152 since I had a report from someone outside the Unraid ecosystem as well. TLDR: it's a false positive due to it being compiled from

Posted Images

I still don't understand how I can reach my Firefox docker container.

where can i find out which new address my firefox container has now?

40 minutes ago, Tobîîas said:

I still don't understand how I can reach my Firefox docker container.

where can i find out which new address my firefox container has now?

Apologies, my answer before was basically correct, but missing a crucial step if you need to interact with the container :)

 

You will need to expose your Firefox container's web UI port via your Gluetun container (since network traffic now goes through that one).

 

For example, if Firefox's web UI port is 3000, you would add that to Gluetun's configuration. You will need to remove that port mapping from the Firefox container first, or at least change it to something different.

 

So you'd add something like this to your Gluetun container (change ports according to your configuration/preference):

image.png.0ce5c04b98c31f9ac381c72e1d6c38aa.png

 

21 hours ago, ansgaros said:

Apologies, my answer before was basically correct, but missing a crucial step if you need to interact with the container :)

 

You will need to expose your Firefox container's web UI port via your Gluetun container (since network traffic now goes through that one).

 

For example, if Firefox's web UI port is 3000, you would add that to Gluetun's configuration. You will need to remove that port mapping from the Firefox container first, or at least change it to something different.

 

So you'd add something like this to your Gluetun container (change ports according to your configuration/preference):

image.png.0ce5c04b98c31f9ac381c72e1d6c38aa.png

 

THANK YOU!!!
it finally works

  • 2 weeks later...

Hi,

 

I had an issue with the gluetunvpn container, it was stuck in an endles restart circle.

A new container version has been pushed a few hours ago. does anyone had the same problem ?

The latest version is indeed broken : https://github.com/qdm12/gluetun/issues/2244

 

I solved it by manually adding the v3.38 version to the docker application.

Edited by hot22shot

  • 1 month later...
On 4/30/2024 at 4:45 PM, hot22shot said:

Hi,

 

I had an issue with the gluetunvpn container, it was stuck in an endles restart circle.

A new container version has been pushed a few hours ago. does anyone had the same problem ?

The latest version is indeed broken : https://github.com/qdm12/gluetun/issues/2244

 

I solved it by manually adding the v3.38 version to the docker application.

 

From that github thread it looks like it was fixed, though I'm unsure if the fix has been fully released as last week I started to receive a crash loop as well but a different error: context deadline exceeded

 

2024-06-13T19:11:55+10:00 INFO [firewall] setting allowed input port 59339 through interface wg0...
2024-06-13T19:11:55+10:00 INFO [firewall] setting allowed input port 61710 through interface wg0...
2024-06-13T19:11:57+10:00 ERROR [ip getter] Get "https://ipinfo.io/": context deadline exceeded (Client.Timeout exceeded while awaiting headers) - retrying in 40s
2024-06-13T19:11:58+10:00 INFO [http server] 400 GET  wrote 41B to 192.168.0.117:59634 in 7.599µs
2024-06-13T19:11:59+10:00 INFO [http server] 400 HEAD  wrote 42B to 192.168.0.117:59641 in 17.235µs
2024-06-13T19:11:59+10:00 INFO [http server] 400 GET /favicon.ico wrote 41B to 192.168.0.117:59634 in 3.282µs
2024-06-13T19:12:26+10:00 INFO [healthcheck] program has been unhealthy for 31s: restarting VPN
2024-06-13T19:12:26+10:00 INFO [healthcheck] 👉 See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
2024-06-13T19:12:26+10:00 INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION
2024-06-13T19:12:26+10:00 INFO [vpn] stopping
2024-06-13T19:12:26+10:00 INFO [firewall] removing allowed port 59339...
2024-06-13T19:12:26+10:00 INFO [firewall] removing allowed port 61710...
2024-06-13T19:12:26+10:00 INFO [vpn] starting
2024-06-13T19:12:26+10:00 INFO [firewall] allowing VPN connection...
2024-06-13T19:12:26+10:00 INFO [wireguard] Connecting to 146.70.200.194:51820
2024-06-13T19:12:26+10:00 INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.

 

To be honest I kept the 3.38 version and never looked back 😄

  • 2 weeks later...

I am running 2 instances of ddns-updater and this error is appearing in my log:

 

2024-06-28T00:29:39Z ERROR starting services: starting health http server: listen tcp 192.168.1.211:9999: bind: cannot assign requested address

 

This was working until I just updated it.  Nothing else is using that port.

 

Edit: Changed ip to 127.0.0.1 and it seems to be working now.

Edited by Spectral Force

I just set up GluetunVPN with Deluge. It works great until it doesn't.

 

Once a day or so, Deluge stops working. It won't work until I restart GluetunVPN. So I think there's just an occasional disconnect in Gluetun that causes the issues.

 

Is there a way to have Gluetun reconnect on a disconnect or restart the container on an error? Or is there any way to set up an email alert when Gluetun has an issue?

No being , no arranca

Captura de pantalla 2024-07-10 170721.png

  • 3 weeks later...

Hello, I'm trying to get ddns-updater working but I keep running into issues:

 

The log file reports this: 

 

2024-07-26T12:30:02-04:00 ERROR reading file: open /updater/data/updates.json: permission denied
2024-07-26T12:30:02-04:00 INFO Shutdown successful

 

I have tried to create the directory structure and set the permissions it needs to get to the file but it doesn't seem to find it

 

Any suggestions?

  • 5 weeks later...

Installed GluetunVPN (qmcgaw/gluetun) app from Community Application... have it configured and running and seems to be connecting to PIA as expected... Issue seems to be I am unable to add new ports for my existing dockers that I want to route through Gluetun.

 

When adding a new port on the docker config, there is no input for "container port" so unable to access any of those dockers obviously.

Vd7to37.png

 

uENt7IJ.png

 

 

18 minutes ago, SuperW2 said:

Installed GluetunVPN (qmcgaw/gluetun) app from Community Application... have it configured and running and seems to be connecting to PIA as expected... Issue seems to be I am unable to add new ports for my existing dockers that I want to route through Gluetun.

 

When adding a new port on the docker config, there is no input for "container port" so unable to access any of those dockers obviously.

Vd7to37.png

 

uENt7IJ.png

 

 

You're probably using network mode Host. Gluetun defaults to Bridge (like most containers seem to do).

 

Not sure how using Host network changes things. Is there any particular reason you'd be using that?

 

My uneducated suggestion is to use network mode Bridge for Gluetun. That seems to work for me, at least.

 

I'd you're already using Bridge, then I have no idea.

1 hour ago, ansgaros said:

You're probably using network mode Host. Gluetun defaults to Bridge (like most containers seem to do).

 

Not sure how using Host network changes things. Is there any particular reason you'd be using that?

 

My uneducated suggestion is to use network mode Bridge for Gluetun. That seems to work for me, at least.

 

I'd you're already using Bridge, then I have no idea.

I was/am using custom network which I've always run my dockers on a unique network/VLAN segmented from my primary unraid host network.  As soon as I moved the Gluetun docker back to "bridge" mode from my custom network, it then let me add the container port as expected...

  • 2 weeks later...

i am not good with these things, so please forgive me, but I just wanted to protect my server behind a VPN, and I read that gluetun was "easy". (I wish people would stop using words like that for anything techy...). I have Mullvad, and am using wireguard where possible.

 

(I tried installing the vpn with the wireguard settings in Unraid Settings, and that didn't seem to work, though I'd probably prefer to do that).

 

So I installed this app on unraid on the thought that I could route qbittorrent, deluge and rutorrent through it. However, reading replies in this thread, does have I misunderstood what gluetun does? Someone above suggests that the entire internet traffic for a router will now go through it? I don't think I want all internet traffic to go through the server. I just wanted the torrent clients (and *arrs, I guess) to be routed through a VPN.

 

Either way, whatever information and keys and addresses I'm getting from mullvad, it seems i'm inputting incorrectly, and tutorials and guides seem outdated for the amount of fields that need filling now in 2024. (it seems older versions needed less information).

 

Can someone guide me through how to protect my server? Thanks

  • 4 weeks later...

I’ve successfully installed GluetunVPN, and everything seems to be working and connected. However, I’m struggling to get my other Docker container (Stash) to connect and run through the VPN. Here’s what I’ve tried so far on Stash:

 

  • Network type: None
  • Extra Parameters: --network=container:GluetunVPN

 

Every time I try to start Stash, it shows green for a second, but when I refresh the Unraid page, it’s stopped again. I’m super confused and feeling kind of stuck right now.

Any advice or suggestions would be greatly appreciated!

 

 

Edited for more information. This is what the log says:

INFO[2024-09-28 17:15:14] using config file: /root/.stash/config.yml   
INFO[2024-09-28 17:15:16] [InitHWSupport] Supported HW codecs [0]:     
INFO[2024-09-28 17:15:16] stash version: v0.27.0 (c45ae068) - Official Build - 2024-09-23 03:04:17 
INFO[2024-09-28 17:15:16] stash is listening on 0.0.0.0:9999           
INFO[2024-09-28 17:15:16] stash is running at http://localhost:9999/   
ERRO[2024-09-28 17:15:16] http server error: listen tcp 0.0.0.0:9999: bind: address already in use 

Edited by dubbleup99

19 hours ago, dubbleup99 said:

I’ve successfully installed GluetunVPN, and everything seems to be working and connected. However, I’m struggling to get my other Docker container (Stash) to connect and run through the VPN. Here’s what I’ve tried so far on Stash:

 

  • Network type: None
  • Extra Parameters: --network=container:GluetunVPN

 

Every time I try to start Stash, it shows green for a second, but when I refresh the Unraid page, it’s stopped again. I’m super confused and feeling kind of stuck right now.

Any advice or suggestions would be greatly appreciated!

 

 

Edited for more information. This is what the log says:

INFO[2024-09-28 17:15:14] using config file: /root/.stash/config.yml   
INFO[2024-09-28 17:15:16] [InitHWSupport] Supported HW codecs [0]:     
INFO[2024-09-28 17:15:16] stash version: v0.27.0 (c45ae068) - Official Build - 2024-09-23 03:04:17 
INFO[2024-09-28 17:15:16] stash is listening on 0.0.0.0:9999           
INFO[2024-09-28 17:15:16] stash is running at http://localhost:9999/   
ERRO[2024-09-28 17:15:16] http server error: listen tcp 0.0.0.0:9999: bind: address already in use 

Have you added the ports needed for stash to the gluten container configuration?

  • 1 month later...

This morning started getting certificate issue below:

VERIFY ERROR: depth=1, error=self-signed certificate in certificate chain:

  • 1 month later...

Hi ! :)

I have a problem recently, DDNS Updater won't update anymore :/

In fact, in doesn't detect the new IP and just tell me it's unchanged for 300+days, and display an old one


Today i tried to redo the config.json since there was some little change from when i installed it a year ago and used this template :
https://github.com/qdm12/ddns-updater/blob/master/docs/infomaniak.md

 

I'm joining docker logs (replaced my domain by *)

 

I don't understand why it won't work :/

 

Thanks

DDNSlogs.txt

Edited by AinzOolGown

Evening all,

After SpaceInvaders latest video, I thought I'd try out GluetunVPN.

I've successfully setup Sabnzbd, Radarr & Sonarr to run through Gluetun, which is running ProtonVPN (wireguard). My issue however is that I can not for the life of me get qbittorrent (Linuxserver version) to work with Gluetun.

Qbittorrent will start up and returns the VPN IP provided by Gluetun, however it won't download anything. I believe it will be down to me not having successfully set port forwarding. I have tried a million different things, resulting in a mixed bag of Gluetun and/or qbittorrent refusing to start, and me having to start over several times, but I have now exhausted my ability to solve this on my own. I'm sure it will be something simple.

Below are screenshots of my GluetunVPN & qbittorrent setups.

 

Qbittorrent;

Screenshot_20241224_185704_org_mozilla_firefox_HomeActivity.thumb.jpg.0f79094e94bfa231218a818a65eb7112.jpg

 

GluetunVPN;

Screenshot_20241224_185814_org_mozilla_firefox_HomeActivity.thumb.jpg.7bb30771c166100edacdf4b6704dfcae.jpg

Screenshot_20241224_185837_org_mozilla_firefox_HomeActivity.thumb.jpg.7ec5ff8f72ca8da0488029ec6d5c3f9c.jpg

Screenshot_20241224_185900_org_mozilla_firefox_HomeActivity_edit_119074247298482.thumb.jpg.1763372e8a43b75c4c84f377e8f6e956.jpg

Screenshot_20241224_185922_org_mozilla_firefox_HomeActivity.thumb.jpg.15270f38b63fb7f0a7282c5b30b14fb2.jpg

Screenshot_20241224_185940_org_mozilla_firefox_HomeActivity.thumb.jpg.2f8eb065cdc22ff38441e45d3c7e14c4.jpg

Screenshot_20241224_185958_org_mozilla_firefox_HomeActivity.thumb.jpg.b5cc88d74f3b715df3cc036f1a65818b.jpg

Screenshot_20241224_190016_org_mozilla_firefox_HomeActivity.thumb.jpg.db577a3ec2bb53aa0e7297ea9b0074ff.jpg

Screenshot_20241224_190036_org_mozilla_firefox_HomeActivity.thumb.jpg.509824897ad3f5a428a67d2bbeb70955.jpg

Screenshot_20241224_190056_org_mozilla_firefox_HomeActivity.thumb.jpg.7f9f498c0bc4ad667d25455a778dd547.jpg

Screenshot_20241224_190113_org_mozilla_firefox_HomeActivity.thumb.jpg.1f15d50c2ca6fa4ed43659d8d423b8e5.jpg

 


Any advice would be greatly appreciated.

 

 

***Update***

For those that may run across this issue in the future, I managed to resolve the matter. Having a further look around the settings within qbittorrent, I changed the network interface (tools-options-advanced) from wg0 to tun0, which is what is set for the GluetunVPN VPN_INTERFACE option, and its working (just tested via ipleak.net). It seems so straight forward in hindsight, but I've been wracking my brain's for the past few days on this.

Edited by unraid888

  • 3 weeks later...
On 7/5/2024 at 4:21 PM, shaunvis said:

I just set up GluetunVPN with Deluge. It works great until it doesn't.

 

Once a day or so, Deluge stops working. It won't work until I restart GluetunVPN. So I think there's just an occasional disconnect in Gluetun that causes the issues.

 

Is there a way to have Gluetun reconnect on a disconnect or restart the container on an error? Or is there any way to set up an email alert when Gluetun has an issue?


I believe I'm having the same issue.

I have GlueTUN setup using Mullvad and also as a Tailscale Exit Node. I have both Qbit and Prowlarr using the GlueTUN network. All works well, until it doesn't. Regularly I'll wake up to Indexer errors on all my *arrs, saying they can't reach the indexers and Qbit (my *arrs route via Prowlarr). A reboot of each container fixes this.

I'm assuming that at some point GlueTUN has an issue, which it manages to fix itself, but it leaves any container which is using it out in the cold until it is restarted.

Is there any way to get GlueTUN to restart other containers after recovering from an error?

For now I've solved it by removing both Qbit and Prowlarr from the GlueTUN network and pointing them to the GlueTUN proxy instead.

Edited by NeoDude

Surprisingly the container Gluetun runs by default in Userspace

2025-01-17T17:03:16+09:00 INFO [wireguard] Using userspace implementation since Kernel support does not exist

by adding the Extra parameter

--device /dev/tun

the status changes in Log to

2025-01-17T17:03:21+02:00 INFO [wireguard] Using available kernelspace implementation

the overhead (slower) is staggering for usermode:

https://nordvpn.com/blog/wireguard-kernel-module-vs-user-space/
https://www.netmaker.io/resources/kernel-module-vs-user-space-wireguard

Greetings,
 

I have Gluetunvpn running and several dockers working through it. I can confirm in Firefox that I'm behind VPN, but I'm leaking DNS requests. My DNS requests show as originating from Cloudflare. I'm guessing this has to do with the setting "DOT" which is on, and the DOT provider set as Cloudflare. The context help says -

 

Quote

Container Variable: DOT
(Recommended: on) Activate DNS over TLS with Unbound

 

The whole purpose of a VPN is privacy, so I'd presume this is beneficial in some way. I don't know what Unbound is - something I additionally have to set up? Or is DNS over TLS up and running with this setting "on"? Who can see my DNS requests now. Cloudflare can, can my ISP? Can others? Why is this beneficial compared to running DNS through the VPN provider?

 

Thanks for making and offering this software :)

  • 4 weeks later...

Good evening
I have a problem with upload speed with qbittorent: It is very slow (69.6 KiB/s avg.)
I go through pia as a vpn. Is there any action to be taken regarding the port forwarding? A configuration of qbittorent? When restarting gluetun and qbittorent, the upload speed is fast, and then it goes back down to around 1kib/s

  • 2 weeks later...

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.

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.