Deployments are working for me.
I’m not sure why @enaia is getting that other error as I’ve not come across that issue, with repository not found. Think that is one for Fly.
But as regards the:
... unable to connect WireGuard tunnel: context deadline exceeded
error, which I used to get a lot and tried e.g deleting the builder and other random stuff, I’ve solved it by making sure there is a config.yml file present. If there isn’t, I get that error. As it waits several minutes and gives up. If there is, it proceeds immediately to deploy.
So look in the output of the deploy command, a bit further up. Do you see a line about a missing config.yml? It should show where it is expecting it to be found.
It seems like that config.yml is made on a successful deploy, so if you don’t have one, it may be you need to deploy until you get one, and then keep it. That is made much harder with CI builds as generally the server is made fresh each time, losing prior files, and hence this happens way more times. I persisted the config.yml to solve that:
… the other option is not using a remote builder at all, bypassing the issue. That requires you to have docker installed. If you do, great, change --remote-only to --local-only, and that will use your local docker, and so again, avoid the connection to the wireguard tunnel etc.