Skip to content
This repository has been archived by the owner on May 21, 2021. It is now read-only.

Red lock screen appears. Unclear what the reason is #56

Closed
1 of 2 tasks
ramonavic opened this issue Nov 7, 2018 · 5 comments
Closed
1 of 2 tasks

Red lock screen appears. Unclear what the reason is #56

ramonavic opened this issue Nov 7, 2018 · 5 comments

Comments

@ramonavic
Copy link

ramonavic commented Nov 7, 2018

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

  • Mac
  • Windows

OS-Version: 10
SEB-Version: 2.2.6817.21388

@dbuechel
Copy link
Member

dbuechel commented Nov 7, 2018

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 seb.log). "Unconnected" means that the connection to the main SEB process could not be restored, hence multiple features of SEB (like Additional Resources) won't work as long as SEB remains in that state.
A possible reason for the problem could be proxy or other related network settings or strict anti-virus software which interferes with the WebSocket communication. I recommend checking the system event logs for any suspicious entries as well as reviewing the system configuration with regard to the above mentioned inner workings of SEB.

@danschlet
Copy link
Member

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.

@ramonavic
Copy link
Author

@dbuechel and @danschlet, a big thank you for your timely and helping replies.
It sounds likely that the current proxy settings are blocking the socket service.
I will contact the school about this and suggest whitelisting localhost.
When I hear from them I will report back.

@jduminy
Copy link

jduminy commented May 14, 2019

@ramonavic did you ever resolve this? We are experiencing exactly the same issue.

@ramonavic
Copy link
Author

@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!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants