Thatâs what I thought right away, but the Gladys container is indeed active.
Yes, I just did it again 
I did the installation/configuration of z2m via Gladys +
No errors in the Mozilla console
This corresponds to the fact that the websocket is not connected (and therefore the scan will not work).
Oh great, donât hesitate if you need help.
Iâm running locally, and as mentioned, I havenât been able to detect my devices yet.
And indeed, if we can change this error message, it would be great because itâs not understandable.
The issue is that the message suggests that Gladys is down, which is not the case.
If there is really a websocket problem, I think we should address the real issue rather than asking the user to perform manipulations
@Tlse-vins Do you have this error message locally, with Gladys v4.2.3 in production?
CĂŽtĂ© Gladys Plus, the fix is being built â
Itâs perfect on my end 
Yes, thatâs exactly it.
Ok.. do you have a special network configuration, a company proxy that would block WebSockets? ^^
After refreshing the page, does it work again or not at all?
Nothing unusual on an Orange box.
After a refresh, the message disappears and comes back from time to time, but I still canât find my sensors.
Is everything green in Configuration (all containers and links)?
If you canât access port 8080, I think the zigbee2mqtt container is not running. And consequently, your devices are not associated with the Zigbee network of Gladys.
I will add information in the documentation.
What should the message have said? « Connection to Gladys Backend is lost? »
I didnât want to go into technical details.
After that, I agree with you that we should always look for the source of the problem and fix it first. But I wanted to handle all error cases.
Yes, thatâs the case. (I will take a screenshot tonight)
Same, I will check tonight but I think I had everything activated.
Indeed, itâs not necessarily easy to find a formulation that is neither too technical nor too vague, but in any case, itâs better to have an error message than nothing! Iâll think about it.
By the way, we should talk about that, I had no idea that the Zigbee2mqtt container exposes a port, how is this frontend secured? Is it open?
Yes, I think we need to investigate this subject, itâs not normal.
Where I think there is a problem is that the zigbee2mqtt front end is based on the variable « websocketsConnected », however this state is dynamic (the websocket connection disconnects naturally and then reconnects quite regularly, which is quite normal), however if the websocket reconnects, the zigbee2mqtt discover view will remain in a « broken » state. I think itâs just a lifecycle problem.
Port 8080 is exposed (on the same IP) as open. This was a convenience during development and allows people to see the zigbee2mqtt interface (to check that their devices are associated with the network). https://github.com/GladysAssistant/Gladys/blob/master/server/services/zigbee2mqtt/docker/gladys-z2m-zigbee2mqtt-env.sh#L35
But I admit that in terms of security, itâs not great 
I can make a PR to disable the frontend OR secure it with a randomly generated secret for each instance?
Securing it with a secret displayed in the Gladys UI seems good to me Be careful, you need to manage the existing instances and restart the already launched containers!
Oops, it seems there are some issues with your installation 
Should you create a specific topic on the forum to discuss this? I donât think thereâs necessarily a link with the Zigbee2mqtt integration here, if the Docker daemon isnât even accessible, the Zigbee2mqtt integration is not likely to work either ^^
In my opinion, there is a problem with your USB key setup
@Tlse-vins
The docker command is reserved for root or those in the docker group.
Try adding sudo before your docker command. If it still doesnât work, itâs because docker is not started.
No Docker starting.
I will open another post.