Forum Replies Created
-
Posts
-
May I ask for further assistance?
The above mentioned solution (edit server.cfg) worked until now, but after rebooting the server, the max resolution is locked to 1366×768 again.
After a fresh server reboot, when connecting with NoMachine, I am provided by the Lightdm login screen, then after the login, the previous lower resolution is available only, no matter what I set in the cfg file or in the client.
I double-checked the server.cfg file and it still uses the settings, I manually set based on your instruction.
I am not sure, but it seems, like lightdm (?) overrides the NoMachine server settings and does not allow NoMachine to create the display.
Before the restart, after clicking connect with the NoMachine client, I was provided by two options: to connect to ‘Display 10’ or Display 0. When I selected the first option, NoMachine connected with the proper 2560×1440 resolution.
Now, after the restart, I do not have any options in the NoMachine client to select from, but it connects straight to the lightdm login screen of the server where I have to enter my password (strange because I saved it in the client).
Any advice would be greatly appreciated!
Thank you very much, the linked article’s instructions solved the problem.
Enabled CreateDisplay 1 and set DisplayGeometry in the server.cfg and when I connect, the proper resolution comes up by default.
I have checked the resizing/scaling related documentation, but I did not find a solution for my problem.
The problem:
After newly installing the server and NoMachine, the NoMachine connection works fine, but I can not set the proper screen resolution for the server. It is a cloud/headless server, and previously this was not an issue, although now the max resolution seems locked and no matter how/what I change, I can not achieve the desired resolution to match the client screen (2560 x 1440).
It is strange, because when I connect to the server using xrdp, I can set any screen resolutions, including the desired 2560 x 1440.
The same issue exists on freshly installed Ubuntu and Arch cloud servers as well.
Can you please advise? I would like to keep using NoMachine, because xrdp connection is dead slow.
Attachments:
Unfortunately I was not able to fix this with reinstalling NoMachine, so I did reinstall the entire OS from scratch and installed NoMachine freshly and it works fine.
Although I am having a new issue, with this newly installed config: previously I was able to set practically any display resolution for the remote server, but now the maximum available, selectable display resolution is a low value and can not change it to match the client resolution. I am going to post this as a separate thread, to ask for some further help.
