Certificate error when visiting the embedded Juju GUI
Bug #1555083 reported by
Francesco Banconi
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
James Tunnicliffe |
Bug Description
The first time an lxd controller is bootstrapped on the embedded-gui branch, the GUI can be opened without problems, after accepting the self-signed certificate.
After that, if you destroy the controller, and bootstrap again, visiting the GUI URL with the browser returns an error.
For instance, in chrome the error is "SSL connection error (ERR_SSL_
The only workaround I found is removing rm ~/.pki/
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → 2.0-beta3 |
tags: | added: juju-release-support |
tags: | removed: juju-release-support |
tags: | added: juju-release-support lxd |
tags: |
added: juju-gui removed: juju-release-support |
Changed in juju-core: | |
milestone: | 2.0-beta3 → 2.0-beta4 |
tags: | added: 2.0-count |
Changed in juju-core: | |
status: | Triaged → In Progress |
assignee: | nobody → James Tunnicliffe (dooferlad) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta4 → none |
milestone: | none → 2.0-beta4 |
To post a comment you must log in.
This is because we generate a certificate that looks too similar to the last one that we generated. Putting the model UUID in the subject field fixes this.