1. Caddy version (2.1.4
):
2. How I run Caddy: ./caddy run
a. System environment: Windows 10 Pro
b. Command:
./caddy run
d. My complete Caddyfile or JSON config:
{
cert_issuer zerossl 868e8687dbef746f8058e26048e1d50f
http_port 8647
https_port 7468
}
https://jellyfin.invalidparameter.net
reverse_proxy localhost:8096
3. The problem I’m having:
Was using Caddy as a reverse proxy until Windows updated a few days ago. From what I’ve found it looks to be an update to their Windows Update service that has bound port 443 to that service, and there doesn’t seem to be anything I can do to change that. I no longer am able access Jellyfin remotely via HTTPS.
4. Error messages and/or full log output:
PS C:\Caddy> ./caddy run
2021/06/13 21:49:56.292 ←[34mINFO←[0m using adjacent Caddyfile
2021/06/13 21:49:56.293 ←[33mWARN←[0m input is not formatted with ‘caddy fmt’ {“adapter”: “caddyfile”, “file”: “Caddyfile”, “line”: 2}
2021/06/13 21:49:56.302 ←[34mINFO←[0m admin admin endpoint started {“address”: “tcp/localhost:2019”, “enforce_origin”: false, “origins”: [“localhost:2019”, “[::1]:2019”, “127.0.0.1:2019”]}
2021/06/13 21:49:56.303 ←[34mINFO←[0m tls.cache.maintenance started background certificate maintenance {“cache”: “0xc000339ce0”}
2021/06/13 21:49:56.303 ←[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”: 7468}
2021/06/13 21:49:56.303 ←[34mINFO←[0m http enabling automatic HTTP->HTTPS redirects {“server_name”: “srv0”}
2021/06/13 21:49:56.304 ←[34mINFO←[0m tls cleaning storage unit {“description”: “FileStorage:C:\Users\Mike\AppData\Roaming\Caddy”}
2021/06/13 21:49:56.304 ←[34mINFO←[0m tls finished cleaning storage units
2021/06/13 21:49:56.304 ←[34mINFO←[0m http enabling automatic TLS certificate management {"domains": ["jellyfin.invalidparameter.net"]}
2021/06/13 21:49:56.305 ←[34mINFO←[0m autosaved config (load with --resume flag) {“file”: “C:\Users\Mike\AppData\Roaming\Caddy\autosave.json”}
2021/06/13 21:49:56.306 ←[34mINFO←[0m serving initial configuration
2021/06/13 21:49:56.313 ←[34mINFO←[0m tls.obtain acquiring lock {“identifier”: “jellyfin.invalidparameter.net”}
2021/06/13 16:49:56 [INFO][FileStorage:C:\Users\Mike\AppData\Roaming\Caddy] Lock for ‘issue_cert_jellyfin.invalidparameter.net
’ is stale (created: 2021-06-13 00:17:11.7983559 -0500 CDT, last update: 2021-06-13 00:18:01.9189797 -0500 CDT); removing then retrying: C:\Users\Mike\AppData\Roaming\Caddy\locks\issue_cert_jellyfin.invalidparameter.net.lock
2021/06/13 21:49:56.316 ←[34mINFO←[0m tls.obtain lock acquired {“identifier”: “jellyfin.invalidparameter.net”}
2021/06/13 21:49:56.335 ←[34mINFO←[0m tls.issuance.acme waiting on internal rate limiter {“identifiers”: [“jellyfin.invalidparameter.net”]}
2021/06/13 21:49:56.335 ←[34mINFO←[0m tls.issuance.acme done waiting on internal rate limiter {“identifiers”: ["jellyfin.invalidparameter.net
"]}
2021/06/13 21:49:57.012 ←[34mINFO←[0m tls.issuance.acme.acme_client trying to solve challenge {“identifier”: “jellyfin.invalidparameter.net
”, “challenge_type”: “http-01”, “ca”: “https://acme.zerossl.com/v2/DV90”}’’’
5. What I already tried:
I’m very new to this so sorry if I’ve missed something simple.
I’ve tried changing the port numbers for HTTP and HTTPs, and am using the zerossl API key. I did generate certificates from zerossl, but I’m unsure how to properly set them up to work with Caddy.
I have both ports forwarded to my computer that Caddy and jellyfin are on.
I’m really at a loss on how to fix this now.