Webplayer ooops! error

Forum / NoMachine Terminal Server Products / Webplayer ooops! error

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
  • #26022


    I am using the latest NoMachine Terminal Server. For remote sessions in our company we use webplayer and enterprise client.
    Actually due to corona virus most of our employees are working from home via vpn connection into the company network. Unfortunately our company has some bandwidth limit/problems, we have to fight with. Within the companies network everything works fine, but if doing remote sessions from external (via vpn): the enterprise client also works well,

    but if using the webplayer, sometimes if we want to initiate a predefined session config (via URL, for example:, sometimes there is a error (see attachment), instead of the server login webpage. there we have to reload the site so long, until the login webpage will be shown.

    But sometimes it works as it should. I think there is some latency/http(s) timeout problem, or connection loss…

    Is there some config to allow more latency on session initiation in webplayer/nxhtd?



    It doesn’t look that problem is on NoMachine. It seems more like a network issue. Can you send your predefined session config to forum[at]nomachine[dot]com that we could analize if there is any problem on configuration?


    The config files are clean and the logs don’t show anything wrong with NX. The optimizations NoMachine can offer are within the session itself, not before webplayer has been fully loaded.


    Thanks for checking!

    Is there any chance to make the startup (initialization) of the webplayer less latency sensitive, so that the webplayer can handle bad network conditions? The windows client is also able to start properly with this bad conditions.

    Maybe in a future update?



    Hi termmachine,

    For version 7 (coming soon) we made some improvements, the web player should behave better when there is poor network connectivity.

Viewing 5 posts - 1 through 5 (of 5 total)

This topic was marked as solved, you can't post.