WebRTC not working over local network

Forums / NoMachine for Windows / WebRTC not working over local network

Tagged: 

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #40766
    BriBri
    Participant

    I’m evaluating NoMachine Enterprise on my Windows system and in particular want to try out the web session feature. Since I want to stream audio from the host system, I’m trying out the beta WebRTC feature and I have it enabled in server.cfg. I’m connecting to the host system from another system running on the same local subnet, so as I understand, I shouldn’t need a STUN/TURN server set up for that since the two systems can communicate directly.

    When I connect using a web browser, I can go through the steps to start a session, and I get a notification on the host system that the screen is being viewed, but no image comes through and after about a minute I get the “Error: The WebRTC peer-to-peer communication cannot be established” error message. This happens in both Google Chrome and Firefox.

    I tried filling in info for one of Google’s public STUN/TURN servers anyway, like so:

    Section “STUN”
    Host stun1.l.google.com
    Port 19302
    EndSection

    Section “TURN”
    Host stun1.l.google.com
    Port 19302
    EndSection

    …but that didn’t fix the issue either. What do I need to do to get this working?

    #40781
    Britgirl
    Keymaster

    Hi, we found that there is an incompatibility in the way the WebPlayer uses WebRTC, with the latest WebRTC released by Google.
    They made a few changes to the WebRTC protocol and specifically changes to message IDs, that made our version incompatible.
    We’ve fixed it and this is going to be released in the next maintenance, due in the next few days.
    You can track the Trouble Report at this link: https://kb.nomachine.com/TR07T10566.

    #40786
    BriBri
    Participant

    Thanks for the info. I’ll certainly install the update when it’s available. However I am also unable to get this to work in Firefox, which suggests that there is a problem extending beyond just this specific issue with Chrome. Further, one of the copies of Chrome I’m testing with (Ungoogled Chromium 99.0.4844.84) also exhibits this problem, even though it’s apparently not affected by the change to Chrome’s WebRTC protocol.

    #41382
    BriBri
    Participant

    I’ve installed version 8.2.3 and this feature is still not working for me. If I try to connect to the NoMachine web server in the latest Chrome, I now get this error: “Uncaught DOMException: Failed to construct ‘RTCPeerConnection’: ICE server parse failed”. In Firefox I still get theError: The WebRTC peer-to-peer communication cannot be established” error.

    Can you please assist me so I can try out this feature?

    Would it be possible for me to have a trial extension?

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.