Caddy not getting SSL certificate for jellyfin server

Help
1

1. The problem I’m having:

I am trying to connect to my jellyfin server via https over the internet. So I want to use Caddy as a reverse proxy. But I’m having issues with Caddy not retrieving an SSL certificate.

I tried using both a “one liner” as well as running Caddy as a service, (which I want to) but I got similar errors either way. I don’t know what the issue would be.

The tutorial I was following is linked in section 5.

2. Error messages and/or full log output:

2025/07/13 11:37:07.216 WARN    admin   admin endpoint disabled
2025/07/13 11:37:07.216 INFO    http    server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS {"server_name": "proxy", "https_port": 443}
2025/07/13 11:37:07.216 INFO    http    enabling automatic HTTP->HTTPS redirects        {"server_name": "proxy"}
2025/07/13 11:37:07.217 INFO    tls.cache.maintenance   started background certificate maintenance      {"cache": "0xc000241110"}
2025/07/13 11:37:07.217 INFO    tls     cleaning storage unit   {"description": "FileStorage:/home/cskar/.local/share/caddy"}
2025/07/13 11:37:07.217 INFO    tls     finished cleaning storage units
2025/07/13 11:37:07.217 INFO    http    enabling HTTP/3 listener        {"addr": ":443"}
2025/07/13 11:37:07.217 INFO    failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details.
2025/07/13 11:37:07.217 INFO    http.log        server running  {"name": "proxy", "protocols": ["h1", "h2", "h3"]}
2025/07/13 11:37:07.217 INFO    http.log        server running  {"name": "remaining_auto_https_redirects", "protocols": ["h1", "h2", "h3"]}
2025/07/13 11:37:07.217 INFO    http    enabling automatic TLS certificate management   {"domains": ["jellyfinuddnas.linkpc.net"]}
Caddy proxying https://jellyfinuddnas.linkpc.net -> 127.0.0.1:8096
2025/07/13 11:37:07.218 INFO    tls.obtain      acquiring lock  {"identifier": "jellyfinuddnas.linkpc.net"}
2025/07/13 11:37:07.286 INFO    tls.obtain      lock acquired   {"identifier": "jellyfinuddnas.linkpc.net"}
2025/07/13 11:37:07.286 INFO    tls.obtain      obtaining certificate   {"identifier": "jellyfinuddnas.linkpc.net"}
2025/07/13 11:37:07.298 INFO    http    waiting on internal rate limiter        {"identifiers": ["jellyfinuddnas.linkpc.net"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": ""}
2025/07/13 11:37:07.299 INFO    http    done waiting on internal rate limiter   {"identifiers": ["jellyfinuddnas.linkpc.net"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": ""}
2025/07/13 11:37:08.437 INFO    http.acme_client        trying to solve challenge       {"identifier": "jellyfinuddnas.linkpc.net", "challenge_type": "http-01", "ca": "https://acme-v02.api.letsencrypt.org/directory"}
2025/07/13 11:37:10.250 ERROR   http.acme_client        challenge failed        {"identifier": "jellyfinuddnas.linkpc.net", "challenge_type": "http-01", "status_code": 403, "problem_type": "urn:ietf:params:acme:error:unauthorized", "error": "81.231.164.41: Invalid response from http://jellyfinuddnas.linkpc.net/.well-known/acme-challenge/PI9Frz-F5Mz-GRlTJIEXPQeNC14Zv-i7bhp-yXFxwNM: 404"}
2025/07/13 11:37:10.250 ERROR   http.acme_client        validating authorization        {"identifier": "jellyfinuddnas.linkpc.net", "error": "authorization failed: HTTP 403 urn:ietf:params:acme:error:unauthorized - 81.231.164.41: Invalid response from http://jellyfinuddnas.linkpc.net/.well-known/acme-challenge/PI9Frz-F5Mz-GRlTJIEXPQeNC14Zv-i7bhp-yXFxwNM: 404", "order": "https://acme-v02.api.letsencrypt.org/acme/order/2524859381/406106541311", "attempt": 1, "max_attempts": 3}
2025/07/13 11:37:11.687 INFO    http.acme_client        trying to solve challenge       {"identifier": "jellyfinuddnas.linkpc.net", "challenge_type": "tls-alpn-01", "ca": "https://acme-v02.api.letsencrypt.org/directory"}
2025/07/13 11:37:13.487 ERROR   http.acme_client        challenge failed        {"identifier": "jellyfinuddnas.linkpc.net", "challenge_type": "tls-alpn-01", "status_code": 400, "problem_type": "urn:ietf:params:acme:error:connection", "error": "81.231.164.41: Connection refused"}
2025/07/13 11:37:13.487 ERROR   http.acme_client        validating authorization        {"identifier": "jellyfinuddnas.linkpc.net", "error": "authorization failed: HTTP 400 urn:ietf:params:acme:error:connection - 81.231.164.41: Connection refused", "order": "https://acme-v02.api.letsencrypt.org/acme/order/2524859381/406106556471", "attempt": 2, "max_attempts": 3}
2025/07/13 11:37:15.133 ERROR   tls.obtain      could not get certificate from issuer   {"identifier": "jellyfinuddnas.linkpc.net", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "[jellyfinuddnas.linkpc.net] solving challenges: jellyfinuddnas.linkpc.net: no solvers available for remaining challenges (configured=[http-01 tls-alpn-01] offered=[dns-01 http-01 tls-alpn-01] remaining=[dns-01]) (order=https://acme-v02.api.letsencrypt.org/acme/order/2524859381/406106570401) (ca=https://acme-v02.api.letsencrypt.org/directory)"}
2025/07/13 11:37:15.134 WARN    http    missing email address for ZeroSSL; it is strongly recommended to set one for next time
2025/07/13 11:37:15.646 ERROR   tls.obtain      could not get certificate from issuer   {"identifier": "jellyfinuddnas.linkpc.net", "issuer": "acme.zerossl.com-v2-DV90", "error": "account pre-registration callback: failed getting EAB credentials: HTTP 422: caddy_legacy_user_removed (code 2977)"}
2025/07/13 11:37:15.646 ERROR   tls.obtain      will retry      {"error": "[jellyfinuddnas.linkpc.net] Obtain: account pre-registration callback: failed getting EAB credentials: HTTP 422: caddy_legacy_user_removed (code 2977)", "attempt": 1, "retrying_in": 60, "elapsed": 8.360346628, "max_duration": 2592000}

3. Caddy version:

2.6.2

4. How I installed and ran Caddy:

I installed Caddy using

sudo apt install caddy

I tried both running it with the command bellow in section 4.b as well as:

$ sudo systemctl start caddy.service

a. System environment:

Ubuntu server 24.04.2 LTS

b. Command:

$ caddy reverse-proxy --from jellyfinuddnas.linkpc.net --to 127.0.0.1:8096

c. Service/unit/compose file:

d. My complete Caddy config:

jellyfinuddnas.linkpc.net {
        tls mymail@mail.com
        reverse_proxy 127.0.0.1:8096
}

5. Links to relevant resources:

2

This is too old. Don’t use the version supplied by Debian default repository. Use our official repo.

1 Like
3

I installed a newer version (v2.10.0) and ran this command again:

$ caddy reverse-proxy --from jellyfinuddnas.linkpc.net --to 127.0.0.1:8096

I got similar errors as before.

2025/07/13 12:56:10.457 WARN    admin   admin endpoint disabled
2025/07/13 12:56:10.458 INFO    http.auto_https server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS {"server_name": "proxy", "https_port": 443}
2025/07/13 12:56:10.458 INFO    http.auto_https enabling automatic HTTP->HTTPS redirects        {"server_name": "proxy"}
2025/07/13 12:56:10.458 INFO    tls.cache.maintenance   started background certificate maintenance      {"cache": "0xc0001b1780"}
2025/07/13 12:56:10.458 WARN    http    HTTP/2 skipped because it requires TLS  {"network": "tcp", "addr": ":80"}
2025/07/13 12:56:10.458 WARN    http    HTTP/3 skipped because it requires TLS  {"network": "tcp", "addr": ":80"}
2025/07/13 12:56:10.458 INFO    http.log        server running  {"name": "remaining_auto_https_redirects", "protocols": ["h1", "h2", "h3"]}
2025/07/13 12:56:10.458 INFO    http    enabling HTTP/3 listener        {"addr": ":443"}
2025/07/13 12:56:10.458 INFO    failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 7168 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details.
2025/07/13 12:56:10.458 INFO    http.log        server running  {"name": "proxy", "protocols": ["h1", "h2", "h3"]}
2025/07/13 12:56:10.458 INFO    http    enabling automatic TLS certificate management   {"domains": ["jellyfinuddnas.linkpc.net"]}
2025/07/13 12:56:10.459 INFO    caddy proxying  {"from": "https://jellyfinuddnas.linkpc.net", "to": ["127.0.0.1:8096"]}
2025/07/13 12:56:10.521 INFO    tls     cleaning storage unit   {"storage": "FileStorage:/home/cskar/.local/share/caddy"}
2025/07/13 12:56:10.545 INFO    tls.obtain      acquiring lock  {"identifier": "jellyfinuddnas.linkpc.net"}
2025/07/13 12:56:10.572 INFO    tls     finished cleaning storage units
2025/07/13 12:56:10.588 INFO    tls.obtain      lock acquired   {"identifier": "jellyfinuddnas.linkpc.net"}
2025/07/13 12:56:10.588 INFO    tls.obtain      obtaining certificate   {"identifier": "jellyfinuddnas.linkpc.net"}
2025/07/13 12:56:10.598 INFO    http    waiting on internal rate limiter        {"identifiers": ["jellyfinuddnas.linkpc.net"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": ""}
2025/07/13 12:56:10.598 INFO    http    done waiting on internal rate limiter   {"identifiers": ["jellyfinuddnas.linkpc.net"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": ""}
2025/07/13 12:56:10.598 INFO    http    using ACME account      {"account_id": "https://acme-v02.api.letsencrypt.org/acme/acct/2524859381", "account_contact": []}
2025/07/13 12:56:11.559 INFO    trying to solve challenge       {"identifier": "jellyfinuddnas.linkpc.net", "challenge_type": "tls-alpn-01", "ca": "https://acme-v02.api.letsencrypt.org/directory"}
2025/07/13 12:56:12.163 ERROR   challenge failed        {"identifier": "jellyfinuddnas.linkpc.net", "challenge_type": "tls-alpn-01", "problem": {"type": "urn:ietf:params:acme:error:connection", "title": "", "detail": "81.231.164.41: Connection refused", "instance": "", "subproblems": null}}
github.com/mholt/acmez/v3.(*Client).pollAuthorization
        github.com/mholt/acmez/v3@v3.1.2/client.go:557
github.com/mholt/acmez/v3.(*Client).solveChallenges
        github.com/mholt/acmez/v3@v3.1.2/client.go:378
github.com/mholt/acmez/v3.(*Client).ObtainCertificate
        github.com/mholt/acmez/v3@v3.1.2/client.go:136
github.com/caddyserver/certmagic.(*ACMEIssuer).doIssue
        github.com/caddyserver/certmagic@v0.23.0/acmeissuer.go:489
github.com/caddyserver/certmagic.(*ACMEIssuer).Issue
        github.com/caddyserver/certmagic@v0.23.0/acmeissuer.go:382
github.com/caddyserver/caddy/v2/modules/caddytls.(*ACMEIssuer).Issue
        github.com/caddyserver/caddy/v2@v2.10.0/modules/caddytls/acmeissuer.go:288
github.com/caddyserver/certmagic.(*Config).obtainCert.func2
        github.com/caddyserver/certmagic@v0.23.0/config.go:626
github.com/caddyserver/certmagic.doWithRetry
        github.com/caddyserver/certmagic@v0.23.0/async.go:104
github.com/caddyserver/certmagic.(*Config).obtainCert
        github.com/caddyserver/certmagic@v0.23.0/config.go:700
github.com/caddyserver/certmagic.(*Config).ObtainCertAsync
        github.com/caddyserver/certmagic@v0.23.0/config.go:505
github.com/caddyserver/certmagic.(*Config).manageOne.func1
        github.com/caddyserver/certmagic@v0.23.0/config.go:415
github.com/caddyserver/certmagic.(*jobManager).worker
        github.com/caddyserver/certmagic@v0.23.0/async.go:73
2025/07/13 12:56:12.163 ERROR   validating authorization        {"identifier": "jellyfinuddnas.linkpc.net", "problem": {"type": "urn:ietf:params:acme:error:connection", "title": "", "detail": "81.231.164.41: Connection refused", "instance": "", "subproblems": null}, "order": "https://acme-v02.api.letsencrypt.org/acme/order/2524859381/406127178431", "attempt": 1, "max_attempts": 3}
github.com/mholt/acmez/v3.(*Client).ObtainCertificate
        github.com/mholt/acmez/v3@v3.1.2/client.go:152
github.com/caddyserver/certmagic.(*ACMEIssuer).doIssue
        github.com/caddyserver/certmagic@v0.23.0/acmeissuer.go:489
github.com/caddyserver/certmagic.(*ACMEIssuer).Issue
        github.com/caddyserver/certmagic@v0.23.0/acmeissuer.go:382
github.com/caddyserver/caddy/v2/modules/caddytls.(*ACMEIssuer).Issue
        github.com/caddyserver/caddy/v2@v2.10.0/modules/caddytls/acmeissuer.go:288
github.com/caddyserver/certmagic.(*Config).obtainCert.func2
        github.com/caddyserver/certmagic@v0.23.0/config.go:626
github.com/caddyserver/certmagic.doWithRetry
        github.com/caddyserver/certmagic@v0.23.0/async.go:104
github.com/caddyserver/certmagic.(*Config).obtainCert
        github.com/caddyserver/certmagic@v0.23.0/config.go:700
github.com/caddyserver/certmagic.(*Config).ObtainCertAsync
        github.com/caddyserver/certmagic@v0.23.0/config.go:505
github.com/caddyserver/certmagic.(*Config).manageOne.func1
        github.com/caddyserver/certmagic@v0.23.0/config.go:415
github.com/caddyserver/certmagic.(*jobManager).worker
        github.com/caddyserver/certmagic@v0.23.0/async.go:73
2025/07/13 12:56:13.479 INFO    trying to solve challenge       {"identifier": "jellyfinuddnas.linkpc.net", "challenge_type": "http-01", "ca": "https://acme-v02.api.letsencrypt.org/directory"}
2025/07/13 12:56:15.293 ERROR   challenge failed        {"identifier": "jellyfinuddnas.linkpc.net", "challenge_type": "http-01", "problem": {"type": "urn:ietf:params:acme:error:unauthorized", "title": "", "detail": "81.231.164.41: Invalid response from http://jellyfinuddnas.linkpc.net/.well-known/acme-challenge/bYEZsoAQ3qNHkBsTxO7V9M8CQOC7l8kfn4rnL9f3LJI: 404", "instance": "", "subproblems": null}}
github.com/mholt/acmez/v3.(*Client).pollAuthorization
        github.com/mholt/acmez/v3@v3.1.2/client.go:557
github.com/mholt/acmez/v3.(*Client).solveChallenges
        github.com/mholt/acmez/v3@v3.1.2/client.go:378
github.com/mholt/acmez/v3.(*Client).ObtainCertificate
        github.com/mholt/acmez/v3@v3.1.2/client.go:136
github.com/caddyserver/certmagic.(*ACMEIssuer).doIssue
        github.com/caddyserver/certmagic@v0.23.0/acmeissuer.go:489
github.com/caddyserver/certmagic.(*ACMEIssuer).Issue
        github.com/caddyserver/certmagic@v0.23.0/acmeissuer.go:382
github.com/caddyserver/caddy/v2/modules/caddytls.(*ACMEIssuer).Issue
        github.com/caddyserver/caddy/v2@v2.10.0/modules/caddytls/acmeissuer.go:288
github.com/caddyserver/certmagic.(*Config).obtainCert.func2
        github.com/caddyserver/certmagic@v0.23.0/config.go:626
github.com/caddyserver/certmagic.doWithRetry
        github.com/caddyserver/certmagic@v0.23.0/async.go:104
github.com/caddyserver/certmagic.(*Config).obtainCert
        github.com/caddyserver/certmagic@v0.23.0/config.go:700
github.com/caddyserver/certmagic.(*Config).ObtainCertAsync
        github.com/caddyserver/certmagic@v0.23.0/config.go:505
github.com/caddyserver/certmagic.(*Config).manageOne.func1
        github.com/caddyserver/certmagic@v0.23.0/config.go:415
github.com/caddyserver/certmagic.(*jobManager).worker
        github.com/caddyserver/certmagic@v0.23.0/async.go:73
2025/07/13 12:56:15.294 ERROR   validating authorization        {"identifier": "jellyfinuddnas.linkpc.net", "problem": {"type": "urn:ietf:params:acme:error:unauthorized", "title": "", "detail": "81.231.164.41: Invalid response from http://jellyfinuddnas.linkpc.net/.well-known/acme-challenge/bYEZsoAQ3qNHkBsTxO7V9M8CQOC7l8kfn4rnL9f3LJI: 404", "instance": "", "subproblems": null}, "order": "https://acme-v02.api.letsencrypt.org/acme/order/2524859381/406127188041", "attempt": 2, "max_attempts": 3}
github.com/mholt/acmez/v3.(*Client).ObtainCertificate
        github.com/mholt/acmez/v3@v3.1.2/client.go:152
github.com/caddyserver/certmagic.(*ACMEIssuer).doIssue
        github.com/caddyserver/certmagic@v0.23.0/acmeissuer.go:489
github.com/caddyserver/certmagic.(*ACMEIssuer).Issue
        github.com/caddyserver/certmagic@v0.23.0/acmeissuer.go:382
github.com/caddyserver/caddy/v2/modules/caddytls.(*ACMEIssuer).Issue
        github.com/caddyserver/caddy/v2@v2.10.0/modules/caddytls/acmeissuer.go:288
github.com/caddyserver/certmagic.(*Config).obtainCert.func2
        github.com/caddyserver/certmagic@v0.23.0/config.go:626
github.com/caddyserver/certmagic.doWithRetry
        github.com/caddyserver/certmagic@v0.23.0/async.go:104
github.com/caddyserver/certmagic.(*Config).obtainCert
        github.com/caddyserver/certmagic@v0.23.0/config.go:700
github.com/caddyserver/certmagic.(*Config).ObtainCertAsync
        github.com/caddyserver/certmagic@v0.23.0/config.go:505
github.com/caddyserver/certmagic.(*Config).manageOne.func1
        github.com/caddyserver/certmagic@v0.23.0/config.go:415
github.com/caddyserver/certmagic.(*jobManager).worker
        github.com/caddyserver/certmagic@v0.23.0/async.go:73
2025/07/13 12:56:15.294 ERROR   tls.obtain      could not get certificate from issuer   {"identifier": "jellyfinuddnas.linkpc.net", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "HTTP 403 urn:ietf:params:acme:error:unauthorized - 81.231.164.41: Invalid response from http://jellyfinuddnas.linkpc.net/.well-known/acme-challenge/bYEZsoAQ3qNHkBsTxO7V9M8CQOC7l8kfn4rnL9f3LJI: 404"}
2025/07/13 12:56:15.294 ERROR   tls.obtain      will retry      {"error": "[jellyfinuddnas.linkpc.net] Obtain: [jellyfinuddnas.linkpc.net] solving challenge: jellyfinuddnas.linkpc.net: [jellyfinuddnas.linkpc.net] authorization failed: HTTP 403 urn:ietf:params:acme:error:unauthorized - 81.231.164.41: Invalid response from http://jellyfinuddnas.linkpc.net/.well-known/acme-challenge/bYEZsoAQ3qNHkBsTxO7V9M8CQOC7l8kfn4rnL9f3LJI: 404 (ca=https://acme-v02.api.letsencrypt.org/directory)", "attempt": 1, "retrying_in": 60, "elapsed": 4.7055675, "max_duration": 2592000}
2025/07/13 12:57:15.298 INFO    tls.obtain      obtaining certificate   {"identifier": "jellyfinuddnas.linkpc.net"}
2025/07/13 12:57:15.300 INFO    http    creating new account because no account for configured email is known to us     {"email": "", "ca": "https://acme-staging-v02.api.letsencrypt.org/directory", "error": "open /home/cskar/.local/share/caddy/acme/acme-staging-v02.api.letsencrypt.org-directory/users/default/default.json: no such file or directory"}
2025/07/13 12:57:15.300 INFO    http    ACME account has empty status; registering account with ACME server     {"contact": [], "location": ""}
2025/07/13 12:57:15.354 INFO    http    creating new account because no account for configured email is known to us     {"email": "", "ca": "https://acme-staging-v02.api.letsencrypt.org/directory", "error": "open /home/cskar/.local/share/caddy/acme/acme-staging-v02.api.letsencrypt.org-directory/users/default/default.json: no such file or directory"}
2025/07/13 12:57:16.182 INFO    http    new ACME account registered     {"contact": [], "status": "valid"}
2025/07/13 12:57:16.230 INFO    http    using ACME account      {"account_id": "https://acme-staging-v02.api.letsencrypt.org/acme/acct/212509474", "account_contact": []}
2025/07/13 12:57:16.558 INFO    trying to solve challenge       {"identifier": "jellyfinuddnas.linkpc.net", "challenge_type": "http-01", "ca": "https://acme-staging-v02.api.letsencrypt.org/directory"}
2025/07/13 12:57:17.575 ERROR   challenge failed        {"identifier": "jellyfinuddnas.linkpc.net", "challenge_type": "http-01", "problem": {"type": "urn:ietf:params:acme:error:unauthorized", "title": "", "detail": "81.231.164.41: Invalid response from http://jellyfinuddnas.linkpc.net/.well-known/acme-challenge/CjddFe9ScvdaF0Y1Ibg602BMID7_m_E6eSzU-vnIao0: 404", "instance": "", "subproblems": null}}
github.com/mholt/acmez/v3.(*Client).pollAuthorization
        github.com/mholt/acmez/v3@v3.1.2/client.go:557
github.com/mholt/acmez/v3.(*Client).solveChallenges
        github.com/mholt/acmez/v3@v3.1.2/client.go:378
github.com/mholt/acmez/v3.(*Client).ObtainCertificate
        github.com/mholt/acmez/v3@v3.1.2/client.go:136
github.com/caddyserver/certmagic.(*ACMEIssuer).doIssue
        github.com/caddyserver/certmagic@v0.23.0/acmeissuer.go:489
github.com/caddyserver/certmagic.(*ACMEIssuer).Issue
        github.com/caddyserver/certmagic@v0.23.0/acmeissuer.go:382
github.com/caddyserver/caddy/v2/modules/caddytls.(*ACMEIssuer).Issue
        github.com/caddyserver/caddy/v2@v2.10.0/modules/caddytls/acmeissuer.go:288
github.com/caddyserver/certmagic.(*Config).obtainCert.func2
        github.com/caddyserver/certmagic@v0.23.0/config.go:626
github.com/caddyserver/certmagic.doWithRetry
        github.com/caddyserver/certmagic@v0.23.0/async.go:104
github.com/caddyserver/certmagic.(*Config).obtainCert
        github.com/caddyserver/certmagic@v0.23.0/config.go:700
github.com/caddyserver/certmagic.(*Config).ObtainCertAsync
        github.com/caddyserver/certmagic@v0.23.0/config.go:505
github.com/caddyserver/certmagic.(*Config).manageOne.func1
        github.com/caddyserver/certmagic@v0.23.0/config.go:415
github.com/caddyserver/certmagic.(*jobManager).worker
        github.com/caddyserver/certmagic@v0.23.0/async.go:73
2025/07/13 12:57:17.575 ERROR   validating authorization        {"identifier": "jellyfinuddnas.linkpc.net", "problem": {"type": "urn:ietf:params:acme:error:unauthorized", "title": "", "detail": "81.231.164.41: Invalid response from http://jellyfinuddnas.linkpc.net/.well-known/acme-challenge/CjddFe9ScvdaF0Y1Ibg602BMID7_m_E6eSzU-vnIao0: 404", "instance": "", "subproblems": null}, "order": "https://acme-staging-v02.api.letsencrypt.org/acme/order/212509474/26023457384", "attempt": 1, "max_attempts": 3}
github.com/mholt/acmez/v3.(*Client).ObtainCertificate
        github.com/mholt/acmez/v3@v3.1.2/client.go:152
github.com/caddyserver/certmagic.(*ACMEIssuer).doIssue
        github.com/caddyserver/certmagic@v0.23.0/acmeissuer.go:489
github.com/caddyserver/certmagic.(*ACMEIssuer).Issue
        github.com/caddyserver/certmagic@v0.23.0/acmeissuer.go:382
github.com/caddyserver/caddy/v2/modules/caddytls.(*ACMEIssuer).Issue
        github.com/caddyserver/caddy/v2@v2.10.0/modules/caddytls/acmeissuer.go:288
github.com/caddyserver/certmagic.(*Config).obtainCert.func2
        github.com/caddyserver/certmagic@v0.23.0/config.go:626
github.com/caddyserver/certmagic.doWithRetry
        github.com/caddyserver/certmagic@v0.23.0/async.go:104
github.com/caddyserver/certmagic.(*Config).obtainCert
        github.com/caddyserver/certmagic@v0.23.0/config.go:700
github.com/caddyserver/certmagic.(*Config).ObtainCertAsync
        github.com/caddyserver/certmagic@v0.23.0/config.go:505
github.com/caddyserver/certmagic.(*Config).manageOne.func1
        github.com/caddyserver/certmagic@v0.23.0/config.go:415
github.com/caddyserver/certmagic.(*jobManager).worker
        github.com/caddyserver/certmagic@v0.23.0/async.go:73
2025/07/13 12:57:18.898 INFO    trying to solve challenge       {"identifier": "jellyfinuddnas.linkpc.net", "challenge_type": "tls-alpn-01", "ca": "https://acme-staging-v02.api.letsencrypt.org/directory"}
4

It’s not the same error. Your firewall/router isn’t allowing connections from Let’s Encrypt.

1 Like
5

I changed the port being forwarded in my router settings and now it works.
I’m 90% sure I already tested changed the port so it must have been an issue with the version as well.

1 Like
6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.