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
Reported in slack
With livekit-server 1.4.2 and Ingress 0.9.0, when I tying to send some test rtmp data to ingress, I get following error in logs:
ERROR ingress service/handler.go:120 ingress failed {"nodeID": "NE_Caea23Ygkz3s", "ingressID": "IN_AgLrhaGk9jhP", "ingressID": "IN_AgLrhaGk9jhP", "error": "unauthorized: no permissions to access the room"}
This happens if ws_url has a trailing slash like wss://livekit.example.com/. Removing the trailing slash appears to fix the auth error above.
ws_url
wss://livekit.example.com/
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Reported in slack
With livekit-server 1.4.2 and Ingress 0.9.0, when I tying to send some test rtmp data to ingress, I get following error in logs:
This happens if
ws_url
has a trailing slash likewss://livekit.example.com/
. Removing the trailing slash appears to fix the auth error above.The text was updated successfully, but these errors were encountered: