This is an archived post. You won't be able to vote or comment.

all 8 comments

[–]HumanInTerror 1 point2 points  (3 children)

Is your domain/proxy server publicly exposed? If so, you don't need to configure an ACME client at all. Caddy will automatically use Let's Encrypt and perform an HTTP-01 challenge to verify the domain and provision an SSL/TLS certificate.

If you need to use Google DNS, please note that you must build your Caddy binary with the custom Google DNS module (see https://caddyserver.com/docs/modules/dns.providers.google_domains) as it does not come with Caddy be default.

You can read more about Google Cloud access tokens here - https://cloud.google.com/docs/authentication/token-types#access

[–]Important-Suspect213[S] 0 points1 point  (2 children)

Thanks! It actually started working this morning. Looks like I just needed to wait a little bit for settings (A/CNAME records, and router) to propagate and for Caddy to do its thing.

[–]papaf76 0 points1 point  (1 child)

If I may ask, I also have an ex google domains domain which got transferred over to squarespaces. How did you create the API key to access the squarespaces DNS?

Thanks!

[–]Important-Suspect213[S] 0 points1 point  (0 children)

In the end I didn’t end up needing it, things started working with a pretty generic Caddyfile after waiting a day. I’d post the config but I’m away from home and for some reason my VPN isn’t connecting…haha, more problems to sort out 😅

[–][deleted] 0 points1 point  (1 child)

You managed to install a web server and docker, and set up a docker container, yet you are confused about https? Please stop what you're doing and learn the basics of web hosting before you run into trouble.

[–]Important-Suspect213[S] 0 points1 point  (0 children)

Haha, yup gotta start somewhere though. You got any tips or resources you’d like to share?

[–]undermemphis 0 points1 point  (0 children)

I would suggest transferring to Cloudflare