Just for information, after restarting for the umpteenth time, I managed to get the correct Mosquitto up and running again, and I will explain how…
The server password via Docker had been reset to zero, probably due to the numerous manipulations! At no point did I check what was behind the little dots of the password, and it had been replaced by ******.
So indeed, it couldn’t work…
I am a genius…
Well…
Actually…
No.
Maybe it’s a bug in the MQTT service, isn’t it @AlexTrovato?
At some point, the front end replaces the password content with **** right?
The front end only receives the real password if embedded MQTT is used (otherwise it’s a fake password *********). And the ability to display it is also only available for an embedded broker.
The password is randomly generated as soon as you switch to « embedded broker » mode, but it can be modified from the configuration page, which also modifies it on mosquitto.
I chose to hide the password if it is not managed by Gladys (connection to an external server).
I may have missed something, but if it needs to be fixed, my PC is all hot!
I suspect that normally there are no bugs, but this looks very much like one 
If he didn’t put « **** » in the field and it ends up in the password, then the frontend must have gotten confused at some point. Maybe during an extra click on « connect » later in the UI?
After that, it might be a legacy bug that was fixed in a recent release, but you need to be sure because it’s a scary bug 
I wouldn’t overthink it because, as a reminder, I installed Eclipse Mosquitto outside of Docker, enabled and disabled both several times, manually modified the .conf…
A conflict at some point is not impossible…
In a perfect world, this should never have happened (But we’d be in a pickle;-) )
Greetings!
I’m reviving this topic to let you know about a small recurring issue.
When the eclipse-mosquitto container is updated (I assume via Watchtower, the last time was two hours ago), I always have to re-save the MQTT server login and password in Gladys for it to work again…
Am I the only one?
Hello @GBoulvin,
No, you are not alone in this case, I have the same problem with mosquitto, but it also happens to me during EDF power outages during every storm, apparently Gladys does not know how to automatically reconnect (certainly after several unsuccessful attempts). Also, pressing the button is not enough, you have to retype the password (when I was working on the Netatmo integration, I noticed that the password became ********** in the database instead of the original password).
Indeed! To avoid this, revealing the password before clicking ‹ save configuration › works for me…
Do we have a GitHub issue for this bug?
This would help us keep track of it.
@pierre-gilles, if the credentials are « forgotten » during the container update, wouldn’t that be a bug on the side of eclipse-mosquitto? Or is it up to Gladys to verify that the information is passed to the MQTT container after an update?
To investigate In any case, it doesn’t matter if it comes from eclipse-mosquitto or Gladys, on the Gladys side, it must work!
@Terdious since your full reinstallation (x64), have you had the problem again (being prompted to re-enter the MQTT password after the container update)? It updated about a month ago…
Hi @GBoulvin,
So yes and no …
As a reminder I’m on an external mosquitto server placed on another rpi. With that clarified, during an outage:
Hoping to be clear 
^^
Isn’t a restart enough? Maybe a retry button could do the job?