I've been tasked to migrate our custom multiplayer server from the legacy version, to the new azure version, since the legacy is going away, but I've hit a wall, I don't know how to solve.
Our multiplayer game server is connecting to a third-party server via websocket (443 TCP, should be), to inform our backend about the game state, get player data, and so on. This worked fine on the legacy server, but the new azure server solution simply blocks the connection attempt.
We only receive this error, but most of the time it doesn't even answer: Received websocket error: NET - The connection to the given server / port failed
I don't think it's certification problem, that is usually a different step, giving different error.
According to documentation, outgoing connections do not need to be configured, and should work out of the box.
Using Windows Containers, DV2 server, if it matters.
Thank you for your help