Everything ok in shared runners, but fails on our own
We have set up a gitlab runner of our own on google cloud platform and for some reason we get to UPM (Unity Package Manager) errors when the job is assigned to our runner. Every thing goes perfect in shared runners.
There shouldn't be a difference since it is using same license, same source, same image and all that stuff.
The errors are:
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [693] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #2
[Package Manager] Server::Start -- Port 55698 was selected
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #3
[Package Manager] Server::Start -- Port 55702 was selected
[Package Manager] Cannot connect to Unity Package Manager local server
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #4
[Package Manager] Server::Start -- Port 55704 was selected
[Package Manager] Cannot connect to Unity Package Manager local server
[Package Manager] Server::EnsureServerProcessIsRunning -- ReadyRequest exceeded maximum alloted time, ran for [10] seconds
[Package Manager] Server::Kill -- Server was shutdown
[Package Manager] PackageManager Server::Start -- Process restart attempt #5
[Package Manager] Server::Start -- Port 55707 was selected
[Package Manager] Could not establish a connection with the Unity Package Manager local server process. This is most likely due to a proxy or firewall configuration. Make sure the process ....
Looking online we saw that some domains have to be white listed and reachable. But I dont see a reason why machines inside GCP would not access them. We even tried ssh'ing into the runner workers as soon as they are up a ran some curl and wget agains this domains with no problems...
Any clues about what could be happening here?