Jicofo and Prosody containers keep restarting with fatal error "Jicofo component secret and auth password must be set"

After running docker-compose, the Jicofo and Prosody containers keep restarting every few seconds. The logs provide a fatal error. Below they are in full. The log pattern repeats identically after every restart and from what I can see they are identical for both containers (jicofo and prosody).

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-set-timezone: executing... 
[cont-init.d] 01-set-timezone: exited 0.
[cont-init.d] 10-config: executing... 
FATAL ERROR: Jicofo component secret and auth password must be set
[cont-init.d] 10-config: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

I have tried it with the currently most recent branch (1fa5048). What I don’t understand is why the error message appears in the logs, although it is only echoed in prosody/rootfs/etc/cont-init.d/10-config of the last stable branch (tags/stable-5390-3).

If I add a JICOFO_COMPONENT_SECRET to .env, the containers don’t keep restarting. However, the Websocket connection of the web interface returns 403, but that might be for another issue.

[saghul]

Do not use master unless you build the unstable images yourself. Use a release.

[FlambierterHamburger]

Hi, I had the same problem yesterday after reinstalling because of changed domains. It seems, that a recent commit broke the JiFoCo setup script. I pulled git checkout cb4d9413b7481b9767ff5d2ec09e22bdc76e74e3, deleted all config folders and made a new setup and it was working again. Hope this helps.