We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have a coturn server running on a linode instance with the following config:
`# listening-ip=private ip external-ip=public ip tls-listening-port=5349 listening-port=3478 min-port=10000 max-port=65535
user=something:something realm=domain.online lt-cred-mech
pkey=/path/privkey.pem cert=/path/fullchain.pem
fingerprint log-file=stdout verbose
TURNSERVER_ENABLED=1`
When I try to test my coturn server on this site https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/ everything works fine on chromium 122.0.6261.57:
but on firefox 123.0 the relay does not work:
Any reason why this happens?
The text was updated successfully, but these errors were encountered:
Hi,
you might have to activate ice relay on Firefox. about:config -> media.peerconnection.ice.relay_only -> set to "true".
Regards, J.
Sorry, something went wrong.
Hello, thanks for the quick answer.
If I set that option to true I don't get anything anymore on the webrtc test
No branches or pull requests
I have a coturn server running on a linode instance with the following config:
`# listening-ip=private ip
external-ip=public ip
tls-listening-port=5349
listening-port=3478
min-port=10000
max-port=65535
user=something:something
realm=domain.online
lt-cred-mech
pkey=/path/privkey.pem
cert=/path/fullchain.pem
fingerprint
log-file=stdout
verbose
TURNSERVER_ENABLED=1`
When I try to test my coturn server on this site https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/
everything works fine on chromium 122.0.6261.57:
but on firefox 123.0 the relay does not work:
Any reason why this happens?
The text was updated successfully, but these errors were encountered: