I'm using a random domain that I want to get configured locally with https: *.local.co. I have been using http for everything, but I see that I can use locally signed certificates for it, and that seems nice with Chrome and other browsers that usually redirect to https unless the address is specifically written with http://.
To get this working so far I have this in my docker containers:
This works nicely. I do get https connections, but at this moment it's with a banner of chrome that this is an unsafe HTTPS connection.
I found that you can add the local authority certificate to the local trust store with the caddy commandline tool
caddy trust --address <my-server>:2019
However, when exec-ing into the container, and running curl -L localhost:2019/config, I can see that it's only exposed to tcp/localhost:2019 and not to tcp/<my-server>:2019.
I'm using a random domain that I want to get configured locally with https:
*.local.co. I have been using http for everything, but I see that I can use locally signed certificates for it, and that seems nice with Chrome and other browsers that usually redirect tohttpsunless the address is specifically written withhttp://.To get this working so far I have this in my docker containers:
or
This works nicely. I do get https connections, but at this moment it's with a banner of chrome that this is an unsafe HTTPS connection.
I found that you can add the local authority certificate to the local trust store with the caddy commandline tool
However, when exec-ing into the container, and running
curl -L localhost:2019/config, I can see that it's only exposed totcp/localhost:2019and not totcp/<my-server>:2019.This is supposed to be set with
CADDY_ADMINenv var, but when set, this doesn't apply to the config settings.What can we do here?