1. Caddy version (caddy version
):
latest stable
2. How I run Caddy:
caddy start
curl localhost:2019/load -X POST -H "Content-Type: application/json" -d @caddy_reverse_hostname.json
With this contents:
{
"apps": {
"http": {
"servers": {
"localhost": {
"listen": [":443"],
"routes": [
{
"match": [
{
"path": ["/api/*", "/socket/*"],
"host": ["10.211.55.3", "desktop-5s36bv4.local"]
}
],
"handle": [
{
"handler": "reverse_proxy",
"upstreams": [
{
"dial": "localhost:9090"
}
]
}
]
},
{
"match": [
{
"host": ["10.211.55.3", "desktop-5s36bv4.local"]
}
],
"handle": [
{
"handler": "reverse_proxy",
"upstreams": [
{
"dial": "localhost:8080"
}
]
}
]
}
]
}
}
}
}
}
a. System environment:
Windows
b. Command:
see above.
c. Service/unit/compose file:
see above
d. My complete Caddyfile or JSON config:
see above
3. The problem I’m having:
Certificates are expiring too soon.
Since we need to share an https site on a local network via computername, we are forced to use untrusted certificates (no control on the clients). It seems that Caddy auto generated certificates expire after 1 day, so clients are forced to accept untrusted certificates once a day. It would be good to change the expiration date of the automatically generated certificates to something like a year