-
-
Notifications
You must be signed in to change notification settings - Fork 18.9k
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
WebRTC is not working on HTML5 export of Godot 4.2 Dev #80056
Comments
Is this the same as #80022? |
No, the previous one was related to HttpRequest this one is about making peer-to-peer connections using WebRTC. |
CC @dsnopek |
I need some more time to investigate, but I strongly suspect this is a bug in my addon rather than Godot itself. On my Discord, another user has been having some trouble with the Godot 4 version of the addon - I was able to fix one of their bugs, but some still remain. I'll try to find some time this week to dig deeper into it. |
Actually I made some more tests and it works properly in Chrome browser. But in Mozilla, joining a room stucks in the connecting state. I'm trying to understand what is wrong with Mozilla. |
I can't seem to be able to reproduce using the webrtc_signaling demo, tested with both Chromium and Firefox |
Godot version
4.2.dev
System information
Windows 10 - NVIDIA GeForce RTX 2080 SUPER [Version 531.29] - Godot 4.2.dev
Issue description
WebRTC is not working on HTML5 export of Godot 4.2 dev. In testing the Nakama-WebRTC demo project, I face a problem with Web export. Users get stuck in the connecting state.
Steps to reproduce
1- export the project in this link for HTML5. ( Test can be done by running the exported project locally or on a web host like itch.io.
2- configure a Nakama server with an SSL certificate and use port forwarding to secure the Nakama port
3- try to authenticate on the exported app.
4- create a room with one client and joint with another one.
5- It stucks in the connecting state.
Minimal reproduction project
NA (I didn't manipulate the original project except for port and server address)
The text was updated successfully, but these errors were encountered: