Creating caddyfile macos arm

[francislavoie]

@deletedbyadmin

I was under the impression that 80 & 443 had to be used to allow the lets encrypt do its thing by issuing the ssl cert.

Caddy will take care of handling requests on those ports appropriately before requests hit your configured routes. That handling sits transparently in front of the rest of your config. You should use ports 80/443 to serve your site, and omitting the port in your site address tells Caddy to serve the site on the default HTTPS port, i.e. 443 (and set up HTTP->HTTPS redirects on the default HTTP port, i.e. 80).

@deletedbyadmin

So would you suggest just using the caddy reverse proxy like this

caddy reverse-proxy --from example.ddns.net --to 127.0.0.1:8096

Yeah that would work, but this isn’t a great long-term solution typically, best to use a Caddyfile if you plan to leave it running long-term. To make Caddy run at startup, you might need to look into using launchd to run Caddy as a service on mac (Google is your friend here).

@deletedbyadmin

Or should i just remove everything i was trying to do and point port forward example.ddns.net 80 & 443 to 127.0.0.1:8096

No, you need something to serve the site securely over HTTPS, i.e. do the encryption between the client and server; that’s what Caddy does best.

I recommend reading this article that explains the fundamentals of serving a site from your home network:

Using Caddy as a reverse proxy in a home network

If you want to run a service inside a Local Area Network (LAN) such as your home or office – and especially if you want to be able to access it from outside that network – Caddy can help you accomplish this quite easily. This guide will show you how. It assumes you’ve never done this before, but that you have some technical proficiency and are somewhat knowledgable about your own network. Do this at your own risk. There are several ways to make private services accessible from other n…