brettpennings Dev Tracker | devtrackers.gg

Tweet reply

Comment

03 Jan 21:09 brettpennings on Steam Forums - Thread - Direct

Okay, this IS interesting. It appears to be an issue on the Azure side then, because clearly your request is reaching their servers. I'm attempting to pay them for technical support but it saying it's currently unavailable. I will keep trying and we will figure this out!!

Brett

03 Jan 21:06 brettpennings on Twitter

Comment

02 Jan 19:34 brettpennings on Steam Forums - Thread - Direct

Assuming that doesn't work, would you be able to run a command for me and report back what it returns?

tracert matchmaker.magequit.com

Comment

02 Jan 19:16 brettpennings on Steam Forums - Thread - Direct

Okay, I expected everything mentioned except for that last part about it not working for your other provider as well.

I've loosened up the Azure firewall restrictions for the matchmaking VM just to see if that makes a difference at all for you. Please let me know if the responses are any different (or if Online magically works for you now).

If not, I'm going to open up a support ticket with the Azure team to see if something could be causing this on their end.

Thank you for your patience!!

Brett

Comment

02 Jan 14:54 brettpennings on Steam Forums - Thread - Direct

Yes, it could also be that -- the ports aren't terribly unusual though. The matchmaker cycles between ports 80 and 8081 each version update. (I'm sure 80 isn't blocked as that's web default)

IP address is 40.121.22.148 or matchmaker.magequit.com

I'm curious what you get if you visit that address in your browser. I receive ERR_EMPTY_RESPONSE which is what the matchmaker is programmed to return when sent an unrecognized request (in this case a standard GET). I imagine your browser will not be able to resolve the address if it is indeed an issue with your ISP. If it is a DNS resolution issue, than you'd receive a different response for visiting the IP address vs the named address, but I doubt this is the case.

Who is your internet service provider if you don't mind me asking?

Hope this helps.

Brett

Comment

02 Jan 00:03 brettpennings on Steam Forums - Thread - Direct

Hey!

We've only seen this happen a handful of times, and what we've narrowed it down to is either parental controls that block our matchmaker's IP (you would know if you had this), or, what's more likely, is that your internet service provider is unable to properly make a connection to our matchmaker. I believe this has only been an issue with Comcast/Xfinity, and it's very rare. You can attempt to hotspot your phone and connect to see if the matchmaker is available that way (I don't recommend playing like that, it would just be to verify that it has something to do with your ISP). How this has been fixed in the past is EVENTUALLY the ISP fixes its issue and it ends up working. It's a mystery to me how or why this happens, and how it miraculously fixes itself.

It probably won't help, but this guy had the same issue as you are describing: ... Read more