You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Despite using the docker-letsencrypt image, we will get an invalid cert because we access docker on an IP, rather than a domain name.
If we were to make domain names part of this script (thus generating valid certs), then there would be a requirement that the user has provided proof of ownership through the GCP portal first, or the terraform scripts would fail.
Subsequently perhaps this is a toggle option, if provided; we will manage DNS entries too and generate a valid cert.
The text was updated successfully, but these errors were encountered:
Stono
changed the title
GoCD comes up with Invalid SSL due to be on an IP
GoCD comes up with Invalid SSL due to accessing on an IP
Mar 14, 2017
Despite using the docker-letsencrypt image, we will get an invalid cert because we access docker on an IP, rather than a domain name.
If we were to make domain names part of this script (thus generating valid certs), then there would be a requirement that the user has
provided proof of ownership
through the GCP portal first, or the terraform scripts would fail.Subsequently perhaps this is a toggle option, if provided; we will manage DNS entries too and generate a valid cert.
The text was updated successfully, but these errors were encountered: