chore: renew Southwark SSL certs #3529
Merged
Conversation
This file contains 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
|
Removed vultr server and associated DNS entries |
DafyddLlyr
approved these changes
Aug 17, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🤞 these look all good in AWS cert manager
Note that Southwark sends us a "Root.crt" & "ServerCertificate.crt" in addition to the "Intermediate.crt" (chain), and the "ServerCertificate" is what's used here ("Root" still throws "does not match key" error!).
Also learned through this that Southwark's internal email rules were blocking any emails with the zip of certs attached, therefore had some confusion around them thinking they'd already sent things to eachother/us when nothing had actually come through - in the end Sam was able to send directly in Slack fine.