Docs: restart Chrome after trusting the HTTPS certificate #112

Merged
littlefox merged 1 commit from issue-51-chrome-restart into main 2026-10-18 14:33:32 +00:00
Owner

Refs #51 (Android check done; iPhone check left, so this doesn't close it).

  • DOCKER.md: pick CA certificate, then force-stop Chrome; a trouble row for ERR_CERT_AUTHORITY_INVALID.
  • ROADMAP: #71 no longer part of 0.2 (D-038).

Verified the cause first: headless Chromium gets ERR_CERT_AUTHORITY_INVALID from https://192.168.0.11:8443/ without the CA and loads it (200) once the CA is in its NSS store; the user's phone worked after a Chrome restart.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XJW2ocwLunyaLiUwCBHEP8

Refs #51 (Android check done; iPhone check left, so this doesn't close it). - DOCKER.md: pick *CA certificate*, then force-stop Chrome; a trouble row for ERR_CERT_AUTHORITY_INVALID. - ROADMAP: #71 no longer part of 0.2 (D-038). Verified the cause first: headless Chromium gets ERR_CERT_AUTHORITY_INVALID from https://192.168.0.11:8443/ without the CA and loads it (200) once the CA is in its NSS store; the user's phone worked after a Chrome restart. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01XJW2ocwLunyaLiUwCBHEP8
Docs: restart Chrome after trusting the HTTPS certificate
All checks were successful
ci / check (push) Successful in 9m46s
ci / desktop (push) Successful in 11m27s
ci / e2e (push) Successful in 19m56s
8198a2c529
On the user's Android phone Chrome kept showing ERR_CERT_AUTHORITY_INVALID
after the CA was installed, until it was force-stopped. Say so in the
install steps and the trouble table. Also bring the roadmap up to date
with D-038: #71 is no longer part of 0.2.

Refs #51

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XJW2ocwLunyaLiUwCBHEP8
littlefox referenced this pull request from a commit 2026-10-18 14:33:49 +00:00
Sign in to join this conversation.
No description provided.