Skip to content
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

code.cloudfoundry.org HTTPS certificate incorrect #503

Closed
ymorin-orange opened this issue Jan 2, 2023 · 3 comments
Closed

code.cloudfoundry.org HTTPS certificate incorrect #503

ymorin-orange opened this issue Jan 2, 2023 · 3 comments

Comments

@ymorin-orange
Copy link

ymorin-orange commented Jan 2, 2023

When trying to reach https://code.cloudfoundry.org/, the certificate presented is invalid for the code.cloudfoundry.org domain:

$ curl 'https://code.cloudfoundry.org/'
curl: (51) SSL: certificate subject name (*.de.a9sapp.eu) does not match target host name 'code.cloudfoundry.org'

This prevents fetching go packages that use code.cloudfoundry.org as a redirector; see for example this issue about vendoring Elastic Search beats

@batrov
Copy link

batrov commented Jan 3, 2023

I've got similar issue showing this error:

go: code.cloudfoundry.org/go-diodes@v0.0.0-20190809170250-f77fb823c7ee: unrecognized import path "code.cloudfoundry.org/go-diodes" (https fetch: Get https://code.cloudfoundry.org/go-diodes?go-get=1: x509: certificate is valid for *.de.a9sapp.eu, de.a9sapp.eu, not code.cloudfoundry.org)

@spgreenberg
Copy link

spgreenberg commented Jan 3, 2023

This should be fixed now. The short answer is we moved the code app to cloud run on GCP and certs should be automatically renewed. Please let me know if you run into additional problems.

The longer explanation involves the linux foundation's DNS provider limitations + EC certs being the new let's encrypt default + limitations on EC certs on a9s + an alias DNS record. I can expand if anyone cares but will save you the details of what I believe happened as this is on cloud run now.

@ymorin-orange
Copy link
Author

@spgreenberg

I can confirm that it is working on my side. 👍

Thank you for the explanations, and for the fast reply!

Happy new year (or whatever you may celebrate on your side)!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants