So after the shutdown of Hathora, we had to disable our UBA solution with them of containerized agents only being used for compilation tasks. I set out to try and recreate the situation using docker and wine with the necessary changes (such as https://github.com/EpicGames/UnrealEngine/blob/5\.7\.4\-release/Engine/Source/Programs/Horde/Docs/Deployment/Agent.md\#linux\-and\-wine). Now I’ve gotten to the point where these docker containers can connect to our Horde server, do all the setup and are available as an agent, but whenever I attempt to send UBA work to them, they timeout on the process and just keep closing the lease in a never ending loop. Obviously there’s a lot of variables here and most of them are probably not on your guys side of the fence, but if there’s any assistance in trying to figure out exactly why I’m getting time outs when the connection looks ready to go I’d be really grateful! Attached logs to this.
Hello, are you able to test that the UBA initiator can connect to the agent at the IP listed in the container log (“<agent ip>”)?
After checking that, I would check the following two things:
Agent settings for computeIp and computePort, since when they are not set, the system will try to resolve them automatically, and this may not be a suitable address.
That port range 7000-7010 is open on the agents, as this is a listed prerequisite in the Horde UBA Remote Compilation tutorial.
It was the port range that unblocked me into the next step. I didn’t have 7002 open which is what I had chosen for the UbaProxyPort. Once it was open I got a full UBAAgent.exe call. I’m running into some other issues now, but I have leads on it to follow up already. Thanks!