Ooooh I didn’t know that. Then in that case yes there’s definitely errors here.
2023/07/07 14:10:45.164 ←[34mINFO←[0m using provided configuration {"config_file": "Caddyfile", "config_adapter": ""}
2023/07/07 14:10:45.164 ←[33mWARN←[0m Caddyfile input is not formatted; run the 'caddy fmt' command to fix inconsistencies {"adapter": "caddyfile", "file": "Caddyfile", "line": 1}
2023/07/07 14:10:45.177 ←[34mINFO←[0m admin admin endpoint started {"address": "localhost:2019", "enforce_origin": false, "origins": ["//localhost:2019", "//[::1]:2019", "//127.0.0.1:2019"]}
2023/07/07 14:10:45.178 ←[34mINFO←[0m tls.cache.maintenance started background certificate maintenance {"cache": "0xc00020ff80"}
2023/07/07 14:10:45.178 ←[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}
2023/07/07 14:10:45.178 ←[34mINFO←[0m http enabling automatic HTTP->HTTPS redirects {"server_name": "srv0"}
2023/07/07 14:10:45.179 ←[34mINFO←[0m tls cleaning storage unit {"description": "FileStorage:C:\\Users\\user\\AppData\\Roaming\\Caddy"}
2023/07/07 14:10:45.179 ←[34mINFO←[0m tls finished cleaning storage units
2023/07/07 14:10:45.179 ←[34mINFO←[0m http enabling HTTP/3 listener {"addr": ":443"}
2023/07/07 14:10:45.179 ←[34mINFO←[0m http.log server running {"name": "srv0", "protocols": ["h1", "h2", "h3"]}
2023/07/07 14:10:45.179 ←[34mINFO←[0m http.log server running {"name": "remaining_auto_https_redirects", "protocols": ["h1", "h2", "h3"]}
2023/07/07 14:10:45.180 ←[34mINFO←[0m http enabling automatic TLS certificate management {"domains": ["jellyfin-k.duckdns.org"]}
2023/07/07 14:10:45.181 ←[34mINFO←[0m autosaved config (load with --resume flag) {"file": "C:\\Users\\user\\AppData\\Roaming\\Caddy\\autosave.json"}
2023/07/07 14:10:45.182 ←[34mINFO←[0m serving initial configuration
2023/07/07 14:10:45.187 ←[34mINFO←[0m tls.obtain acquiring lock {"identifier": "jellyfin-k.duckdns.org"}
2023/07/07 14:10:45.194 ←[34mINFO←[0m [INFO][FileStorage:C:\Users\user\AppData\Roaming\Caddy] Lock for 'issue_cert_jellyfin-k.duckdns.org' is stale (created: 2023-07-07 14:39:21.5874625 +0100 BST, last update: 2023-07-07 15:03:29.6600409 +0100 BST); removing then retrying: C:\Users\user\AppData\Roaming\Caddy\locks\issue_cert_jellyfin-k.duckdns.org.lock
2023/07/07 14:10:45.197 ←[34mINFO←[0m tls.obtain lock acquired {"identifier": "jellyfin-k.duckdns.org"}
2023/07/07 14:10:45.197 ←[34mINFO←[0m tls.obtain obtaining certificate {"identifier": "jellyfin-k.duckdns.org"}
2023/07/07 14:10:45.211 ←[34mINFO←[0m http waiting on internal rate limiter {"identifiers": ["jellyfin-k.duckdns.org"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": ""}
2023/07/07 14:10:45.211 ←[34mINFO←[0m http done waiting on internal rate limiter {"identifiers": ["jellyfin-k.duckdns.org"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": ""}
2023/07/07 14:10:46.193 ←[34mINFO←[0m http.acme_client trying to solve challenge {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "ca": "https://acme-v02.api.letsencrypt.org/directory"}
2023/07/07 14:13:26.319 ←[31mERROR←[0m http.acme_client cleaning up solver {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "error": "no memory of presenting a DNS record for \"_acme-challenge.jellyfin-k.duckdns.org\" (usually OK if presenting also failed)"}
2023/07/07 14:13:26.476 ←[31mERROR←[0m tls.obtain could not get certificate from issuer {"identifier": "jellyfin-k.duckdns.org", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "[jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme-v02.api.letsencrypt.org/acme/order/1189994857/193419756077) (ca=https://acme-v02.api.letsencrypt.org/directory)"}
2023/07/07 14:13:26.491 ←[34mINFO←[0m http waiting on internal rate limiter {"identifiers": ["jellyfin-k.duckdns.org"], "ca": "https://acme.zerossl.com/v2/DV90", "account": "caddy@zerossl.com"}
2023/07/07 14:13:26.492 ←[34mINFO←[0m http done waiting on internal rate limiter {"identifiers": ["jellyfin-k.duckdns.org"], "ca": "https://acme.zerossl.com/v2/DV90", "account": "caddy@zerossl.com"}
2023/07/07 14:13:27.078 ←[34mINFO←[0m http.acme_client trying to solve challenge {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "ca": "https://acme.zerossl.com/v2/DV90"}
2023/07/07 14:16:07.230 ←[31mERROR←[0m http.acme_client cleaning up solver {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "error": "no memory of presenting a DNS record for \"_acme-challenge.jellyfin-k.duckdns.org\" (usually OK if presenting also failed)"}
2023/07/07 14:16:08.099 ←[31mERROR←[0m tls.obtain could not get certificate from issuer {"identifier": "jellyfin-k.duckdns.org", "issuer": "acme.zerossl.com-v2-DV90", "error": "[jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme.zerossl.com/v2/DV90/order/g8D62rkqtyLST4n6fSZ94Q) (ca=https://acme.zerossl.com/v2/DV90)"}
2023/07/07 14:16:08.099 ←[31mERROR←[0m tls.obtain will retry {"error": "[jellyfin-k.duckdns.org] Obtain: [jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme.zerossl.com/v2/DV90/order/g8D62rkqtyLST4n6fSZ94Q) (ca=https://acme.zerossl.com/v2/DV90)", "attempt": 1, "retrying_in": 60, "elapsed": 322.9025064, "max_duration": 2592000}
2023/07/07 14:17:08.112 ←[34mINFO←[0m tls.obtain obtaining certificate {"identifier": "jellyfin-k.duckdns.org"}
2023/07/07 14:17:09.139 ←[34mINFO←[0m http.acme_client trying to solve challenge {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "ca": "https://acme-staging-v02.api.letsencrypt.org/directory"}
2023/07/07 14:19:49.258 ←[31mERROR←[0m http.acme_client cleaning up solver {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "error": "no memory of presenting a DNS record for \"_acme-challenge.jellyfin-k.duckdns.org\" (usually OK if presenting also failed)"}
2023/07/07 14:19:49.416 ←[31mERROR←[0m tls.obtain could not get certificate from issuer {"identifier": "jellyfin-k.duckdns.org", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "[jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme-staging-v02.api.letsencrypt.org/acme/order/109530464/9631747144) (ca=https://acme-staging-v02.api.letsencrypt.org/directory)"}
2023/07/07 14:19:49.824 ←[34mINFO←[0m http.acme_client trying to solve challenge {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "ca": "https://acme.zerossl.com/v2/DV90"}
2023/07/07 14:22:29.970 ←[31mERROR←[0m http.acme_client cleaning up solver {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "error": "no memory of presenting a DNS record for \"_acme-challenge.jellyfin-k.duckdns.org\" (usually OK if presenting also failed)"}
2023/07/07 14:22:30.635 ←[31mERROR←[0m tls.obtain could not get certificate from issuer {"identifier": "jellyfin-k.duckdns.org", "issuer": "acme.zerossl.com-v2-DV90", "error": "[jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme.zerossl.com/v2/DV90/order/B0KobW174mwfW8pkdJWcgQ) (ca=https://acme.zerossl.com/v2/DV90)"}
2023/07/07 14:22:30.635 ←[31mERROR←[0m tls.obtain will retry {"error": "[jellyfin-k.duckdns.org] Obtain: [jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme.zerossl.com/v2/DV90/order/B0KobW174mwfW8pkdJWcgQ) (ca=https://acme.zerossl.com/v2/DV90)", "attempt": 2, "retrying_in": 120, "elapsed": 705.4386799, "max_duration": 2592000}
2023/07/07 14:24:30.647 ←[34mINFO←[0m tls.obtain obtaining certificate {"identifier": "jellyfin-k.duckdns.org"}
2023/07/07 14:24:31.124 ←[34mINFO←[0m http.acme_client trying to solve challenge {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "ca": "https://acme-staging-v02.api.letsencrypt.org/directory"}
2023/07/07 14:27:11.249 ←[31mERROR←[0m http.acme_client cleaning up solver {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "error": "no memory of presenting a DNS record for \"_acme-challenge.jellyfin-k.duckdns.org\" (usually OK if presenting also failed)"}
2023/07/07 14:27:11.410 ←[31mERROR←[0m tls.obtain could not get certificate from issuer {"identifier": "jellyfin-k.duckdns.org", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "[jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme-staging-v02.api.letsencrypt.org/acme/order/109530464/9631829214) (ca=https://acme-staging-v02.api.letsencrypt.org/directory)"}
2023/07/07 14:27:11.897 ←[34mINFO←[0m http.acme_client trying to solve challenge {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "ca": "https://acme.zerossl.com/v2/DV90"}
2023/07/07 14:29:52.058 ←[31mERROR←[0m http.acme_client cleaning up solver {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "error": "no memory of presenting a DNS record for \"_acme-challenge.jellyfin-k.duckdns.org\" (usually OK if presenting also failed)"}
2023/07/07 14:29:52.385 ←[31mERROR←[0m tls.obtain could not get certificate from issuer {"identifier": "jellyfin-k.duckdns.org", "issuer": "acme.zerossl.com-v2-DV90", "error": "[jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme.zerossl.com/v2/DV90/order/VPXNFRstxBIbH4i5ERFo9w) (ca=https://acme.zerossl.com/v2/DV90)"}
2023/07/07 14:29:52.385 ←[31mERROR←[0m tls.obtain will retry {"error": "[jellyfin-k.duckdns.org] Obtain: [jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme.zerossl.com/v2/DV90/order/VPXNFRstxBIbH4i5ERFo9w) (ca=https://acme.zerossl.com/v2/DV90)", "attempt": 3, "retrying_in": 120, "elapsed": 1147.188406, "max_duration": 2592000}
2023/07/07 14:31:52.394 ←[34mINFO←[0m tls.obtain obtaining certificate {"identifier": "jellyfin-k.duckdns.org"}
2023/07/07 14:31:52.872 ←[34mINFO←[0m http.acme_client trying to solve challenge {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "ca": "https://acme-staging-v02.api.letsencrypt.org/directory"}
2023/07/07 14:34:33.032 ←[31mERROR←[0m http.acme_client cleaning up solver {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "error": "no memory of presenting a DNS record for \"_acme-challenge.jellyfin-k.duckdns.org\" (usually OK if presenting also failed)"}
2023/07/07 14:34:33.192 ←[31mERROR←[0m tls.obtain could not get certificate from issuer {"identifier": "jellyfin-k.duckdns.org", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "[jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme-staging-v02.api.letsencrypt.org/acme/order/109530464/9631905764) (ca=https://acme-staging-v02.api.letsencrypt.org/directory)"}
2023/07/07 14:34:33.791 ←[34mINFO←[0m http.acme_client trying to solve challenge {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "ca": "https://acme.zerossl.com/v2/DV90"}
2023/07/07 14:37:13.909 ←[31mERROR←[0m http.acme_client cleaning up solver {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "error": "no memory of presenting a DNS record for \"_acme-challenge.jellyfin-k.duckdns.org\" (usually OK if presenting also failed)"}
2023/07/07 14:37:14.258 ←[31mERROR←[0m tls.obtain could not get certificate from issuer {"identifier": "jellyfin-k.duckdns.org", "issuer": "acme.zerossl.com-v2-DV90", "error": "[jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme.zerossl.com/v2/DV90/order/Y4NqQPgSNc1d1s44z2Ki2w) (ca=https://acme.zerossl.com/v2/DV90)"}
2023/07/07 14:37:14.258 ←[31mERROR←[0m tls.obtain will retry {"error": "[jellyfin-k.duckdns.org] Obtain: [jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme.zerossl.com/v2/DV90/order/Y4NqQPgSNc1d1s44z2Ki2w) (ca=https://acme.zerossl.com/v2/DV90)", "attempt": 4, "retrying_in": 300, "elapsed": 1589.0615354, "max_duration": 2592000}
2023/07/07 14:42:14.272 ←[34mINFO←[0m tls.obtain obtaining certificate {"identifier": "jellyfin-k.duckdns.org"}
2023/07/07 14:42:15.101 ←[34mINFO←[0m http.acme_client trying to solve challenge {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "ca": "https://acme-staging-v02.api.letsencrypt.org/directory"}
2023/07/07 14:44:55.230 ←[31mERROR←[0m http.acme_client cleaning up solver {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "error": "no memory of presenting a DNS record for \"_acme-challenge.jellyfin-k.duckdns.org\" (usually OK if presenting also failed)"}
2023/07/07 14:44:55.389 ←[31mERROR←[0m tls.obtain could not get certificate from issuer {"identifier": "jellyfin-k.duckdns.org", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "[jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme-staging-v02.api.letsencrypt.org/acme/order/109530464/9632040024) (ca=https://acme-staging-v02.api.letsencrypt.org/directory)"}
2023/07/07 14:44:55.854 ←[34mINFO←[0m http.acme_client trying to solve challenge {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "ca": "https://acme.zerossl.com/v2/DV90"}
2023/07/07 14:47:36.020 ←[31mERROR←[0m http.acme_client cleaning up solver {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "error": "no memory of presenting a DNS record for \"_acme-challenge.jellyfin-k.duckdns.org\" (usually OK if presenting also failed)"}
2023/07/07 14:47:36.235 ←[31mERROR←[0m tls.obtain could not get certificate from issuer {"identifier": "jellyfin-k.duckdns.org", "issuer": "acme.zerossl.com-v2-DV90", "error": "[jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme.zerossl.com/v2/DV90/order/j1_B3JBj3PkYbYPOI4xPfg) (ca=https://acme.zerossl.com/v2/DV90)"}
2023/07/07 14:47:36.235 ←[31mERROR←[0m tls.obtain will retry {"error": "[jellyfin-k.duckdns.org] Obtain: [jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme.zerossl.com/v2/DV90/order/j1_B3JBj3PkYbYPOI4xPfg) (ca=https://acme.zerossl.com/v2/DV90)", "attempt": 5, "retrying_in": 600, "elapsed": 2211.0384729, "max_duration": 2592000}
2023/07/07 14:57:36.236 ←[34mINFO←[0m tls.obtain obtaining certificate {"identifier": "jellyfin-k.duckdns.org"}
2023/07/07 14:57:37.047 ←[34mINFO←[0m http.acme_client trying to solve challenge {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "ca": "https://acme-staging-v02.api.letsencrypt.org/directory"}
2023/07/07 15:00:17.194 ←[31mERROR←[0m http.acme_client cleaning up solver {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "error": "no memory of presenting a DNS record for \"_acme-challenge.jellyfin-k.duckdns.org\" (usually OK if presenting also failed)"}
2023/07/07 15:00:17.359 ←[31mERROR←[0m tls.obtain could not get certificate from issuer {"identifier": "jellyfin-k.duckdns.org", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "[jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme-staging-v02.api.letsencrypt.org/acme/order/109530464/9632241304) (ca=https://acme-staging-v02.api.letsencrypt.org/directory)"}
2023/07/07 15:00:18.837 ←[34mINFO←[0m http.acme_client trying to solve challenge {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "ca": "https://acme.zerossl.com/v2/DV90"}
2023/07/07 15:02:59.001 ←[31mERROR←[0m http.acme_client cleaning up solver {"identifier": "jellyfin-k.duckdns.org", "challenge_type": "dns-01", "error": "no memory of presenting a DNS record for \"_acme-challenge.jellyfin-k.duckdns.org\" (usually OK if presenting also failed)"}
2023/07/07 15:02:59.245 ←[31mERROR←[0m tls.obtain could not get certificate from issuer {"identifier": "jellyfin-k.duckdns.org", "issuer": "acme.zerossl.com-v2-DV90", "error": "[jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme.zerossl.com/v2/DV90/order/j5g0RLQuv-_FulSmjl6ZWg) (ca=https://acme.zerossl.com/v2/DV90)"}
2023/07/07 15:02:59.245 ←[31mERROR←[0m tls.obtain will retry {"error": "[jellyfin-k.duckdns.org] Obtain: [jellyfin-k.duckdns.org] solving challenges: presenting for challenge: could not determine zone for domain \"_acme-challenge.jellyfin-k.duckdns.org\": could not find the start of authority for _acme-challenge.jellyfin-k.duckdns.org.: dial tcp 1.0.0.1:53: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. (order=https://acme.zerossl.com/v2/DV90/order/j5g0RLQuv-_FulSmjl6ZWg) (ca=https://acme.zerossl.com/v2/DV90)", "attempt": 6, "retrying_in": 1200, "elapsed": 3134.0484605, "max_duration": 2592000}