1. Caddy version (caddy version):
v2.4.6 h1:HGkGICFGvyrodcqOOclHKfvJC0qTU7vny/7FhYp9hNw=
2. How I run Caddy:
a. System environment:
b. Command:
Paste command here.
c. Service/unit/compose file:
Paste full file contents here.
Make sure backticks stay on their own lines,
and the post looks nice in the preview pane.
d. My complete Caddyfile or JSON config:
02lc.cn {
# only one of these will happen
respond “Hello, privacy!”
reverse_proxy 127.0.0.1:3001
}
localhost {
reverse_proxy 127.0.0.1:3001
}
127.0.0.1 {
reverse_proxy 127.0.0.1:3001
}
3. The problem I’m having:
4. Error messages and/or full log output:
C:\canddy>caddy.exe run
2022/04/12 09:51:16.424 e[34mINFOe[0m using adjacent Caddyfile
2022/04/12 09:51:16.426 e[33mWARNe[0m input is not formatted with ‘caddy fmt’
{“adapter”: “caddyfile”, “file”: “Caddyfile”, “line”: 2}
2022/04/12 09:51:16.431 e[34mINFOe[0m admin admin endpoint started {“addres
s”: “tcp/localhost:2019”, “enforce_origin”: false, “origins”: [“localhost:2019”,
“[::1]:2019”, “127.0.0.1:2019”]}
2022/04/12 09:51:16.432 e[34mINFOe[0m http server is listening only on the
HTTPS port but has no TLS connection policies; adding one to enable TLS {“server
_name”: “srv0”, “https_port”: 443}
2022/04/12 09:51:16.433 e[34mINFOe[0m http enabling automatic HTTP->HTTPS r
edirects {“server_name”: “srv0”}
2022/04/12 09:51:16.433 e[34mINFOe[0m tls.cache.maintenance started backgrou
nd certificate maintenance {“cache”: “0xc000311a40”}
2022/04/12 09:51:16.435 e[34mINFOe[0m http enabling automatic TLS certifica
te management {“domains”: [“localhost”, “127.0.0.1”, “02lc.cn”]}
2022/04/12 09:51:16.437 e[33mWARNe[0m tls stapling OCSP {“error”: “no OC
SP stapling for [localhost]: no OCSP server specified in certificate”}
2022/04/12 09:51:16.438 e[33mWARNe[0m tls stapling OCSP {“error”: “no OC
SP stapling for [127.0.0.1]: no OCSP server specified in certificate”}
2022/04/12 09:51:16.440 e[34mINFOe[0m tls cleaning storage unit {“descri
ption”: “FileStorage:C:\Users\Administrator\AppData\Roaming\Caddy”}
2022/04/12 09:51:16.450 e[34mINFOe[0m tls finished cleaning storage units
2022/04/12 09:51:16.464 e[34mINFOe[0m pki.ca.local root certificate is alre
ady trusted by system {“path”: “storage:pki/authorities/local/root.crt”}
2022/04/12 09:51:16.465 e[34mINFOe[0m autosaved config (load with --resume fla
g) {“file”: “C:\Users\Administrator\AppData\Roaming\Caddy\autosave.js
on”}
2022/04/12 09:51:16.465 e[34mINFOe[0m serving initial configuration
2022/04/12 09:51:38.303 e[31mERRORe[0m tls.issuance.acme looking up info
for HTTP challenge {“host”: “02lc.cn”, “error”: “no information found to so
lve challenge for identifier: 02lc.cn”}
2022/04/12 09:51:38.303 e[31mERRORe[0m tls.issuance.acme looking up info
for HTTP challenge {“host”: “02lc.cn”, “error”: “no information found to so
lve challenge for identifier: 02lc.cn”}
2022/04/12 09:52:43.190 e[31mERRORe[0m tls.issuance.acme looking up info
for HTTP challenge {“host”: “02lc.cn”, “error”: “no information found to so
lve challenge for identifier: 02lc.cn”}
2022/04/12 09:52:43.190 e[31mERRORe[0m tls.issuance.acme looking up info
for HTTP challenge {“host”: “02lc.cn”, “error”: “no information found to so
lve challenge for identifier: 02lc.cn”}
2022/04/12 09:53:42.373 e[31mERRORe[0m tls.issuance.acme looking up info
for HTTP challenge {“host”: “02lc.cn”, “error”: “no information found to so
lve challenge for identifier: 02lc.cn”}
2022/04/12 09:53:42.373 e[31mERRORe[0m tls.issuance.acme looking up info
for HTTP challenge {“host”: “02lc.cn”, “error”: “no information found to so
lve challenge for identifier: 02lc.cn”}
2022/04/12 09:53:42.420 e[31mERRORe[0m tls.issuance.acme looking up info
for HTTP challenge {“host”: “02lc.cn”, “error”: “no information found to so
lve challenge for identifier: 02lc.cn”}
2022/04/12 09:53:42.420 e[31mERRORe[0m tls.issuance.acme looking up info
for HTTP challenge {“host”: “02lc.cn”, “error”: “no information found to so
lve challenge for identifier: 02lc.cn”}
2022/04/12 09:54:14.010 e[31mERRORe[0m tls.issuance.acme looking up info
for HTTP challenge {“host”: “02lc.cn”, “error”: “no information found to so
lve challenge for identifier: 02lc.cn”}
2022/04/12 09:54:20.700 e[31mERRORe[0m tls.issuance.acme looking up info
for HTTP challenge {“host”: “02lc.cn”, “error”: “no information found to so
lve challenge for identifier: 02lc.cn”}
2022/04/12 09:59:01.274 e[31mERRORe[0m tls.issuance.acme looking up info
for HTTP challenge {“host”: “02lc.cn”, “error”: “no information found to so
lve challenge for identifier: 02lc.cn”}
2022/04/12 09:59:01.274 e[31mERRORe[0m tls.issuance.acme looking up info
for HTTP challenge {“host”: “02lc.cn”, “error”: “no information found to so
lve challenge for identifier: 02lc.cn”}
2022/04/12 10:02:08.750 e[34mINFOe[0m shutting down {“signal”: “SIGINT”}
2022/04/12 10:02:08.750 e[33mWARNe[0m exiting; byeee!! 
{“signal”: “SIGI
NT”}
2022/04/12 10:02:10.016 e[34mINFOe[0m tls.cache.maintenance stopped backgrou
nd certificate maintenance {“cache”: “0xc000311a40”}
2022/04/12 10:02:10.018 e[34mINFOe[0m admin stopped previous server {“addres
s”: “tcp/localhost:2019”}
2022/04/12 10:02:10.019 e[34mINFOe[0m shutdown complete {“signal”: “SIGI
NT”, “exit_code”: 0}