Forum Replies Created
-
AuthorPosts
-
Bilbotine
ParticipantHello Practice,
NoMachine Free is limited to one connection.
You can check all the features and differences here: https://www.nomachine.com/everybody/nomachine-for-your-os
Bilbotine
ParticipantHello Steve,
If you need a command to know how to check if nxserver is operative, it is
nxserver --status
.If this is not what you need, can you please give us more details on what you need to do and on which platform ?
Bilbotine
ParticipantHi Strider,
In order to investigate, we need logs – can you please gather them with debug enabled?
In order to do so, follow the instructions in this document: https://kb.nomachine.com/DT07S00243. It’s valid for v9 as well.
Reboot the server, or logout and log back in.
Gather logs again, and send them to forum[at]nomachine[dot]com, making sure to reference the topic as the subject of the email.
Bilbotine
ParticipantHello Steve,
Can you answer the following questions, to help us understand better what the issue can be:
– Can you try to connect to the same server using another username ?
– Can you confirm that the server you are connecting is SBTS ?
Thank you!
Bilbotine
ParticipantHi lmvdr,
Thank you for the additional info.
We could provide you a package with a possible fix, if you are willing to try it?
If you agree, please send us an email to forum[at]nomachine[dot]com, making sure to reference the topic as the subject of the email, and we’ll send a link to the package, as soon as it’s ready.
Bilbotine
ParticipantHi Peter,
I presume you, with “make visible”, mean “how do I connect with NoMachine”. To connect you need either an IP address or a Machine Id, the latter case if you added the machine to NoMachine Network, but in any case your VMs must be “visible” on the LAN, so an IP address on the LAN must have been assigned to them.
June 5, 2025 at 14:22 in reply to: M2 Mac Mini Server – always software encoded, cpu up to 40% #53298Bilbotine
ParticipantHi weezul,
Thank you for reporting it.
This issue will be fixed in the next update.
Bilbotine
ParticipantHi lmvdr,
We are aware of the problem and are actively working on a resolution.
In the meantime, could you please confirm whether your Mac is equipped with an Intel processor?
June 5, 2025 at 13:28 in reply to: Core Dump on Arch Linux with XFCE after screen locked using xflock4 #53296Bilbotine
ParticipantHi SimpleTechGuy,
We are not able to reproduce the problem on our side, unfortunately.
From what we understand, you are connecting to the arch, thescreen lock is inside and there is a crash player with the session to that arch – or do you have the player on the arch and you are connecting to another host, and that player crashes after screen lock ?
Can you give us more details to continue the investigation ?
Bilbotine
ParticipantHi ShayMu,
Can you specify which product you’re using, what version it is, and also send us the logs so we can investigate deeper ? Please send the via email, to forum[at]nomachine[dot]com, making sure to reference the topic as the subject of the email.
If needed, here’s the procedure to collect the logs: NoMachine – Collect Server And Client Logs Manually – Knowledge Base
June 3, 2025 at 09:31 in reply to: Camera won’t work on Jetson Orin NX via using NoMachine (headless) #53251Bilbotine
ParticipantHi Haidit,
Please try to install xfce; xfce physical session should work, even without a monitor plugged.
On our side it works with NVIDIA Jetson Nana, it should be the same on your model. You can check our article “Tips for using NoMachine on NVIDIA Jetson Nano” for more info: NoMachine – Tips For Using NoMachine On NVIDIA Jetson Nano – Knowledge Base
Bilbotine
ParticipantHi graphixillusion,
Thanks for the logs, we checked them but we need more info.
Can you please gather the logs with debug enabled? In order to do so, follow the instructions in this document: https://kb.nomachine.com/DT07S00243. It’s valid for v9 as well. Reboot the server, or logout and log back in. Gather logs again, and send them.
Thanks!
Bilbotine
ParticipantGlad the issue is solved, tashin ! 🙂
Bilbotine
ParticipantHi tashin,
It looks like you have artifacts on the session, but only on linux. Please try to disable the hardware decoding in the session: Menu>Display settings>Modify>”Disable client side hardware decoding”
Let us know if it solves the issue or not!
February 6, 2025 at 11:53 in reply to: Best practices for SELinux PAM authentication parameters ? #51730Bilbotine
ParticipantHello Steve,
First, sorry for the delay in answering.
Whilst we don’t have a specific article dedicated to SELinux, NoMachine does not require any special configurations and installs out-of-the-box. All our tests are with SELinux enabled, so with the standard default settings of SELinux.
Best regards
-
AuthorPosts