GreenLock asking for a wildcard cert #16
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A user reported the MeshCentral could not get a Let's Encrypt certificate and sent over the logs here: https://github.com/Ylianst/MeshCentral/issues/986.
Something of note is that he is requesting a single "remote.xxxxxxxxxxxxxxx.pl" name, but the request fails with:
{"context":"cert_issue","subject":"remote.xxxxxxxxxxxxxxx.pl","altnames":["*.xxxxxxxxxxxxxxx.pl","remote.xxxxxxxxxxxxxxx.pl"]}
Notice the wildcard name was added and I don't want it added. Looking at "GreenLock.js" the "_single" method figures out the wildcard name for any name with 2 dots of more. The manager.js then seems to add it as an altname.
Looking for guidance on how to not have the wildcard name be added to the altnames. Thanks.
My guess is that you have something misconfigured. The default behavior is NOT to use wildcards.
Try the example in the Greenlock Express README.md and make a few small changes until you get to where you'd like to be.