NoMachine Support

Your questions answered

Knowledge Base

Searching in: Trouble Reports
Filter the search results
Last update:
Searching in: Trouble Reports
ID: TR09R09819
Added on: 2020-09-02
Last update: 2020-09-02
Affects: 6
Due to be solved in:  6.x
Platform: All Platforms
Product: NoMachine Web Player
Severity: Minor
Status: Open
Web sessions freeze when run on contemporary from two browsers with and without WebRTC support

This problem occurs when the user, from the same computer, connects to the same remote desktop from a browser which supports WebRTC (e.g. Firefox or Chrome) and then from a browser which doesn't support WebRTC, like Safari.

The WebRTC session uses HTML5 real-time communication, while the other session is run with the classic web media exchange protocol.  When there are two or more web sessions working simultanously with different methods, WebRTC and classic, the WebRTC session freezes.

The temporary workaround is to run the sessions from the same computer only from browsers which support WebRTC or which don't support it.

Notify me when the TR is closed.