We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As per https://letsencrypt.org/docs/certificate-compatibility/ some of my users on iOS 9 can no longer access my website.
It looks like my site is using the legacy keychain with the expired root:
Is there a way in mup to force let's encrypt to use the modern keychain?
The text was updated successfully, but these errors were encountered:
Looks like this would need to expose the certbot preferred-chain parameter as per electron/electron#31212 (comment)
preferred-chain
sudo certbot certonly --nginx -d <domain> --preferred-chain "ISRG Root X1"
And also we'd need to be using an appropriate version of certbot which supports this parameter.
Sorry, something went wrong.
We probably need to update to version 2 of https://github.com/nginx-proxy/acme-companion
No branches or pull requests
As per https://letsencrypt.org/docs/certificate-compatibility/ some of my users on iOS 9 can no longer access my website.
It looks like my site is using the legacy keychain with the expired root:
Is there a way in mup to force let's encrypt to use the modern keychain?
The text was updated successfully, but these errors were encountered: