Forum Replies Created
-
Posts
-
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!
That package has debug enabled so we would be interested in seeing the logs from the Macbook when you try to connect. Send logs to forum[at]nomachine…..
You can extract them using the usual instructions here: https://kb.nomachine.com/DT07S00243 (see #2 Detailed instructions)
Also, can you try connecting from your other Mac, the Mac Mini, to the Macbook instead from the iPhone?
I sent an email to the email account with which you are registered on the forums. I’ll send again.
Edited: just sent. If you have not received anything from us, reach out to us at info[at]nomachine[dot]com and we will respond from that.
Check that you have a keyboard attached to your Mac mini. That way you can see the shortcuts configurations in settings.
It could be a simple case of installing the 32-bit package instead of the one for 64-bit systems. Which package from our website did you install?
Hi,
double NAT requires configuring port-forwarding on both routers. The NoMachine Network feature, to be released with version 9, will remove the need for IP addresses, port-forwarding and interventions on the router. In the meantime, please take a look at the instructions on how to set up port-forwarding here: https://kb.nomachine.com/AR04S01122#2.
Similar topics: