Forum Replies Created
-
Posts
-
We are still unable to reproduce the problem with resize connecting from any OS to Ubuntu 22 with Wayland. What I suggest is everyone update to the latest version (8.8) and open a new topic, not forgetting to submit logs from both NoMachine client and server sides.
“With Wayland, no flickering login screen, with X11 flickering login screen.”
Also here, this requires a new topic separate from the resize issue.
I’m running RHEL 8.8 and NoMachine 8.8.1-1. If it matters,
nx-libsandnxagentare version 3.5.99.26-1.That “3.5.99.26-1.” indicates an NX-derivative which is not from NoMachine and it could be interfering with the NoMachine software. So, uninstall the derivative and verify if the issue continues.
If it does, please check or share .xsession-errors file in user’s homedir on server, and the /var/log/messages or journalctl logs.
Both second attachments didn’t attach.
Before you do anything else, and before we investigate, I suggest updating from 8.2 to 8.8 which is the current version. Please do this on both client and server sides. A number of issues have been fixed since 8.2, such as a possible nx daemon crash.
If, after updating, you are still getting the same problem, resubmit server side logs and Player logs from the Windows machine.
There is a small bug in the NoMachine node.cfg on Fedora: there is the wrong value set for key AudioInterface during installation on Linux with Pipewire
The key is set to node.cfg: AudioInterface alsa
The workaround is to set manually “AudioInterface pipewire” and
nxserver --restartPlease try this and let us know if it helps.
This is very strange. Can you submit a screenshot showing the problem?
Logs would also be useful. You can gather both player and server side logs by following the instructions in https://kb.nomachine.com/DT07S00243. You can send the logs to forum[at]nomachine[dot]com.
Hi, NoMachine Network (www.nomachine.com/network) is very much on the roadmap and is nearing completion. It will be released in version 9. This is what you are referring to when you write “a connection can be established via the Internet”, I imagine 🙂
The portable client suitable for starting connections via USB flash/pendrive is planned. However, priority was given to other features and we are unable to provide a target version right now.
Hi, we are unable to reproduce it. Can you enable debug on the affected Windows machine, restart Windows, connect, and if the connection fails, collect logs and share them with us. We would also need the logs from the Player which cannot connect. Please follow the instructions here to enable debug: https://kb.nomachine.com/DT07S00243 (first through to fourth steps). Submit the logs to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email.
We do not have this particular model in our labs. Please update to 8.8 on both client and server so that we can investigate further. It would be helpful if you send us the logs from an affected session. Please take a look at the following document for instructions on how to gather logs for Player and Server sides. Then submit them via email to forum[at]nomachine[dot]com.
We didn’t receive the logs. Please update to the latest version (both sides) and let us know if you can reproduce the same issue by opening a new topic and providing steps to reproduce, along with logs.
Hi Tomas,
Update to the latest 8.8 and tell us if there is any improvement because some fixes have been applied to keyboard in general. Is the result the same as before?
Hardening nxhtd should follow same rules of hardening Apache. The NoMachine web server, nxhtd, is a minimal version of Apache web server currently based on httpd-2.4.56 (NoMachine v8.5 or later). The nxhtd web server has some built-in modules already preconfigured necessary for the functioning of the Web Player application. Most common configurations suitable for Apache should work also with nxhtd.
Can you print from Windows outside NoMachine sessions? If not, you probably turned off the print spooler service.
If you can print outside the NoMachine session, please submit the Player logs (see the following document on how to extract them: https://kb.nomachine.com/DT07S00243 (section Fourth Step: Collect Client Side Logs) Attach here in the topic or submit directly to forum[at]nomachine[dot]com.
Also, please state the version of NoMachine you are using on the Windows client.
What you can look for in the logs is this indicator:
ERROR! Bitrate is equal or below 0.
VCE: WARNING! Failed to set parameters.instead of these:
VCE: WARNING! Failed to init device.
VCE: WARNING! Failed to create encoder.Just a note about VP8 decoding/encoding.
Prior to the more recent update (8.7.1 for Android/iOS) the NoMachine app for iOS and Android used VP8 as the default decoding method. With 8.7.1 it is now H.264 on mobile as well(see here for more details https://kb.nomachine.com/SU07U00248).
As for the HW encoding on the Ubuntu side, there is a bit of a mess with the drivers you have installed. Is it possible for you to revert back to the drivers version you had around June 23, because logs indicate that was the time when the encoder went through initial stages of initialization (so drivers were not actually failing). Then, on the server side, in the node.cfg file set the EncoderMode key to ‘bitrate’. Then try connecting.