Could not connect to the server. Error is 22: Invalid argument

[bk1412]

In my company we only can use network with proxy and authentication with username and Password, before I was using [removed] on my arm Linux（oracle Cloud server, now I just found NoMachine and I great there support for proxy to connection session, but I get this problem. Someone said it this error probably with proxy. Another question is about the proxy have global proxy and every session have single proxy because I saw in the setting I can set proxy, but in the session my proxy is empty. If I set it again, won’t there be Network proxy conflict? If won’t which one proxy will be first use？

[Britgirl]

It’s not clear what your question is 🙂

There are two proxy configurations, one global (in Player Settings) and one per-connection (in Connection configuration). You can configure a proxy per session by editing the connection. Select Configuration, check “Use custom proxy configuration for this session”, click Modify and configure it according to your requirements 🙂 This does not overwrite what you already set in the general configuration in Player settings -> Security -> Proxy.

 

[bk1412]

The problem is when I set proxy try to connection my arm64 Linux, NoMachine will show error : Could not connect to the server. Error is 22: Invalid argument

proxy have authentication with user name and password

There is the log(after hidden my info)

Info: Starting NoMachine version 8.2.3.
Info: Loading settings from ‘C:/names/name/.nx\config\player.cfg’.
Info: Loaded translation files for ‘English’.
15252 3360 2023-01-31 16:47:37 411.127 Main: Creating the client session.
15252 3360 2023-01-31 16:47:37 411.127 ClientSession: Initializing session at 0x00000000032b5ca0.
15252 3360 2023-01-31 16:47:37 522.253 ClientSession: Initialized session at 0x00000000032b5ca0.
15252 3360 2023-01-31 16:47:37 522.253 ClientSession: Starting session at 0x00000000032b5ca0.
15252 3360 2023-01-31 16:47:37 522.253 ClientSession: Going to start session ‘C:\names\name\Documents\NoMachine\Tokyo.nxs’.
15252 3360 2023-01-31 16:47:37 539.563 Connection: Initializing connection at 0x0000000006927010.
15252 3360 2023-01-31 16:47:37 539.563 Connection: Initialized connection at 0x0000000006927010.
15252 3360 2023-01-31 16:47:37 539.563 Connection: Starting connection at 0x0000000006927010.
15252 3360 2023-01-31 16:47:37 539.563 ClientDaemonConnector: Starting a new connection to host ‘xxx.xyz.yz.191’ on port ‘4000’.
15252 3360 2023-01-31 16:47:37 539.563 Connection: Started connection at 0x0000000006927010.
15252 3360 2023-01-31 16:47:37 547.558 ClientSession: Started session at 0x00000000032b5ca0.
Info: Slave server running with pid 15100.
Info: Listening to slave connections on port 24545.
15252 3360 2023-01-31 16:47:37 547.558 Main: Entering the GUI event loop.
Info: Connection to 192.168.2.78 port 8080 started at 16:47:37 555.552.
15252 7308 2023-01-31 16:47:37 695.144 DaemonGreeter/DaemonGreeter: ERROR! Invalid server identification ‘
‘.
Error: Invalid server identification ‘
‘.
15252 3240 2023-01-31 16:47:37 695.144 DaemonClientApplication/DaemonClientApplication: WARNING! Session terminated abnormally.
15252 3240 2023-01-31 16:47:37 695.144 DaemonClientApplication/DaemonClientApplication: WARNING! Error is 22, ‘Invalid argument’.
Warning: Connection to 192.168.2.78 port 8080 failed at 16:47:37 695.144.
Warning: Error is 22, ‘Invalid argument’.
15252 3360 2023-01-31 16:47:37 695.144 Connection: Connection at 0x0000000006927010 failed.
15252 3360 2023-01-31 16:47:37 695.144 ClientSession: Runnable at 0x0000000006927010 caused the session at 0x00000000032b5ca0 to fail.
15252 3360 2023-01-31 16:47:37 695.144 ClientSession: Failing reason is ‘Could not connect to the server.

Error is 22: Invalid argument’.
15252 3360 2023-01-31 16:47:37 705.087 ClientSession: Stopping session at 0x00000000032b5ca0.
15252 3360 2023-01-31 16:47:37 705.087 ClientSession: Destroying display client.
Info: Slave server running with pid 14872.
Info: Listening to slave connections on port 57361.
15252 3360 2023-01-31 16:47:37 715.289 Connection: Stopping connection at 0x0000000006927010.
15252 3360 2023-01-31 16:47:37 715.289 ClientDaemonConnector: Stopping the current connection.
15252 3360 2023-01-31 16:47:37 715.289 Connection: Stopped connection at 0x0000000006927010.
15252 3360 2023-01-31 16:47:37 724.355 ClientSession: Stopped session at 0x00000000032b5ca0.

[Tom]

Hi bk1412,
is your proxy Squid, if not what is it?
Does the proxy accept connections on port 8080?
Squid has a default port of 3128.

Please configure nxplayer according to https://kb.nomachine.com/AR05S01130
It will allow us to eliminate unnecessary settings that may be the cause of the error.
Can you connect via proxy to ARM64 with the player configured in this way?

Regards,
Tom

[bk1412]

Thanks for reply. I can make sure my proxy port is 8080, and with username＆password for authentication of proxy . It’s a company public proxy, with out proxy I can normal connection my Linux in home, but in company with proxy, I cant.

[Tom]

I set up a proxy in my laboratory with a user and password, it works without a problem.

Did you try what I wrote last time?

Please configure nxplayer according to https://kb.nomachine.com/AR05S01130
It will allow us to eliminate unnecessary settings that may be the cause of the error.
Can you connect via proxy to ARM64 with the player configured in this way?

Reagards,
Tom

[Author]

Posts