Forum / NoMachine for Windows / WebRTC not working over local network
Tagged: server.cfg, UPnP, WebRTC
- This topic has 12 replies, 2 voices, and was last updated 2 months ago by BriBri.
October 17, 2022 at 02:49 #40766
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:
…but that didn’t fix the issue either. What do I need to do to get this working?October 17, 2022 at 11:18 #40781
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.October 17, 2022 at 15:22 #40786
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.November 12, 2022 at 22:44 #41382
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?December 7, 2022 at 17:58 #41866
you can of course request an extension with the sales team if you go to the footer of this website and click Contact us -> Sales enquiries and submit your request there.
Regarding the error that you reported, we have reproduced it and would like to send you a fixed package to test. Can I assume you are using Enterprise Desktop for Windows?December 8, 2022 at 00:06 #41874
Yes, I am using Enterprise Desktop for Windows. I’d be happy to test a new version. (Though since my trial has expired I will need to obtain an extension before I can. I’ll contact the sales team for that as you suggest.)December 8, 2022 at 15:51 #41885
Okay, I’ve been given an extension to my evaluation period. Go ahead and send along the test version to try out, and I’ll report back.January 20, 2023 at 19:02 #42610
Sorry for the delay in reporting back. I just tried the test version you sent, and when I connect using HTTPS, I just get a blank screen. 🙁
I also tried updating to the current latest version 8.3.1, and have the same issue. The only error I can report is that the following gets printed to the web browser console:
Uncaught TypeError: Cannot read properties of undefined (reading ‘toLowerCase’)
at Object.z0182af5a83 [as SETTINGS] (desktop.js:1483:22223)
at Object.zfbae673a6e [as success] (desktop.js:1483:4361)
at c (desktop.js:10:28327)
at Object.fireWith [as resolveWith] (desktop.js:10:29072)
at l (desktop.js:10:79901)
at XMLHttpRequest.<anonymous> (desktop.js:10:82355)January 23, 2023 at 11:07 #42648
Clean out your cache and cookies and then try again.January 23, 2023 at 15:13 #42650
I just tried and I’m afraid it didn’t make a difference. I also tried loading the page in multiple web browsers (Chrome, Firefox and Safari) in a private window with all extensions turned off, and am still getting a blank screen.January 24, 2023 at 11:42 #42676
We’ve found a possible issue during the update procedure. Can you send us your server.cfg file from the computer you’re connecting to, so that we can check it?January 26, 2023 at 10:33 #42715
BriBri, in your server.cfg there were some changed parameters which were preventing NoMachine from working correctly (not only those which were incorrectly configured during the update), some which you changed. We are going to send it back to you, but corrected.
I will also include a freshly built package which you should download and install. Then replace the server.cfg file with the one attached to our email.
Let us know if this helps.January 27, 2023 at 18:52 #42736
I just tried out the new server.cfg and version you sent, and it works! Thank you for helping me work through this.
(I don’t know how those settings in server.cfg were changed, especially since they were obviously wrong. It seemed like some of the STUN/TURN settings I set up got mixed into the main server settings. I’m fairly certain I didn’t make those changes myself!)
This topic was marked as solved, you can't post.