How to set up HTTPS with AWS ACM and a private IP? #1882
Replies: 1 comment
-
Hi @isaccavalcante - CapRover is designed to work on public IP addresses. It's a requirement of CapRover to work properly. Your question is very AWS specific. If you're not using CapRover's built in mechanism to enable HTTPS, you're on your own. The way you're mapping ports shows that you're completely bypassing CapRover's internal nginx container that routes the requests. Hence making CapRover fully useless. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I can't have a public IP in my caprover EC2 instance to setup SSL with LetsEncrypt. So I tried to add an ALB with ACM certificate, and updated the route53 domain to that ALB address. But that didn't seem to work.
What I noticed was that caprover kept restarting because of the DNS verification. I was able to pass that by disabling it:
But the connection was still not HTTPS after that.
I had my target groups set to 80 -> 3000 and 443 -> 3000. What am I doing wrong?
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions