Certificate error when visiting the embedded Juju GUI

Bug #1555083 reported by Francesco Banconi
10
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_SERVER_CERT_BAD_FORMAT)". Perhaps this indicates that the same cert number is reused across domains?
The only workaround I found is removing rm ~/.pki/nssdb/cert9.db and restarting the browser. Embedded GUI needs this to be fixed.

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
Curtis Hovey (sinzui)
tags: added: juju-gui
removed: juju-release-support
Curtis Hovey (sinzui)
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)
Revision history for this message
James Tunnicliffe (dooferlad) wrote :

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.

Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
Revision history for this message
Nicolas Thomas (thomnico) wrote :

I face the exact same issue with beta7 if rebooting the controller

env : juju 2.0-beta7 on maas1.9 (ob).

Need to reboot for agent installation to get unstuck (will fill another bug)

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 report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.