Repository navigation
Enable HTTPS for cloudmonitorsite.duckdns.org - #26
Merged
Merged
Conversation
|
Caution Review failedThe pull request is closed.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
ayushcmd
commented
Nov 13, 2026
ayushcmd
left a comment
ayushcmd
left a comment
Owner
Author
There was a problem hiding this comment.
domain configured HTTPS for cloudmonitorsite.duckdns.org
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
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.
Enable automated Let's Encrypt TLS on port 443 using Caddy and preserve the existing Nginx API rate limits and monitoring routes. Redirect HTTP requests for cloudmonitorsite.duckdns.org to HTTPS, preserve the forwarded scheme, and document persistent deployment configuration.
Validation: Nginx configuration passed nginx -t on the production Docker network; Caddy configuration passed caddy validate. DuckDNS resolves to the production EC2 IP. Existing loopback health checks and database volumes are unchanged.