NoMachine Support

Your questions answered

Knowledge Base

Searching in: Trouble Reports
Filter the search results
Last update:
Affects:
Product:
Status:
Searching in: Trouble Reports
ID: TR04P08517
Added on: 2018-04-19
Last update: 2019-12-20
Affects: 6.0
Due to be solved in:  6.x
Platform: All Platforms
Product: NoMachine Web Player
Severity: Cosmetic
Status: Open
'Socket error' messages are printed in the nxwebclient.log when the session is terminated

The JS front-end sends further messages to the web player after the stop/close sequence. Such messages are unexpected because the communication channel is already closed and generate the following errors in the nxwebclient.log file:

12707 12707 16:07:31 925.965  NXWEBCLIENT: Socket::openConnection
Connection to port 2xxx failed with error number 111: Connection refused.
12707 12707 16:07:31 926.327  NXWEBCLIENT: Main Failed to handle event: -1.
8371 8371 08:51:24 936.544  NXWEBCLIENT: Socket::openConnection Connection
to port 23955 failed with error number 111: Connection refused.
8370 8370 08:51:25 434.262  NXWEBCLIENT: Socket::getBuffer Error while
reading on FD#4, error number 104: Connection reset by peer. 

Such messages can be safely ignored.


Notify me when the TR is closed.