I already checked the headers sent by colyseus , but there is no duplicated header.
And my local server ( from fresh install ) have no rule about allow cross origin but sent "," like the remote server

I tried with and without header ( the settings are in the main post of the thread ), put logs before the connection request (directly in the colyseus code) to display the headers, they are empty or show only my settings set but nothing about "*, *", and my local wamp server has no CORS rules ... and fresh install

Ok thanks

Same message :/

Hi , already tested , doesn't fix

Hello with my team, we have decided to switch from version 0.10 of colyseus to version 0.14.18. We manage to connect with the remote server from Unity without worries but as soon as it comes to connecting to the remote server via the website with the WEBGL application, this one displays a CORS error that I cannot get to solve , the error seems to come from the header sent by the client :

I have an other error after that

Here is the code that allows me to make the connection:

The headers in Colyseus Settings are the same in the code previously mentioned.
The secure protocole is checked.

Hope to have some help coming here , good day for you !

I do not have a solution strictly speaking to counter the problem in a "clean" way, only a way to circumvent the problem by adding a condition that would remove an element of the dictionary if it already exists

Hello at the moment I have a problem with Colyseus "Argument exception: An element with the same key already exist in the dictionary" at line 214 in Client.cs , the logs show that I left a room properly but apparently this.rooms of client.cs did not delete the key in the dictionary.
(It happens when I want to change rooms, I leave the room in progress then I join a new room, moreover the error does not trigger often and is rather random)

Thanks for help

Hi, I discovered today a bug apparently already mentioned on other forum but no solution was found.

Colyseus/Client.cs : 88

I made some changes, and I have no problem, no more bug, could you validate this code and integrate it into the original code

Thanks