pikvm/pikvm

h264 / webrtc not working on ungoogled-chromium

realies opened this issue · 6 comments

realies commented

this has been going on for probably more than a year, but using ungoogled-chromium on either windows or macos can't connect via h264 / webrtc; it appears that it handshakes with janus but the screen is black and bitrate at 0kbps; any ideas what could be going wrong?

mdevaev commented

Hello. Try to use alternative STUN server: https://docs.pikvm.org/webrtc/#how-its-working

Checked on our side already.

mdevaev commented

We have tested ungoogled chromium with static WebRTC configuration in the local network without any STUN server, and it's not working too. It looks like the guys from ungoogle team broke off something necessary besides unnecessary.

The problem is not on our side, so please redirect this issue to the ungoogled chromium team. I'm sorry, but there's nothing I can do here.

Snuupy commented

since we're talking about broken webrtc I've noticed it's also broken in librewolf for a long time, haven't checked on latest but I'll do so and report back

mdevaev commented

Okay. The problem may be identical. We don't use any specific things that Google would require. I use regular Chromium and it works great. Other forks sometimes break something, for example, Vivaldi did not work for my colleague before.

Snuupy commented

I tested webrtc on librewolf and it's working. https://mozilla.github.io/webrtc-landing/gum_test.html

When I switch to webrtc on librewolf for pikvm, I get this error:

Ooops: 465 Error processing SDP [janus.js:1434:13](https://snupikvm.lan/share/js/kvm/janus.js)
    transaction https://snupikvm.lan/share/js/kvm/janus.js:1434
    handleEvent https://snupikvm.lan/share/js/kvm/janus.js:770

I also tried following these instructions https://jrballesteros05.codeberg.page/posts/librewolf/ to enable webrtc. Is there any other debugging you want me to do? I will post an issue for librewolf. (edit: https://codeberg.org/librewolf/issues/issues/1830)

It is working on firefox.

mdevaev commented

465 means that the browser has transmitted an incorrect SDP. This is really a problem inside the browser. Librewolf devs should compare the SDP that their browser generates with what Chrome generates. It is likely that some kind of discrepancy will be found leading to problems.

  • 👍1