You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you tested that this is not an upstream issue or an issue with your configuration?
I have tried reproducing this issue in Chrome and it could not be reproduced there
I have tried reproducing this issue in vanilla Chromium and it could not be reproduced there
I have tried reproducing this issue in ungoogled-chromium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there
Description
Webrtc does not seem to work. SDPs and ICE candidates can be generated but peer connections cannot be established
observe that the report says "Peer connection did not work"
I found this to be the case on my own project and am just using this website as it is simpler to show the problem. I just installed this browser specifically to test this so its already a new profile so I doubt creating a new profile will fix it. (and I don't understand how to do that in any case.)
Ok, you just need to set chrome://flags/#webrtc-ip-handling-policy. That was actually in the issue I linked above but I actually meant to link to another issue I read that had the same test link on it. I just read that issue I linked above now.
OS/Platform
Windows
Installed
https://ungoogled-software.github.io/ungoogled-chromium-binaries/
Version
127.0.6533.99
Have you tested that this is not an upstream issue or an issue with your configuration?
--user-data-dir
command line argument and it could not be reproduced thereDescription
Webrtc does not seem to work. SDPs and ICE candidates can be generated but peer connections cannot be established
How to Reproduce?
I found this to be the case on my own project and am just using this website as it is simpler to show the problem. I just installed this browser specifically to test this so its already a new profile so I doubt creating a new profile will fix it. (and I don't understand how to do that in any case.)
Actual behaviour
The peer connection did not work
Expected behaviour
The peer connection should work
Relevant log output
No response
Additional context
related: #2516
The text was updated successfully, but these errors were encountered: