Suddenly unable to connect to Normcore servers
Hey guys, as of yesterday I could connect to the servers using the same app key as I am using now.
Initially I try to connect and it gives me
Realtime: Connecting to room "AdminRoom" then Disconnected.
Eventually it throws the unable to connect error, and will ocassionally give me: Realtime (native): BidirectionalClient: Connection Error: Unable to connect to webgl-demo.normcore-matcher.normcore.io on port 3000, error: Cancelled
I have tried:
- Deleting all gameobject except the realtime
- Connecting to a different wifi network (phone hotspot) - so probably not a firewall issue
- Making a blank scene with just the realtime, same result
- Generating and trying a different app key in the blank scene, same result
Any help as to where I could start to debug this would be great!
24 Replies
Hi @NeuroGoblin. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry to hear that you're having trouble connecting to the Normcore servers. Here are a few things you could try:
1. Check your firewall settings: Normcore uses multiple cloud providers to ensure a high-quality connection for all players. If you're having trouble connecting to Normcore's servers, make sure the following IP ranges and ports are enabled. Normcore requires TCP ports 443, 3000 and UDP ports 32,768 - 65,535 to be open for all Normcore Clients. You can find more details about this in the Firewalls + Corporate Networks (https://normcore.io/documentation/architecture/firewalls) section of the Normcore documentation.
2. Check your App Key: Make sure that the App Key you're using is correct and is entered correctly in the App Key field on the Realtime component. You can create a new App Key from your account dashboard (https://normcore.io/dashboard) if needed. More details about this can be found in the Creating a Normcore application (https://normcore.io/documentation/essentials/getting-started#creating-a-normcore-application) section of the Normcore documentation.
3. Check your Unity version: Make sure you're using a compatible version of Unity. Normcore 2, for example, requires Unity 2019.1 or above. You can find more details about this in the Upgrading from Normcore 1 to Normcore 2 (https://normcore.io/documentation/guides/upgrading-from-normcore-1-to-normcore-2) section of the Normcore documentation.
4. Check your connection method: If you're using the
Connect() method to connect to a room, make sure you're passing the correct room name and app key. More details about this can be found in the Connecting to a room (https://normcore.io/documentation/realtime) section of the Normcore documentation.
If none of these suggestions help, it might be a good idea to reach out to the Normcore support team for further assistance.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------<@196555254496493568> kapa.ai is still learning and improving, please let us know how it did by reacting below
is it possible network permissions were denied for your app. this looks like it’s getting blocked at an OS level
perhaps - I am running this in the unity editor on my mac for the first time (usually use a windows PC)
i'm gonna try a webgl build and see if it can connect in the browser
same, unable to connect ( this is reading from _realtime.room.connected)
do you have code calling Disconnect? I’ve got a blank project here connected and the webgl demo on normcore.io also connects
also triple check your console, some browsers (including flavors of chromium) do not allow localhost to connect to a secure websocket
No, this scene only has a Realtime component on a blank gameobject and a textmeshpro
however it does do this on load:
but previously after the seccond connection attempt it would succeed
that’s fine that’s a benign bug in the webgl alpha
what does the browser console say?
identical to editor besides the 'waiting for client offer'
what does the network tab show?
I can see the matcher url
but no additional info
there is also this one actually
which is pending
and now finished after 39 sec
what does it show the response was after it finished?
empty
also can you do me a favor. you're on mac? can you disable wifi and turn it back on again?
there's a chromium bug we've seen where chrome thinks its offline and web sockets fail to connect
cycling wifi seems to do it
no luck, tried 2 wifi networks too
when i get home tonight i'll be able to confirm if this is isolated to the mac
given that i have the same problem in the editor it's probably not chromium related
Normcore uses libwebrtc from chromium for our native plugin
ah i see
i gotta brb for a while but i'm using MacOS Monterey 12.7.1 if that helps
my coworker on his mac m1 max was able to connect to realtime via a deployed webgl app