Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Firefox issues: Wasm client socket doesn't connect #46

Open
connorcarpenter opened this issue Apr 21, 2022 · 1 comment
Open

Firefox issues: Wasm client socket doesn't connect #46

connorcarpenter opened this issue Apr 21, 2022 · 1 comment
Labels
bug needs fixing naia socket pertaining to naia_socket crates

Comments

@connorcarpenter
Copy link
Member

Here is an example message when attempting to run the demo on the Firefox browser

STUN-CLIENT(zcVq|IP4:192.168.1.100:42831/UDP|IP4:172.104.138.54:55501/UDP(host(IP4:192.168.1.100:42831/UDP)|candidate:1 1 UDP 4006861156 172.104.138.54 55501 typ host)): Received response; processing

STUN-CLIENT(zcVq|IP4:192.168.1.100:42831/UDP|IP4:172.104.138.54:55501/UDP(host(IP4:192.168.1.100:42831/UDP)|candidate:1 1 UDP 4006861156 172.104.138.54 55501 typ host)): XOR-MAPPED-ADDRESS is bogus

STUN-CLIENT(zcVq|IP4:192.168.1.100:42831/UDP|IP4:172.104.138.54:55501/UDP(host(IP4:192.168.1.100:42831/UDP)|candidate:1 1 UDP 4006861156 172.104.138.54 55501 typ host)): Error processing response: Invalid data, stun error code 0.

Should log an issue with https://github.com/kyren/webrtc-unreliable to troubleshoot this. The readme there says that Firefox WebRTC connections don't work when using a loopback address, but it's actually breaking in production.
@connorcarpenter connorcarpenter changed the title naia_socket: wasm client doesn't work on Firefox Wasm client socket doesn't work on Firefox Apr 21, 2022
@connorcarpenter connorcarpenter added naia socket pertaining to naia_socket crates bug needs fixing labels Apr 21, 2022
@FF-AntiK
Copy link
Contributor

FF-AntiK commented Apr 25, 2022 •
edited
Loading

This could have to do with IPv4 and IPv6 Address mix and match.
When connecting with Chrome, I get two STUN messages from the Server. One for IPv4 and one for IPv6.
When connecting with Firefox, I get only the IPv4 STUN message.

@connorcarpenter connorcarpenter mentioned this issue Aug 25, 2022
Open
@connorcarpenter connorcarpenter changed the title Wasm client socket doesn't work on Firefox Firefox issues: Wasm client socket doesn't connect Nov 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug needs fixing naia socket pertaining to naia_socket crates
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@connorcarpenter @FF-AntiK