Replies: 2 comments 3 replies
-
This is kind of a stupid question, but why would you setup SSL's via LetsEncrypt for something you won't be able to use later? In any case, you could use WireGuard on super cheap VPS as a server, and then WireGuard as a client on the CapRover server and expose your server to the internet, punching a whole in NAT or CNAT, whatever you have that normally blocks inbound ports 80 and 443. Once you have confirmed networking between sever and client, you can then setup Haproxy to reverse proxy all requests to port 80 and 443 to your new network interface created by WireGuard. Once that's completed, you'll have access to your CapRover server via the IP of your VPS. You can then point a domain (or domains) to this IP. This is my setup for a Raspberry Pi running Caprover. I pay $3.50/mo for a VPS with Vultr to proxy my requests to my IP using the IP of the VPS. It works quite nice, even though my Pi is on Starlink or 4G LTE internet. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
I have run into this situation where I run Caprover on an internal server. Now access from the internet on all external ports, including 80 and 443 is blocked (I had them open when installing Caprover). This prevents Certbot from renewing the certificates.
This makes a nginx health check fail, which seems to lead to other trouble (eg installing apps fails often, and I have to log in time and time again).
So my question is: can I run certbot manually to renew the certs periodically? Or can I use another (nonstandard) port perhaps? Or can I use DNS challenge instead of the HTTP challenge?
Thanks in advance for any suggestion.
Beta Was this translation helpful? Give feedback.
All reactions