We have our custom server program running in in the new Servers 2.0 setup, and being fed into via a Matchmaking 2.0 queue. I've verified that it all runs correctly up to the point where players connect to the server, which happens successfully.
After connecting, players send the server their session ticket, and the server attempts to call the following C# code to authenticate that session ticket:
```
PlayFabServerAPI.AuthenticateSessionTicket(new AuthenticateSessionTicketRequest()
{
SessionTicket = message.AuthTicket
}, OnAuthLocalUserResponse, (error) =>
{
Logger.Dispatch(LoggerTypes.Info, error.GenerateErrorReport());
}, uconn.ConnectionId);
```
This code works fine when running the server on our own machines, but when running inside the Thunderhead setup, that call returns an error message `/Server/AuthenticateSessionTicket: Unknown Error`
I'm kind of at a loss. Is it possible that the firewall around the custom servers is preventing these servers from contacting the PlayFab server API endpoints? This is the only PlayFabServerAPI call which our servers are currently attempting to make. Might we have missed something in our configuration?
(This is leftover flow from when we were using Matchmaking 1.0; if we weren't running using matchmaker 1.0, we would authenticate session tickets instead of validating Matchmaking 1.0 tickets. If this isn't the right way to validate that players are legitimate any more in the Matchmaking 2.0 world, it'd be handy to learn that too!)
Thanks for any advice!
