- This topic has 5 replies, 3 voices, and was last updated 1 year, 10 months ago by
.
-
Posts
-
Hi,
I am trying to connect to an EC2 instance of a M1 macOS instance with NoMachine version 8.2.3 (client and server). I currently use NoMachine on local instances of macOS (Big Sur and Monterey are both) without issue. I haven’t had any luck with the EC2 instance.
When trying to connect, the client just loops trying to reconnect after a protocol error. The session logs indicate there may be an issue with permissions on the display, as noted below. When connected with [remote desktop], I can see the session connecting and disconnecting via the taskbar widget messages.
Has anyone been able to get NoMachine working with EC2 instances recently and is there a setup step particular to EC2 I am missing?
Extract from session log:
Info: Connection with remote peer completed.
Info: Using link parameters 5/1/3200/25/200.
Info: Using cache parameters 16384KB/16384KB/16384KB.
Info: Using pack method dynamic with session physical-desktop.
Info: Using product MS/None.
Info: Transport running with pid 2808.
Info: Forwarded new port device connection.
Info: Forwarded new network device connection.
Info: Forwarded new smartcard device connection.
Info: Established display connection.
Info: Detected AVC decoding device with id ‘0x67df’.
20676 2808 2022-12-02 18:15:42 247.869 DXVALoadLibrary: WARNING! Failed to initialize Direct3D.
Info: H264 support is available.
Info: Forwarded new display connection.
Info: Display client for channel 9 connected on Fri Dec 02 18:15:42 2022.
Info: The session was closed before reaching a usable state.
Info: This can be due to the local display refusing access to the client.
Info: Please check authorization provided by the remote application.
Session: Session terminated at Fri Dec 02 18:15:42 2022.
20676 24876 2022-12-02 18:15:42 384.724 ClientSession: Exiting from the client transport loop.
20676 24876 2022-12-02 18:15:42 384.724 ClientSession: The transport closed with reset ‘1’ error ‘134’.
20676 24876 2022-12-02 18:15:42 384.724 ClientSession: Session at 0x035aa0b8 failed.
20676 24876 2022-12-02 18:15:42 384.724 ClientSession: Failing reason is ‘The connection with the server was lost.
Error is 134: Protocol error.’.
Thanks in advance for any direction you can provide!
I’m seeing the same issue but with a local M1 mac mini, NoMachine presents a blank screen connecting from a Windows machine to the Mac Mini.
Hi Ckapser.
Login to the machine via ssh and change the /var/tmp directory to drwxrwxrwx
Command: chmod 777 /var/tmp
After this change it will start working
Regards,
TomHi Jason-swiftnav
What macOS do you have?
What NoMchine product and version are you using?
I just checked on my hardware, the connection between Windows 10 Home 21H2 and MacOS Ventura 13.0 on Mac mini M1 works without a problem.
Regards,
TomHi Tom,
Thanks for the reply. I ended up abandoning the AWS MacOS M1 setup as the costs are still a bit higher than I would like and decided to just purchase the physical hardware. I will keep this in mind for future reference, and if I ever provision another mini on AWS I will give that a try.
Regards,
Cory
This topic was marked as solved, you can't post.