[SUPPORT] DiamondPrecisionComputing - ALL IMAGES AND FILES

[biggiesize]

4 hours ago, davidudl said:

Hello,

i get some weird behaviour regarding port mappings with docker containers which are routed through Gluetun (see picture). The containers routed through Gluetun show port mappings of other containers which are NOT routed through Gluetun. In this case port 3306 is a MariaDB container and the other ones are from Jellyfin. It seems every time i restart the containers, they show other mappings. Everything seems to be working fine regardless, but why does this happen?

That looks to me like the containers are set to use "container:GluetunVPN" as their network connection. Make sure you go into each and set the "Network Type" accordingly.

[davidudl]

Yes, I want that the network connection is GluetunVPN for the containers shown in the picture. What bothers me is that there are port mappings for the ports 3306, 1900, 7359, 8096 and 8920. The ports for the containers with the VPN  network connection (shown in picture) are defined in GlueTUN and they have nothing to do with the ports shown in port mappings.

[biggiesize]

1 hour ago, davidudl said:

Yes, I want that the network connection is GluetunVPN for the containers shown in the picture. What bothers me is that there are port mappings for the ports 3306, 1900, 7359, 8096 and 8920. The ports for the containers with the VPN  network connection (shown in picture) are defined in GlueTUN and they have nothing to do with the ports shown in port mappings.

If memory serves me correctly, the UI doesn't look at the template for the container for the ports in use but instead inspects the container itself to see which ports are exposed. I wouldn't expect any issues. Possibly @bonienl would have more insight.

[leif]

I just upgraded to the latest  version and and its restarting all the time with the following info/error 

 

ERROR [vpn] cannot get version information: Get "https://api.github.com/repos/qdm12/gluetun/commits": context canceled

INFO [healthcheck] program has been unhealthy for 26s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)

 

and its ongoing in a endless loop im running nordvpn 

 

[biggiesize]

On 8/15/2023 at 3:18 PM, leif said:

I just upgraded to the latest  version and and its restarting all the time with the following info/error 

 

ERROR [vpn] cannot get version information: Get "https://api.github.com/repos/qdm12/gluetun/commits": context canceled

INFO [healthcheck] program has been unhealthy for 26s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)

 

and its ongoing in a endless loop im running nordvpn 

 

Can you post the full error log?

[leif]

On 8/17/2023 at 5:37 PM, biggiesize said:

Can you post the full error log?

2023-08-16T18:46:32+02:00 INFO [openvpn] TUN/TAP device tun0 opened
2023-08-16T18:46:32+02:00 INFO [openvpn] /sbin/ip link set dev tun0 up mtu 1500
2023-08-16T18:46:32+02:00 INFO [openvpn] /sbin/ip link set dev tun0 up
2023-08-16T18:46:32+02:00 INFO [openvpn] /sbin/ip addr add dev tun0 10.8.3.3/24
2023-08-16T18:46:32+02:00 INFO [openvpn] UID set to nonrootuser
2023-08-16T18:46:32+02:00 INFO [openvpn] Initialization Sequence Completed
2023-08-16T18:46:37+02:00 INFO [healthcheck] program has been unhealthy for 6s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)
2023-08-16T18:46:37+02:00 INFO [vpn] stopping
2023-08-16T18:46:37+02:00 ERROR [vpn] cannot get version information: Get "https://api.github.com/repos/qdm12/gluetun/commits": context canceled
2023-08-16T18:46:37+02:00 INFO [vpn] starting
2023-08-16T18:46:37+02:00 INFO [firewall] allowing VPN connection...
2023-08-16T18:46:37+02:00 INFO [openvpn] OpenVPN 2.5.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Nov  2 2022
2023-08-16T18:46:37+02:00 INFO [openvpn] library versions: OpenSSL 3.1.2 1 Aug 2023, LZO 2.10
2023-08-16T18:46:37+02:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]X.X.X.X:1194
2023-08-16T18:46:37+02:00 INFO [openvpn] UDP link local: (not bound)
2023-08-16T18:46:37+02:00 INFO [openvpn] UDP link remote: [AF_INET]X.X.X.X:1194
2023-08-16T18:46:37+02:00 INFO [openvpn] [se507.nordvpn.com] Peer Connection Initiated with [AF_INET]X.X.X.X:1194
2023-08-16T18:46:38+02:00 INFO [openvpn] TUN/TAP device tun0 opened
2023-08-16T18:46:38+02:00 INFO [openvpn] /sbin/ip link set dev tun0 up mtu 1500
2023-08-16T18:46:38+02:00 INFO [openvpn] /sbin/ip link set dev tun0 up
2023-08-16T18:46:38+02:00 INFO [openvpn] /sbin/ip addr add dev tun0 10.8.2.5/24
2023-08-16T18:46:38+02:00 INFO [openvpn] UID set to nonrootuser
2023-08-16T18:46:38+02:00 INFO [openvpn] Initialization Sequence Completed
2023-08-16T18:46:50+02:00 INFO [healthcheck] program has been unhealthy for 11s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)
2023-08-16T18:46:50+02:00 INFO [vpn] stopping
2023-08-16T18:46:50+02:00 INFO [vpn] starting
2023-08-16T18:46:50+02:00 INFO [firewall] allowing VPN connection...
2023-08-16T18:46:50+02:00 INFO [openvpn] OpenVPN 2.5.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Nov  2 2022
2023-08-16T18:46:50+02:00 INFO [openvpn] library versions: OpenSSL 3.1.2 1 Aug 2023, LZO 2.10
2023-08-16T18:46:50+02:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]X.X.X.X:1194
2023-08-16T18:46:50+02:00 INFO [openvpn] UDP link local: (not bound)
2023-08-16T18:46:50+02:00 INFO [openvpn] UDP link remote: [AF_INET]X.X.X.X:1194
2023-08-16T18:46:50+02:00 INFO [openvpn] [se545.nordvpn.com] Peer Connection Initiated with [AF_INET]X.X.X.X:1194
2023-08-16T18:46:51+02:00 INFO [openvpn] TUN/TAP device tun0 opened
2023-08-16T18:46:51+02:00 INFO [openvpn] /sbin/ip link set dev tun0 up mtu 1500
2023-08-16T18:46:51+02:00 INFO [openvpn] /sbin/ip link set dev tun0 up
2023-08-16T18:46:51+02:00 INFO [openvpn] /sbin/ip addr add dev tun0 10.8.0.5/24
2023-08-16T18:46:51+02:00 INFO [openvpn] UID set to nonrootuser
2023-08-16T18:46:51+02:00 INFO [openvpn] Initialization Sequence Completed
2023-08-16T18:47:07+02:00 INFO [healthcheck] program has been unhealthy for 16s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)
2023-08-16T18:47:07+02:00 INFO [vpn] stopping
2023-08-16T18:47:07+02:00 INFO [vpn] starting
2023-08-16T18:47:07+02:00 INFO [firewall] allowing VPN connection...
2023-08-16T18:47:07+02:00 INFO [openvpn] OpenVPN 2.5.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Nov  2 2022
2023-08-16T18:47:07+02:00 INFO [openvpn] library versions: OpenSSL 3.1.2 1 Aug 2023, LZO 2.10
2023-08-16T18:47:07+02:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]X.X.X.X:1194
2023-08-16T18:47:07+02:00 INFO [openvpn] UDP link local: (not bound)
2023-08-16T18:47:07+02:00 INFO [openvpn] UDP link remote: [AF_INET]X.X.X.X:1194
2023-08-16T18:47:07+02:00 INFO [openvpn] [se400.nordvpn.com] Peer Connection Initiated with [AF_INET]X.X.X.X:1194
2023-08-16T18:47:08+02:00 INFO [openvpn] TUN/TAP device tun0 opened
2023-08-16T18:47:08+02:00 INFO [openvpn] /sbin/ip link set dev tun0 up mtu 1500
2023-08-16T18:47:08+02:00 INFO [openvpn] /sbin/ip link set dev tun0 up
2023-08-16T18:47:08+02:00 INFO [openvpn] /sbin/ip addr add dev tun0 10.8.1.5/24
2023-08-16T18:47:08+02:00 INFO [openvpn] UID set to nonrootuser
2023-08-16T18:47:08+02:00 INFO [openvpn] Initialization Sequence Completed
2023-08-16T18:47:28+02:00 INFO [healthcheck] program has been unhealthy for 21s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)
2023-08-16T18:47:28+02:00 INFO [vpn] stopping
2023-08-16T18:47:28+02:00 INFO [vpn] starting
2023-08-16T18:47:28+02:00 INFO [firewall] allowing VPN connection...
2023-08-16T18:47:28+02:00 INFO [openvpn] OpenVPN 2.5.8 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Nov  2 2022
2023-08-16T18:47:28+02:00 INFO [openvpn] library versions: OpenSSL 3.1.2 1 Aug 2023, LZO 2.10
2023-08-16T18:47:28+02:00 INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]X.X.X.X:1194
2023-08-16T18:47:28+02:00 INFO [openvpn] UDP link local: (not bound)
2023-08-16T18:47:28+02:00 INFO [openvpn] UDP link remote: [AF_INET]X.X.X.X:1194
2023-08-16T18:47:28+02:00 INFO [openvpn] [se590.nordvpn.com] Peer Connection Initiated with [AF_INET]X.X.X.X:1194
2023-08-16T18:47:30+02:00 INFO [openvpn] TUN/TAP device tun0 opened
2023-08-16T18:47:30+02:00 INFO [openvpn] /sbin/ip link set dev tun0 up mtu 1500
2023-08-16T18:47:30+02:00 INFO [openvpn] /sbin/ip link set dev tun0 up
2023-08-16T18:47:30+02:00 INFO [openvpn] /sbin/ip addr add dev tun0 10.8.1.2/24
2023-08-16T18:47:30+02:00 INFO [openvpn] UID set to nonrootuser
2023-08-16T18:47:30+02:00 INFO [openvpn] Initialization Sequence Completed

2023-08-16T18:47:44+02:00 WARN Caught OS signal terminated, shutting down
2023-08-16T18:47:44+02:00 INFO dns ticker: terminated ✔️
2023-08-16T18:47:44+02:00 INFO updater ticker: terminated ✔️
2023-08-16T18:47:44+02:00 INFO http server: terminated ✔️
2023-08-16T18:47:44+02:00 INFO control: terminated ✔️
2023-08-16T18:47:44+02:00 INFO updater: terminated ✔️
2023-08-16T18:47:44+02:00 INFO public IP: terminated ✔️
2023-08-16T18:47:44+02:00 INFO tickers: terminated ✔️
2023-08-16T18:47:44+02:00 INFO HTTP health server: terminated ✔️
2023-08-16T18:47:44+02:00 INFO vpn: terminated ✔️
2023-08-16T18:47:44+02:00 INFO port forwarding: terminated ✔️
2023-08-16T18:47:44+02:00 INFO shadowsocks proxy: terminated ✔️
2023-08-16T18:47:44+02:00 INFO http proxy: terminated ✔️
2023-08-16T18:47:45+02:00 WARN other: group shutdown timed out: 2 out of 4 goroutines: unbound: goroutine shutdown timed out: after 400ms, public IP: goroutine shutdown timed out: after 400ms ⚠️
2023-08-16T18:47:45+02:00 INFO [routing] routing cleanup...
2023-08-16T18:47:45+02:00 INFO [routing] default route found: interface eth0, gateway 172.17.0.1, assigned IP 172.17.0.2 and family v4
2023-08-16T18:47:45+02:00 INFO [routing] deleting route for 0.0.0.0/0
2023-08-16T18:47:45+02:00 WARN Shutdown not completed gracefully: ordered shutdown timed out: other: group shutdown timed out: 2 out of 4 goroutines: unbound: goroutine shutdown timed out: after 400ms, public IP: goroutine shutdown timed out: after 400ms

[biggiesize]

Try turning DOT off and see if that helps. I'm assuming that it worked in a previous version?

[leif]

12 minutes ago, biggiesize said:

Try turning DOT off and see if that helps. I'm assuming that it worked in a previous version?

Yes it worked in the previous  version I have tried to turn of DOT and its the same issue  

[biggiesize]

56 minutes ago, leif said:

Yes it worked in the previous  version I have tried to turn of DOT and its the same issue  

Then I would probably change the repository to use :v3.35.0 instead of :latest. That should at least get you back up and running. Then I would probably open an issue with the dev. There could be a new feature or bug that I'm not aware of.

 

https://github.com/qdm12/gluetun-wiki/issues/new

[leif]

38 minutes ago, biggiesize said:

Then I would probably change the repository to use :v3.35.0 instead of :latest. That should at least get you back up and running. Then I would probably open an issue with the dev. There could be a new feature or bug that I'm not aware of.

 

https://github.com/qdm12/gluetun-wiki/issues/new

 

I managed to solve my issue by changing the network type of my docker from Bridge to Host mode and that for some unknown reason solved my problem it has always run in bridge mode before this update 

[grslc]

On 8/18/2023 at 2:43 PM, leif said:

 

I managed to solve my issue by changing the network type of my docker from Bridge to Host mode and that for some unknown reason solved my problem it has always run in bridge mode before this update 

I had the same problem, and solved it the same way.  However, I noticed My Home Assistant VM and one of my docker containers were no longer available from WebUI after making the change.  I figured the update must have caused a port conflict somewhere, but haven't been able to figure it out.  Possibly Healthcheck?  

 

Rolled back to my previous version of Gluetun, and logs show that it is healthy now, but I still can't access the docker containers I had routed through...

Edited August 23, 2023 by grslc

[Slarti123]

Hi,

I'm using Gluetun with Surfshark and no territory restrictions.

 

Recently my connection speed decreased significantly. 

 

When I restart the container, it connects to other servers. Sometimes they are faster, sometimes not.

 

Is there a better way to receive a new IP/server with an API call or using the command line?

 

Thanks!

[Johnyb62]

On 8/18/2023 at 7:01 PM, biggiesize said:

Then I would probably change the repository to use :v3.35.0 instead of :latest. That should at least get you back up and running. Then I would probably open an issue with the dev. There could be a new feature or bug that I'm not aware of.

 

https://github.com/qdm12/gluetun-wiki/issues/new

Have the same issue, your fix got me back up & running (thanks). Case reported: here

[biggiesize]

On 8/18/2023 at 1:43 PM, leif said:

 

I managed to solve my issue by changing the network type of my docker from Bridge to Host mode and that for some unknown reason solved my problem it has always run in bridge mode before this update 

 

1 hour ago, Johnyb62 said:

Have the same issue, your fix got me back up & running (thanks). Case reported: here

I have updated the CA template for Gluetun to default to Host instead of Bridge

[Johnyb62]

20 minutes ago, biggiesize said:

 

I have updated the CA template for Gluetun to default to Host instead of Bridge

Ok but strangely :v3.35.0 runs just fine in bridge mode?

[biggiesize]

10 minutes ago, Johnyb62 said:

Ok but strangely :v3.35.0 runs just fine in bridge mode?

Now that I think about it, I am on the latest branch and running in bridge mode without issues. Odd...

[Johnyb62]

18 hours ago, biggiesize said:

Now that I think about it, I am on the latest branch and running in bridge mode without issues. Odd...

If I use the latest build (in either bridge or host) doesn't work, but qmcgaw/gluetun:v3.35.0 does (in bridge) 

[bouncing-skeptic5048]

Downgrading doesn't work for me. It keeps on restarting. Host mode works on latest, but I can't use it as I need nzbget and transmission to go through the container... Any other way to make it work?

[biggiesize]

3 hours ago, bouncing-skeptic5048 said:

Downgrading doesn't work for me. It keeps on restarting. Host mode works on latest, but I can't use it as I need nzbget and transmission to go through the container... Any other way to make it work?

Host mode should not have any effect on containers connected through Gluetun.

 

Also, you can remove the restart always from extra parameters field and it will not restart but that should only be done for testing.

[bouncing-skeptic5048]

I got it to work again on 3.35.0, but the VPN_PORT_FORWARDING=on breaks everything. I can make it work without port forwarding, but that is exactly what I need from gluetun. I am using protonvpn.

 

Also, now when I have the docker installed, it seems like all the traffic goes through it and I dont have access to the community apps anymore...

 

Any way to unbreak this?

Edited August 28, 2023 by bouncing-skeptic5048
Added text

[biggiesize]

2 hours ago, bouncing-skeptic5048 said:

I got it to work again on 3.35.0, but the VPN_PORT_FORWARDING=on breaks everything. I can make it work without port forwarding, but that is exactly what I need from gluetun. I am using protonvpn.

 

Also, now when I have the docker installed, it seems like all the traffic goes through it and I dont have access to the community apps anymore...

 

Any way to unbreak this?

Try switching back to bridge mode.

[Tarnished]

I've been having some trouble setting up GluetunVPN with IVPN as a provider.

 

I've filled only the required fiedls per the creator wiki (WIREGUARD_PRIVATE_KEY and WIREGUARD_ADDRESSES (+SERVER_CITIES)) and I'm always getting this message:

Quote

INFO [vpn] starting
INFO [firewall] allowing VPN connection...
INFO [wireguard] Using available kernelspace implementation
INFO [wireguard] Connecting to WIREGUARD_ADDRESSES (Replaced instead of the IP)
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.
INFO [healthcheck] program has been unhealthy for 6s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)

This goes on in a loop, the only thing that changes is the seconds assigned to the unhealthy state. From the list within the link in the log I think that the only acceptable blockage may my firewall, but my machine doesn't have any limitations and I don't have any kind of blockage on my router set in place ...

 

Did anyone faced this issue as well?

[foo98]

Hi. 

 

I just switched from a linux box with portainer to unraid this week. I use PIA as my VPN provider.

 

On the old system I was able to set a country (Canada or USA) as where I wanted gluetun to connect. I did all configuration using portainer.

 

Gluetun on unraid will let me set country, region, or city but it won't connect. It won't even let me look at the logs. If I leave country, region, and city blank, it will connect to a random location anywhere in the world.

 

Am I missing something regarding how to set where I want to exit PIA. Specifically I want to use cities such as Toronto, Buffalo, NY, Montreal, or countries such as USA or Canada, as well as regions such as Eastern USA and Eastern Canada. Can you please help me out.

 

Thanks

[biggiesize]

5 hours ago, fusco98 said:

Hi. 

 

I just switched from a linux box with portainer to unraid this week. I use PIA as my VPN provider.

 

On the old system I was able to set a country (Canada or USA) as where I wanted gluetun to connect. I did all configuration using portainer.

 

Gluetun on unraid will let me set country, region, or city but it won't connect. It won't even let me look at the logs. If I leave country, region, and city blank, it will connect to a random location anywhere in the world.

 

Am I missing something regarding how to set where I want to exit PIA. Specifically I want to use cities such as Toronto, Buffalo, NY, Montreal, or countries such as USA or Canada, as well as regions such as Eastern USA and Eastern Canada. Can you please help me out.

 

Thanks

The Cities, Regions, etc. are defined differently in Gluetun vs PIA. Take a look at the servers list and see what options you have available.

 

https://github.com/qdm12/gluetun-wiki/blob/main/setup/servers.md

[foo98]

Feeling dumb right now. I was using the wrong info. Once I used the correct region info it worked just fine. Thanks!!!

 

PS. For multiple regions eg. "CA Toronto, CA Ontario" it did not work...... But it does work if you don't use a space after the comma.... "CA Toronto,CA Ontario" ... Thanks again!

 

Here is a screenshot for anyone who runs into this in the future.