{"id":"6a8b4cee522a0311ca0e4b66","title":"2026 08 23 Issue 357 Build 848","path":"how-to/committee/release-notes/2026-08-23-issue-357-build-848","contentMarkdown":"# 23-Aug-2026 — set Jitsi internal component secrets (jicofo/jvb auth) so the self-hosted container starts [#357](https://github.com/nbarrett/ngx-ramblers/issues/357)\n\n## [build 848](https://github.com/nbarrett/ngx-ramblers/actions/runs/32661203418) — [commit 9c9f50d](https://github.com/nbarrett/ngx-ramblers/commit/9c9f50dc4167ff530ac22130812f42890c4af8e4)\n\n_____\n\n## What's new\n\nThe self-hosted video meeting server failed to start when deployed: two of its internal services need passwords, and the deploy was not setting them, so the container stopped at start-up. The deploy now sets those passwords automatically, and the server starts first time. Nothing changes for groups using the default free public video service.\n\n## At a glance\n\n- Deploying the self-hosted video meeting server now works first time\n- The internal service passwords are set by the deploy - there is nothing to configure\n- Groups on the default public video service are unaffected","contentHtml":"

23-Aug-2026 — set Jitsi internal component secrets (jicofo/jvb auth) so the self-hosted container starts #357

\n

build 848 — commit 9c9f50d

\n
\n

What's new

\n

The self-hosted video meeting server failed to start when deployed: two of its internal services need passwords, and the deploy was not setting them, so the container stopped at start-up. The deploy now sets those passwords automatically, and the server starts first time. Nothing changes for groups using the default free public video service.

\n

At a glance

\n\n"}