1. Caddy version (caddy version
):
v2.3.0
2. How I run Caddy:
batch file
a. System environment:
Windows 10
b. Command:
caddy run
c. Service/unit/compose file:
d. My complete Caddyfile or JSON config:
connormorse.com
reverse_proxy /ombi/* 192.168.0.1:5000
reverse_proxy /sonarr/* 192.168.0.2:8989
3. The problem I’m having:
Built new server and copied v1 caddyfile across but am running into issues where it is stuck on trying to solve http-01 challenge when changing to v2. v1 doesn’t work either.
4. Error messages and/or full log output:
C:\CaddyV2>caddy run
2021/04/29 11:48:20.503 ←[34mINFO←[0m using adjacent Caddyfile
2021/04/29 11:48:20.509 ←[34mINFO←[0m admin admin endpoint started {"address": "tcp/localhost:2019", "enforce_origin": false, "origins": ["localhost:2019", "[::1]:2019", "127.0.0.1:2019"]}
2021/04/29 11:48:20.509 ←[34mINFO←[0m tls.cache.maintenance started background certificate maintenance {"cache": "0xc00034e690"}
2021/04/29 11:48:20.509 ←[34mINFO←[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}
2021/04/29 11:48:20.509 ←[34mINFO←[0m http enabling automatic HTTP->HTTPS redirects {"server_name": "srv0"}
2021/04/29 11:48:20.510 ←[34mINFO←[0m http enabling automatic TLS certificate management {"domains": ["connormorse.com"]}
2021/04/29 11:48:20.510 ←[34mINFO←[0m tls cleaned up storage units
2021/04/29 11:48:20.510 ←[34mINFO←[0m autosaved config {"file": "C:\\Users\\Connor\\AppData\\Roaming\\Caddy\\autosave.json"}
2021/04/29 11:48:20.510 ←[34mINFO←[0m serving initial configuration
2021/04/29 11:48:20.522 ←[34mINFO←[0m tls.obtain acquiring lock {"identifier": "connormorse.com"}
2021/04/29 11:48:20.523 ←[34mINFO←[0m tls.obtain lock acquired {"identifier": "connormorse.com"}
2021/04/29 11:48:20.532 ←[34mINFO←[0m tls.issuance.acme waiting on internal rate limiter {"identifiers": ["connormorse.com"]}
2021/04/29 11:48:20.532 ←[34mINFO←[0m tls.issuance.acme done waiting on internal rate limiter {"identifiers": ["connormorse.com"]}
2021/04/29 11:48:21.516 ←[34mINFO←[0m tls.issuance.acme waiting on internal rate limiter {"identifiers": ["connormorse.com"]}
2021/04/29 11:48:21.517 ←[34mINFO←[0m tls.issuance.acme done waiting on internal rate limiter {"identifiers": ["connormorse.com"]}
2021/04/29 11:48:23.143 ←[34mINFO←[0m tls.issuance.acme.acme_client trying to solve challenge {"identifier": "connormorse.com", "challenge_type": "http-01", "ca": "https://acme.zerossl.com/v2/DV90"}
5. What I already tried:
Tried v1 which used to work but fails on rate limit, I have waited a week but still the same issue, maybe I didn’t wait a full week and tripped the limit again? Sorry for lack of information I am not well versed in this stuff. I would appreciate any help