biggiesize

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.