Forum Replies Created
-
AuthorPosts
-
CarinParticipant
Hi Tz0,
We cannot reproduce this issue. Did you actually uncomment the key (i.e. remove the appending #)?
CarinParticipantHi mries,
It looks like the problem is something that happens between iHD_drv_video.so and libigdgmm.so.
To avoid the problem and be able to use gdm3, please try to disable hardware decoding in nxplayer. You can disable it completely in the player.cfg. Please edit the file$HOME/.nx/config/player.cfg
and set the configuration key “Enable hardware accelerated decoding” to “disabled”.CarinParticipantHi Tz0,
Did you change the value of the key “DisplayMonitorNotifications” to: DisplayMonitorNotifications 0?
April 9, 2021 at 08:24 in reply to: Use NoMachine together with ngrok for accessing remote access on Jetson #32851CarinParticipantHi acro,
To log in to NoMachine you must use credentials of a system account you have on that host, not the ngrok dashboard credentials.
April 8, 2021 at 20:21 in reply to: Use NoMachine together with ngrok for accessing remote access on Jetson #32847CarinParticipantHi acro,
We have tested ngrok in our labs and we did not find any issue.
I kindly ask you to double-check if either hostname and port were not correct. Or perhaps the IP address changed? Thanks!CarinParticipantHi acro,
Currently, an enterprise version for ARM is not available.
You can download the free version packages for ARMv8 here: NoMachine for ARM.
Installation & configuration notes for NoMachine Linux ARM packages can be found here: https://www.nomachine.com/AR03M00842Please check this article for some additional tips:AR02R01074- Tips for using NoMachine on NVIDIA Jetson
CarinParticipantHi Meumdav,
Thank you for the update! Please check our latest version v7.4.1, and let us know whether you encounter the same problem as before. If you are able to reproduce it, please provide the steps and environment details.
The update that was left by @Britgirl in the other topic was to close the topic given that the TR was closed a few months back i.e in 7.1.3.
April 8, 2021 at 15:24 in reply to: Use NoMachine together with ngrok for accessing remote access on Jetson #32842CarinParticipantHi acro,
You may check this article:AR11L00827 – How to connect to NoMachine when the server is behind a NAT router or a firewall. If your router supports UPnP you can use this option to connect over the internet. In the article, you can find instructions on how to enable UPnP in the NoMachine server.
Please take also a look at How to get started with NoMachine – section: Using NoMachine for remote access to a computer over the internet.
If you want to forward port manually you should pass traffic to port 4000 (NX protocol), 22 (SSH protocol on Linux/MacOSX) or (4022) (SSH protocol on Windows). Follow your router instructions to know how to do that (guides you can also find on the internet, for example from here: https://portforward.com/router.htm).
CarinParticipantHi mries,
your debugging details have been removed and added as an attachment to avoid having long amounts of files content in the thread 😉
CarinParticipantHi @mymachines,
we have received your logs, but we will need additional debug logs. We kindly ask you to enable debug logs for nxnode and nxserver as described in this article: https://www.nomachine.com/DT11R00181#1.4.
The steps are the following:
1. Enable additional debug logs for nxnode and nxserver (as described in the article) .
2. Reproduce the issue.
3. Send us the new logs, node.cfg and server.cfg.Can you please send them directly to forum[at]nomachine[dot]com making sure you use the title of the topic in the subject of your email? Many thanks!
CarinParticipantHi webangel,
We are glad the issue is resolved. Thank you for letting us know!
CarinParticipantHi Peter,
Can you let us know more about what you mean by a “different screen”? Is it the screen size that looks different?
Is it possible to send us a screenshot showing the screen behavior?It would be great if you could also send server-side logs (Ubuntu PC). Please see the following article for guidance: Collect server and client logs manually. You can send the logs and screenshot directly to forum[at]nomachine[dot]com making sure you use the title of the topic in the subject of your email? Thanks!
CarinParticipantHi, ConorMcKinnon
It appears you are using a third-party product to connect to the NoMachine server. We can’t help with the third-party product. You should contact your IT admin and ask whether they have set a limit to connection numbers on NoMachine servers. Thank you!
CarinParticipantHi basstie,
Can you send us logs from the server-side, please? You can see the following article for guidance: Collect server and client logs manually.
Please send them as an attachment to forum[at]nomachine[dot]com making sure you use the title of the topic in the subject of your email. Thanks!
CarinParticipantHi webangel,
The server-side logs show that PAM does not recognize the user and nxserver cannot recognize the public key as well.
So it seems that public key is not present in~/.nx/config/authorized.crt
Can you please check if the public part of private key is fully inserted in this file and is pasted there correctly?
The command to get the public part from private key is the following:ssh-keygen -y -f ~/.ssh/id_rsa > /tmp/id_rsa.pub
In nxplayer the private key should be selected, whereas on the server-sideauthorized.crt
only the public part should be placed/inserted.
Please check all the above again, to make sure that all the information present is correct and that the private key on the client-side has the correct permissions.
It is possible that the public key might have been “damaged” while ‘sent’ to server-side.
If the login fails again, please send us both client and server-side logs. Thanks! -
AuthorPosts