Red lock screen appears. Unclear what the reason is #56
Comments
Thanks for your report. The lock screen is rendered by the (independently running) browser engine when it looses the connection to the main SEB component. The two applications communicate with one another via a WebSocket connection on the local host. The exact reason why the lock screen is rendered should be logged in the browser engine log (written to file |
If that school has proxy settings set in Windows, localhost (127.0.0.1) needs to be in the domain exception list (sometimes called "bypass proxy for these domains"). Otherwise the lock screen is always displayed and SEB will only work in the "unconnected" state. |
@dbuechel and @danschlet, a big thank you for your timely and helping replies. |
@ramonavic did you ever resolve this? We are experiencing exactly the same issue. |
@jduminy in the end we didn't solve this but the system admin of the related school did. They made a proxy exception for our domain and made a hole in their firewall for our application IP. Hopefully this helps, good luck! |
Red lock screen appears on launch
Description
Dear SEB,
First of all, we use SEB on various schools and get a lot of positive feedback on your application.
On one of our schools there seems to be a uniform problem where on startup SEB shows the red lock screen implemented in the 2.2.1 release.
This happened to about 80% in a group with the same devices and only on the startup of the SEB client.
After entering the lock password most students said they were able to continue in an "unconnected"
state (show in red in the upper left of the browser).
We have recovered two log files from the school in question but can't see any lead to what may have triggered this lock state.
Would you be able to explain why this occurs and what we can do against it?
SebClient (3).log
SebClient (2).log
Environment & Version
OS-Version: 10
SEB-Version: 2.2.6817.21388
The text was updated successfully, but these errors were encountered: