Forum Replies Created
-
Posts
-
Hi, I’ve split this off to start a new topic because you submitted it to a topic which was about macOS, so best to keep them separate.
It’s a bug on the server side, but this problem will be removed when v9 comes out. The default timeout will be 30 secs in version 9.
Yes, it seems there are a few issues with the latest Ubuntu and RPi5 (not NoMachine issues). You might also consider using XFCE instead of Gnome.
An update: we have to backtrack on what we last wrote. We thought we had reproduced the same issue, but it was a false allarm. It seems to be related strictly to Android Studio. We will keep investigating and update here if we find anything. I imagine you’ve already tried:
– adb kill-server
-revoke usb debugging authorisation
Hi, you said you followed the instructions in the article about headless https://kb.nomachine.com/AR03P00973 in point 4. Executing the steps there correctly shouldn’t require any further intervention.
If you stop the display server, NoMachine should start its own virtual one. What happens when you stop the display server and restart the nxserver, and then try to connect?
You also wrote ” and after a few minutes:” What happens after a few minutes? Did you mean to attach an image or show an error maybe? Please attach it using the attach tool below.
Hmm, are you able to access and zip up the VAR folder and send it to us? (C:\ProgramData\NoMachine\…)
Hi and welcome 🙂
…there should be a timeout to close the connection if client has disappeared for (say) 60 seconds.
You’re right and there is.
Try setting the following key in node.cfg on the server side:
ProxyExtraOptions timeout=30
Something for the future, the current default timeout is too long and this will change in v9.
During tests we noticed some Xorg crashes with some specified graphic card drivers when, on proxmox, the “Default” option in “Display” settings was set. Changing it to “SPICE” stopped the Xorg crashes.
Does this help in your case?
Hi, the path is C:\Program Files (x86)\NoMachine\etc\keys\host\nx_host_rsa_key.crt. Can you tell us the precise steps you took to verify the NoMachine host key certificate?
The command is correct when running it from a CMD prompt as administrator.
If you are using Powershell, try& "$ENV:ALLUSERSPROFILE\NoMachine\nxserver\nxserver.exe" --debug --enable all.We will update the documentation for Powershell users. Raising the log level in the server.cfg will be effective from the next restart.
Please try enabling debug again through the CLI on the server side host and reproduce the problem, then submit the logs to forum[at]nomachine[dot]com.
It would have been useful to see the name of the package. We test regularly on a number of hypervisor solutions and tested again on the fly with HyperV and didn’t have any issues installing Mint, which is generally considered an easy to use Linux distro by many.
No, it includes data based on earlier versions. Better for version is the following document for NoMachine products in general https://kb.nomachine.com/AR02P00966. We will be adding more documentation soon about version 8 and the upcoming version 9.
That said, 1 GB per user is certainly not right. Please show us the list of processes showing such high CPU usage. Also, logs from the ECS server host, also knowing what OS version it is would be useful as well.
Of course the keyboard is simulated, or it wouldn’t work, but the fact the OS hides that setting if a physical keyboard is not attached doesn’t depend on NoMachine 🙂
Hi, the logs were clean, so let’s try with the journalctl log from the server-side. Can you send it to us?
Hi,
hmm, strange behaviour. We can assume you have set up port-forwarding correctly. Could you uninstall, reboot. Then reinstall and reboot. Do you get the same error? If you do, we need to see debug logs from the server side computer. Please follow the instructions here and send them to forum[at]nomachine[dot]com.
https://kb.nomachine.com/DT07S00243
Please use the title of this topic as the subject of your email. Thanks!