Add SAN to *.docker.amazee.io certificate to avoid invalid certificate issues

[uandco]

Hi,

It seems the *.docker.amazee.io certificate doesn't have SAN and triggers this error, which needs to be repeatedly added as an exception:

This server could not prove that it is project.docker.amazee.io; its security certificate does not specify Subject Alternative Names. This may be caused by a misconfiguration or an attacker intercepting your connection.

It would be great if SAN could be added. Thanks

[Mihaic100]

Hi I second this request it would be great if SAN could be added. Thanks

[rocketeerbkw]

Pygmy has support for loading trusted local certificates which bypasses this issue of browsers not trusted the included self-signed cert https://github.com/pygmystack/pygmy#generating-local-certificates-with-mkcert.

[uandco]

Pygmy has support for loading trusted local certificates which bypasses this issue of browsers not trusted the included self-signed cert https://github.com/pygmystack/pygmy#generating-local-certificates-with-mkcert.

Yes this was mentioned by @Mihaic100 in pygmystack/pygmy#381 and this works, but it would still be nice to have fully trusted certs out of the box

[rocketeerbkw]

but it would still be nice to have fully trusted certs out of the box

That's not possible, any cert we ship as an haproxy default will always be untrusted. We are more likely to improve the flow with mkcert since that's the better developer experience.