Replace self-signed SSL cert with a Google-managed cert#23
Merged
Conversation
phargogh
approved these changes
Mar 3, 2026
Member
phargogh
left a comment
phargogh
left a comment
There was a problem hiding this comment.
Makes sense to me! Nice to simplify things a bit, and also nice that the trusted SSL certificate is shorter/easier to implement than a self-signed certificate.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Now that we've set up the DNS record for
compute.naturalcapitalalliance.orgpointing to the load balancer static IP, we can get a Google-managed SSL certificate. This removes the "insecure connection" warning because now our certificate is from a trusted authority.