koopa-admin-log/2026/2026-08-17--bonfire-chromium-login.md
2026-08-17 14:59:27 +02:00

1.8 KiB

Bonfire — Chromium login stays on homepage (2026-08-17)

Site: https://bonfire.hacktivism.ch/
Canonical: configs/bonfire/README.md (section Login in Chromium).

Symptom

  • Firefox: Log in and /login work.
  • curl https://bonfire.hacktivism.ch/login: 200, title Log in.
  • Chromium (operator profile, tab on /): Log in click does nothing; typing /login in the address bar still shows Explore local activities. Incognito/Firefox not affected.

Not the isoc account (email + username profile exist; login API ok).

Checks

Check Result
Guest / HTML data-live-socket="false"; Log in is <a href="/login" data-phx-link="redirect">
#modal opacity-0 modal-closed; modal_invisible loading stub has no CSS rule (Chromium can show a black overlay)
Bonfire JS navigator.serviceWorker.register("/pwabuilder-sw.js", {scope: "/"})
/pwabuilder-sw.js (before kill-switch) 404; hashed pwabuilder-sw-*.js exists under priv/static/
UI badge Federation disabled while container FEDERATE=true

Workaround

Unregister the worker for bonfire.hacktivism.ch in that Chromium profile (chrome://serviceworker-internals or DevTools Application), clear site data, hard reload. Then /login matches Firefox.

Host copies (optional, recreate-volatile in the image): ~/koopa-bonfire/data/branding/{pwabuilder-sw.js,hacktivism-login-fix.css,unregister-sw.js}.

Upstream

Not marked known in Bonfire GitHub (2026-08-17): no issue matches pwabuilder-sw or “service worker login”. Related PWA issues are push (#1292) and widgets (#1758), not Chromium /login hijack.

Still open locally. File a bonfire-app issue when ready: configs/bonfire/TODO-chromium-login-upstream.md.