i am trying to add multiplayer service to my project , i am getting this error since yesterday, first i thought its service issues will be fixed in few hours, but it still shows up, i am not able to setup the configuration…please check it asap
Yo, me too. I have been stressing it was somehow my fault. Thankfully (not really) other people are having the same issue
update here if it gets fixed.
1 Like
Me too!! I cannot find the way to solve that.
they have not fixed it yet, this is frustrating
super frustrating cause only so few people are affected by this error and no one knows how to fix it.
it has not been fixed yet… are the mods looking at this?
Yeah, this problem has halted my development in it’s tracks, hopefully this is resolved soon.
We’re looking into this right now, seems it only happens to some users, and we’ve not been able to reproduce. If affected people could PM me their project ID or UNET ID and at what time they saw the error that would be helpful. Also does this happen on existing multiplayer configs which worked before? Or only new configurations?
1 Like
Im about to PM you my project ID, i just wanted to give some more information. Im not able to load the configurations of any projects even the ones i have been working with for a while (using the Unet system). But the ones i already have the multiplayer enabled are still able to use the match making services but the ones without it enable do not work, and when used for match making then the error(
) appears using the OnMatchCreated’s extended info . The tab multiplayer doesnt even load ( ) and when clicked then this error pops up ( ). I only noticed this on the 4th around 11:30 pm AEST when i went to enable match making on my new project. For now though I’m using another projects of mines project ID for multi-playing. Let me know if you more!
It’s happen to me too, really need help
1 Like
Its working for me now. Hope you all the best!
Shoutout to Iarus!!
same…
Glad it works for you guys, this affected mostly the Asia region and was caused by timeouts when authenticating the user. It’s worked around for now by icreasing the timeouts, so expect the dashboard there to be a little slow, we’ll continue working on fixing the root cause. This does not affect the matches themselves as they don’t go through this codepath, only the dashboard.
1 Like