Forum Replies Created
-
Posts
-
The part I don’t understand is why you are forwarding the ports to the nxserver in order to use WebRTC when in fact you use WebRTC to not have to forward the ports. But it doesn’t matter 🙂
Let’s come back to the WebRTC setup…
You’ve set up your own TURN and also google’s STUN. So, we made some further tests when using google’s STUN server. We got the same errors. Apparently the STUN servers from Google work only with Google and with the Google powered WebRTC services, for reasons we don’t know. How can we investigate more? I doubt Google is going to show us their STUN servers’ configuration. We’ll be updating the documentation accordingly.
What to do? Remove Google’s STUN and try using coturn’s STUN. Coturn can be configured as both a STUN and TURN server and it works. See point 8 of the article AR07N00894. Let us know how you get on.
Hi,
server logs show:
1260 1260 2023-10-04 22:14:25 642.149 NXSERVER WARNING! Node 559f7dda-f4cc-4302-8617-351ef916b26b from session B44E42017A62285DD8CAEFCD8CC2E8E1 reported: Session with pid '1138' terminated unexpectedly.We would need logs with debug enabled to understand more clearly.
https://kb.nomachine.com/DT07S00243
Please follow the instructions in the document for the server side at the link above. When you’ve enabled debug, reproduce the same 104 error and zip up. Send them directly to forum[at]nomachine[dot]com making sure to use the title of the topic as the subject of your email. Thanks!
I would say that it is quite normal. That’s 75-80% of a single CPU core, which is possible, especially if the remote screen resolution is high.
I don’t understand. You say “There is an ubuntu server VM which has ports 3478 TCP and UDP, and UDP 49152 – 65535 forwarded to it”. Do you want to use, do you plan to use WebRTC, and so the TURN, STUN servers or not? As I said, you can connect directly to the nxserver in question, if you have the ports being forwarded to it. But if you want to use WebRTC, you must not forward the ports, and instead use the TURN, STUN servers, configuring these into the server.cfg as we said. Please, don’t forward the ports, don’t open the ports on your router, do the nxserver.cfg configuration as I said and tell us if WebRTC works.
If I understand correctly, a peer to peer connection requires open ports on both ends, which would be an issue as most people can’t open ports on their routers.
Here is where STUN kicks in, by allowing the “hole punching”, so even if there are no ports, opened beforehand, on the routers.
However, couldn’t a TURN server be bypassed entirely by having the ports open on the server and setting up WebRTC as a client-server model where only ports would need to be opened on the server?
Well, the TURN server is used when the “hole punching” fails to work, as it can happen with some routers and some router configurations. Here is where the user needs this TURN server. If you open the ports on your router, beforehand, you of course don’t need STUN (no “hole punching”, since the ports are already open) and you don’t need TURN (since the connections can be “direct” and so no need for the relay), but if you do so… Why the need to use WebRTC??? You could directly connect the browser to the NX server on the other side and connect through the opened ports! Clear the reason you need WebRTC, STUN and TURN? To not have to open the ports on your router!
Looking at your server.cfg, it does not show TURN as configured. What’s missing is this part:
Section “TURN”
Host
Port
User
PasswordEndSection
Take a look at the article “How to configure NoMachine servers to use WebRTC “.
https://kb.nomachine.com/AR07N00892Please do the configuration of WebRTC as documented there. You have the STUN server as you need, you have the TURN server as you must have, you miss nothing! It should work! Let us know 🙂
A Trouble Report has been opened for this issue which will be fixed in line with development priorities. This has not been reproduced on any of our official supported distros. Please use the following link to monitor its status.
https://www.nomachine.com/TR09U11006
The workaround for Gentoo users:
The workaround is to change the default pipewire configuration:
1) In /usr/share/pipewire/pipewire-pulse.conf change:pulse.properties = {
# the addresses this server listens on
server.address = [
//“unix:native” # -> this path is used by default
“unix:/var/run/pulse/native” # -> this path should be used for workaround2) Create a symlink /var/run/pipewire/pipewire-0 to /var/run/user/{uid}/pipewire/pipewire-0
Hi,
if we understand, you have set up the STUN server you need. Perfect, But STUN works by allowing the router “hole punching”, to make the connection work across firewalls. On the LAN, by the way, you don’t even need this “hole punching”. Regardless of this, on the LAN your connection works. The fact is that, outside the LAN, you need a way to make your connections work even if the “hole punching” is not possible, because the router “cannot be traversed”. You need a relay server, for that. You need a TURN server. Did you also set up the TURN server you need?
Sorry for not responding earlier. Do you mean that the image of the desktop is outside of the window frame?! Indeed very very strange. Can you check whether it happens in different view modes (viewport, scaling, resize etc). Does anything happen if you resize the window or move it around the desktop?
We just released 8.9, does it still happen?
There is a TR open for this problem which you can track here: https://kb.nomachine.com/TR08U10963.
A patched version is possible. Please contact us via the website (Contact us) and select General Enquiries if you are still encountering the issue.
Please update to the latest 8.9 release and tell us if the issue persists. If it does, please enable debug, try to reproduce the issue and send a complete set of logs of the failed or problematic session that you can extract using the guidelines here:
How to gather debug logs for Support requests
https://kb.nomachine.com/DT07S00243Hi, what you need is the upcoming NoMachine Network service which will be released in version 9. This will let you connect to the remote machine without having to know the IP address of the remote machine. You’ll be able to publish your computer on Network, and then by logging in with your NoMachine account and provided you have a Network Subscription, you will be able to reach that computer. Read more about it here: https://www.nomachine.com/network 🙂