pokeguru87

I just updated to the latest and now I get the following constantly in my log: [06:51:23.898979] STUBBY: Read config from file /config/stubby.yml Starting cloudflared ./run: line 7: /usr/local/bin/cloudflared: No such file or directory Stopping stubby Stopping cloudflared cloudflared: no process found It just repeats over and over, and all queries in my web browser result in Name Unresolved errors.

So some recent PIA changes have broken the Transmission_VPN docker when using PIA. There are ways to work around it. PIA changed the name of the Zips that the new versions of the Docker download to get all the various servers you can connect to. The way around this is to add a variable named "PIA_OPENVPN_CONFIG_BUNDLE" and then set the value to "openvpn", there are several other valid values, but I'd recommend going to haugene's github and look up the configure shell script for PIA to find the other ones. The other issue is PIA changed how the OpenVPN files in their bundles are named. Now they are all lower case and have underscores instead of spaces, i.e. "CA Toronto" is now "ca_toronto". So your "OPENVPN_CONFIG" needs to conform to the new naming scheme. That is it to work around PIA's recent changes. The first step, hopefully won't be necessary "soon". I have submitted an issue for it on the GitHub for the docker. The second however will need to be addressed in the Unraid template to correct the available values for that variable. My work around requires you to swap to Advanced mode in the Edit screen and edit the available values to the way the files are now named, otherwise Unraid just sets your value to blank if it isn't in the "Default Value" section for the variable (no clue why it would just throw away my manual setting like that but it is something I've encountered several times). I do have another issue, and it is tied to the recent 3.0 version of the docker. For whatever reason if the "TRANSMISSION_RATIO_LIMIT" or "TRANSMISSION_RATIO_LIMIT_ENABLED" are even included, even if the "ENABLED" one is set to false, the docker reports the port that PIA returns as closed, and consequently, like a lot of you have seen, prevents Transmission from connecting to basically any tracker, at least that has been my experience. Removing those variables outright gets it working just fine, however every time there is an update for the docker those variables get added back in Unraid and I have to go in and manually deleted them. I've turned off my auto update for that particular docker and just do it manually when I see there is an update. I believe most of the Transmission settings are supposed to be persistent now with the release of v3.0, so it might be possible to just remove the vast majority of the Transmission configuration options as Environment variables.