-
Notifications
You must be signed in to change notification settings - Fork 500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to connect to the same room #68
Comments
Do you have your STUN server (e.g. Twilio) set up correctly? |
I am sorry. I am not sure what's the stun server you said. I have signed up for free twilio account and got Account SID and Auth Token from the Twillio console and filled in credentials in the .env file. Then I successfully ran ngrok. Is it enough? |
Alright, if you set up twilio inside the If this doesn't work, I can investigate further :) |
Check this line decentralized-video-chat/server.js Line 81 in 4b92b8a
Only 2 people can be present in a room as per the code mentioned |
Exactly. However, OPs issue is that the second client can't join the room :) |
Any update on this? I have the same issue. The second client can not join and it seems another room is being initiated. The second room also is waiting for someone to join. |
@SaeedehAf Development of this project is halted for now. Please check the pinned issue. |
I download the code and run the project locally followed the instructions. But one room could only accommodate one user. The user who accesses the same url will be seperated. And the log would print :
PS D: decentral ized-video-chat -master> npm start
video-chat201. 0.0 start D: dachuang decentralized- video-chat- master
node server. js
http://localhost:3000
darkfox: A client joined the room
darkfox: Broadcasting ready message
darkfox: Received token request
darkfox: Error: The requested resource 2010-04-01 Accounts AC/Tokens. json was not found
The text was updated successfully, but these errors were encountered: