I am trying to be able to use https://jdk.test and use my site with https, but I cant seem to get the certificate verification to work without an external IP, is there any way of getting around this?
4. Error messages and/or full log output:
5. What I already tried:
Tried different site names but none have worked. Lots of sudo caddy reload
Either use the DNS challenge if that’s a real domain that you own, or use tls internal or the local_certs global option to use a local CA managed by Caddy to issue the certificates.
FYI this doesn’t really make sense, because Caddy will bind on port 80, so you’ll be proxying Caddy to itself, probably causing a redirect loop (which I guess you “solved” by using auto_https disable_redirects, but I consider this a mistake here)
Thank you for your reply! It helped me get this working!
We already bind to port 80 with our development environment. We are testing out Caddy purely for the solutions where we need a certificate to work. Is there any way to only use caddy with port 443 so that I can keep our normal setup for the sites and still have access to SSL via Caddy?
Since port 80 is already allocated by our development server I get this when trying to get it to work: run: loading initial config: loading new config: http app module: start: tcp: listening on :80: listen tcp :80: bind: address already in use