Forum Replies Created
January 11, 2021 at 18:52 in reply to: Cannot detect any display running. Do you want NoMachine to create a new display #31206
Can you tell us what is your desktop environment installed on Server?
Additionally, please check following forum posts related to Manjaro Linux
This is not NoMachine issue, it is protection module in Kaspersky application.
Please check following link https://support.kaspersky.com/10947 and enable nxnode.bin in the trusted applications.
Attachments:November 12, 2020 at 19:03 in reply to: Welcome window does not open correctly after install #30327
This issue looks like problem with loading fonts. Can you check MacOS console for possible errors related to NoMachine or font loading.
Additionally can you please compress and upload here $HOME/.nx.
Can you try to grab the keyboard input in the session. You can do it in the in-session menu-panel or by pressing Ctrl + Alt + K to toggle the keyboard grabbing.October 27, 2020 at 00:10 in reply to: How does NoMachine “advertising on the network” work #30077
There is a feature request https://www.nomachine.com/FR09P03687 that could help for your case.
If I am not wrong, when you are mentioning that you dont see NoMachine server in client i am thinking that you need to enable mDNS port as well inside of firewall.
Here is the article about NoMachine used ports: https://www.nomachine.com/AR01L00770.
You are trying to download old version not available for current download.
Please see the following forum post to download latest nomachine version
I understood it is virtual machine as you have mentioned “Linux VM (Ubuntu 20.04)”.
If you Linux machine is without monitor attached probably Linux X server if forcing one resolution. Possibly you can attach hdmi dummy dongle or you can let NoMachine create a display on the fly rather than using physical one.
Try to turn off lightdm or gdm:
sudo service lightdm stop
and then restart NoMachine server:
sudo /usr/NX/bin/nxserver –restart
What i have noticed is that you are having the Ubuntu virtual machine:
– I would recommend to install hypervisor drivers and verify if your machine is able to use different resolutions.
Or You may try to switch off your X server and let NoMachine create display for you. You can stop or disable you Display Manager, and create a connection to that desktop.
Visit this link for more information about the configuration:
Can you try to disable “multi-pass encoding” in session Display Settings of NoMachine Menu Panel. https://www.nomachine.com/DT04O00140#5.1October 2, 2020 at 16:11 in reply to: Collect logs automatically and plug it to Elastic search #29780
This is not related to NoMachine software and i think that you can find all information on Elastic Search website. I can present one possible idea how all works.
- As a first thing you should install Filebeat (https://www.elastic.co/downloads/beats/filebeat) on each NoMachine server which logs have to be monitored.
Filebeat monitors the log files, collects log events, and forwards them to endpoint. Settings of logs input and endpoints outputs have to be filled in filebeat.yml – you should include there all paths of log files
NoMachine store most logs in /var/log directory, ex. /usr/NX/var/log on Linux hosts. More information about NoMachine logs you will find https://www.nomachine.com/AR10K00697, which has to be synchronized with ES and determine also where new logs will be sent (output). It can be a directly elastic search endpoint depending on what will be done with collected data next and how it has to be visualized in Kibana but, in most cases, you will want to transform this data to a more readable format for ES, ex. JSON. In that case, the best choice for your endpoint will be a Logstash.
- Logstash is a data processing pipeline and a part of ELK Stack (https://www.elastic.co/downloads/logstash). It can be installed on the same host where Elastic Search and Kibana.
To process data sent by Filebeats you have to create Logstash pipeline with sections input, filter and output. Input will a Filebeat in our case. The filter section is a place to determine how logs have to be processed. Output as an Elastic Search endpoint.
- Setup your Elastic Search and Kibana, create index patterns for corresponding NoMachine logs data.
If everything is configured correctly you should be able to find indexed new logs entries in Kibana “Discover” or Kibana “Management -> Index Management” sections.
It looks everything is OK from NoMachine side.
Please can you send output of the.
ls -la /Users/npatelv/.home/hosts
We dont have specific mouse, and we tried few other models and all buttons worked correctly.
I would like to ask you the following:
– Does all mouse buttons are working correctly on Linux client?
– What buttons are not working?
– Did you maybe reconfigured or remapped buttons?September 17, 2020 at 16:10 in reply to: Virtual Desktop : Wayland vs. X11 – Gnome Classic vs. Gnome Standard #29510
Wayland is not supported in the NoMachine virtual desktops, you can only use x11 desktops.
At the moment there is no possibility to add more Desktop types to the list, there is Feature Request for this: https://www.nomachine.com/FR09L02833.
However you can still create separate different .nxs connection file for the specific session type.
Create first connection file to start Gnome 3D as default on RHEL8 choose New Desktop and then click “Create a new virtual desktop” and select option “Save this settings in a connection file”;
Create second connection file to start Gnome Classic and then click “Create a new custom session”-> “Run the following command: env GNOME_SHELL_SESSION_MODE=classic /bin/dbus-launch –exit-with-session gnome-session –session gnome-classic” + important is to select options “Run the command in a virtual desktop” and “Save this settings in a connection file”September 11, 2020 at 17:41 in reply to: NoMachine admin page issue after load CA certificate #29453
Based on your information and the error you got we assume that you had overwrite client certificate that is not related to NoMachine Web access.
please execute following commands as root user
echo "Host:localhost" > /var/NX/nxhtd/.nx/config/client.crt cat /usr/NX/etc/keys/host/nx_host_rsa_key.crt >> /var/NX/nxhtd/.nx/config/client.crt echo "Host:127.0.0.1" >> /var/NX/nxhtd/.nx/config/client.crt cat /usr/NX/etc/keys/host/nx_host_rsa_key.crt >> /var/NX/nxhtd/.nx/config/client.crt chown nxhtd:nxhtd /var/NX/nxhtd/.nx/config/client.crt chmod 600 /var/NX/nxhtd/.nx/config/client.crt