biggiesize

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.

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. 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.

There needs to be a space in between each of the extra parameters. (e.g. --shm-size=1gb --network=container:GluetunVPN)

Unfortunately, the servers list is hardcoded to help with security concerns. You can find a detailed explanation here: https://github.com/qdm12/gluetun-wiki/blob/main/faq/others.md#server-information You do have the option to update the servers list yourself and add the ones you would like to connect to. You can find that information here: https://github.com/qdm12/gluetun-wiki/blob/main/setup/servers.md#update-the-vpn-servers-list

Change the HTTP_CONTROL_SERVER_PORT variable to HTTP_CONTROL_SERVER_ADDRESS and see if that works. It's on my list to update the unraid template but I haven't had much free time lately.

The templates for the Unraid appstore are not always up to date with the change logs for the actual applications. I try to keep up with them when time allows. Even if the template is not updated with the new change logs, the application will still update whenever the dev pushes updates for the application. You can always look at the github repo for the application for an up to date change log as well.

Looks like a setting from an older version of the template. Edit the container and change the icon url to this: https://raw.githubusercontent.com/DiamondPrecisionComputing/unraid-templates/master/templates/img/ddnsgopher.png

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

Try switching back to bridge mode.

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.

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

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

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

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

Can you post the full error log?

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.

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.

Did you follow the instructions when creating the config.json file and change the owner and permissions?

There is nothing that stands out as an obvious misconfiguration. The logs showing an I/O timeout will eventually occur to most users. It happening every 6 seconds generally shows when the server you're connecting to is invalid or the IP doesn't match anymore or that the server crashed. That scenario depends on how you are determining which servers to connect to. Are you specifying a single server only, a region, etc. The health check component is not optional and can not be disabled, only the variables are optional. This is by design as it leverages the docker health check. I would suggest looking into the extensive Wiki (here is the specific page on the healthcheck) or opening an issue with the dev. https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md

Correct, because that is what Gluetun defaults to. Can you post the entire log? It obfuscates all important details. I would like to rule out some other config issue.

All of the health check variables are optional but what is included in the template are the application defaults. Most of the variables that are considered optional have OPTIONAL: in the variable description.

Looks like I accidently introduced some bad XML in the last update. I just pushed an update that hopefully brings it back.

You do not need to remove the port configuration inside the qbittorrent application. Just edit the container and remove the ports there. Stop the qbittorrent container. Then add the ports to gluetun. Then once gluetun is running and healthy start qbittorrent.

A few insights: If the logs window for gluetun keeps cycling it means that the container is constantly restarting. The container defaults to restart always. This is for privacy and security reasons. If gluetun is either stopped or restarting then the containers that use gluetun for network connection all become unavailable. The usual cause for gluetun constantly restarting is a bad config or bad credentials. If you turn on advanced view (toggle in the upper right corner) when editing gluetun, you can remove the always restart flag from the extra parameters field for troubleshooting. This should be added back once troubleshooting is complete. What I noticed just from glancing at your config: VPN_ENDPOINT_PORT - Make sure this is the correct port you need to use with Wireguard Firewall should always be on unless you are troubleshooting something being blocked FIREWALL_INPUT_PORTS - This needs to be a comma separated list of the port numbers you need to access outside the VPN tunnel. No need to specify TCP or UDP. e.g. 8080,6881 The same ports in FIREWALL_INPUT_PORTS need to be added to FIREWALL_VPN_INPUT_PORTS. This is due to the way docker networking works. FIREWALL_OUTBOUND_SUBNETS - This need to be your local network IP range in CIDR format e.g. 192.168.1.0/16

I personally do not use port forwarding but the developer has an excellent Wiki. Port forwarding for PIA should be documented here: https://github.com/qdm12/gluetun/wiki/Private-internet-access