VPN connection made within taskcluster-vpn-proxy should be retried if initial attempts failed. There are instances where the vpn gateway returns a 504.

Oops my bad. Misclick on the save changes button. Sorry all!

This issue is different than that plaguing bug 1165759. The docker image for this can be retrieved however, if the vpn within the proxy cannot establish a connection (or the connection is lost) then there is an issue communicating with balrog.

wcosta we heard some chatter in irc that you might have a fix for this - can you provide an update?

I have linked the intermittent issues that cause a wide range of sidecar startup issues to this bug that implements a hopeful workaround: https://bugzilla.mozilla.org/show_bug.cgi?id=1307493 This particular bug is if someone with experience with openvpn wants to craft a config to attempt and test a connection. Hopefully long term this will not be needed as we will no longer need a vpn to communicate with balrog. This proxy was meant as a shorter term solution that has unfortunately lived too long.

A new docker-worker image was deployed last week that hopefully helps with some of the intermittent issues with the containers starting up the first time. That could also help with vpn connections not starting.