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
In the past week I've recently started to run into issues with the self signed SSL certificates.
When visiting my-domain.local (moved from .dev), Google, Firefox and Safari now warn that the domain is not secure and throw the following errors:
Looking to rule out if this is an image issue or a machine issue. Has anyone came across this issue out of the blue?
The text was updated successfully, but these errors were encountered:
Hi @davidianbonner, are you setting the environment variable WEB_HOST to my-domain.local or is it still my-domain.dev?
WEB_HOST
my-domain.local
my-domain.dev
The cert authority error is expected but the subject alternative name missing is not and generally is when the Common Name (CN) in the certificate subject doesn't match the domain being visited ( https://github.com/continuouspipe/dockerfiles/blob/master/php/shared/usr/local/share/php/webserver_functions.sh#L25 ).
If it's set correctly could you let us know the docker image being used?
Sorry, something went wrong.
Hi @kierenevans thanks for your response.
Yes, WEB_HOST is set to my-domain.local as well.
Could it be related to Common Name usage being deprecated from Chrome 65 (haven't looked into other browsers yet) – https://support.google.com/chrome/a/answer/7391219?hl=en. Currently using 63 though.
Common Name
I am using quay.io/continuouspipe/php7.1-nginx:stable.
quay.io/continuouspipe/php7.1-nginx:stable
Cheers.
No branches or pull requests
In the past week I've recently started to run into issues with the self signed SSL certificates.
When visiting my-domain.local (moved from .dev), Google, Firefox and Safari now warn that the domain is not secure and throw the following errors:
Looking to rule out if this is an image issue or a machine issue. Has anyone came across this issue out of the blue?
The text was updated successfully, but these errors were encountered: