Matrix chat drawer doesn't start: Element in the iframe gets 18–29 s server responses from chat.discuss.peerverity.info, then "misconfigured"
Related: #1294 (closed), #1297 (closed).
Environment: denser.discuss.peerverity.info, desktop Chrome, guest4test1, 2026-10-23 ~12:50–13:40 CEST.
What happens
- Sign in on /blog, click the chat icon.
- The drawer is black for 15–40 s, then Element shows "Your Element is misconfigured – Unexpected error while preparing the app. Open the console for details."
Reproducible after reloads. Same in a fresh incognito window without extensions, signed in with safe storage (first tries were Google Drive). So not an extension, not stale storage, not the sign-in method.
Findings
- Inside the iframe, Element's requests to chat.discuss.peerverity.info take 18–29 s:
config.chat.discuss.peerverity.info.json(404) 17.9 s,config.json?cachebuster18.1 s,languages.json28.7 s. - Timing of the 28.6 s request: Queueing 0.9 ms, Stalled 0.8 ms, Request sent 0.1 ms, Waiting for server response 28.57 s, Content download 16 ms. No ServiceWorker rows (sw.js, version 324, is registered and running, but the request didn't go through it). So the server/proxy answers late, not the browser.
- The same
config.jsonfetched bydenser-session.htmltook 133 ms, and Element opened as a normal tab (samedenser-session.html?user=@guest4test1:…&idp=oidc-denser&room=#general…&theme=darkURL) starts in ~1 s: token login, General room, sync OK. - So chat.discuss.peerverity.info is slow only for requests from the embedded Element. Maybe headers (Referer from denser,
Sec-Fetch-Dest: iframe), cookies, a proxy rule or a connection limit? Server/Caddy logs for 12:50–13:40 CEST should show it. - Element then times out on startup: iframe console shows "No bug report endpoint set – logs will not be persisted", then
undefinedfromsettled(index.ts:39/174) andundefinedfrom the startup catch (index.ts:235).
Side effect
While the broken drawer is open, Element in another tab (chat.discuss.peerverity.info) hangs at "MatrixClientPeg: waiting for MatrixClient store to initialise"; after closing the drawer it starts. Two Element instances in one browser block each other.
Expected: the drawer starts like the standalone tab, signed in as the denser user in General.
Edited by Adam Kociubinski