Resolve JVB crash loop — wrong MUC JID + port 8080 conflict

FixKlusterServices
Shipped
March 30, 2026 at 5:21 PM UTC
Author
Kamo
Commit
6a27c82

Two issues causing JVB to crash in a loop for 43+ hours: 1. JVB_BREWERY_MUC was **************** (full JID) but JVB appends XMPP_INTERNAL_MUC_DOMAIN automatically, creating **************** which has @ in the domain — XmppStringprepException crash. Fix: changed to just "jvbbrewery" (room name only) 2. JVB health REST API binds port 8080, which conflicts with CockroachDB's admin UI on the same hostNetwork. Jetty fails to bind → crash. Fix: changed to port 8888 via JVB_OHTTP_SERVER_PORT, updated probes Both k1m1 and k2m1 statefulsets updated.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing