-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't work with Synology nginx as it doesn't have a name #469
Comments
Sorry, by title - I mean "Issued To" field which Synology requires. |
@rightsaidfred99 I'm interested in this one. Where can you see Synology requirements? Maybe with that in mind we can contribute with a PR here. |
I was not able to find any official certificate requirements by Synology, but I noticed the subject CommonName was not set by mkcert. After setting a CN, Synology accepts the generated certificates. I just pushed an PR to add this. |
This problem seems btw very similar to #47 where iOS would not accept the rootCA if CN was not set. |
Environment
mkcert -version
): 1.4.4What you did
I can import the certificates into Synology's nginx UI. It loads okay
What went wrong
The problem occurs as the certificate generated doesn't have a name. so you can add domains and subdomains with Synology's UI. I propose that it just ads a title/name to the certificate.
The text was updated successfully, but these errors were encountered: