[GH-ISSUE #2818] Nextcloud failed dimain check #17230

Closed
opened 2026-05-18 17:41:49 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @jreyes138 on GitHub (Apr 9, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2818

Describe the Bug

After version 1.11 pangolin failed nextcloud domain check.

Environment

  • OS Type & Version: Ubuntu 24.04.4 lts
  • Pangolin Version: 1.17.0
  • Gerbil Version: v0.17
  • Traefik Version: v3.6
  • Newt Version: 1.17.0
  • Olm Version: (if applicable)

To Reproduce

Configure Nextcloud and run domain check.

Expected Behavior

IT should pass the ssl check.

Originally created by @jreyes138 on GitHub (Apr 9, 2026). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2818 ### Describe the Bug After version 1.11 pangolin failed nextcloud domain check. ### Environment - OS Type & Version: Ubuntu 24.04.4 lts - Pangolin Version: 1.17.0 - Gerbil Version: v0.17 - Traefik Version: v3.6 - Newt Version: 1.17.0 - Olm Version: (if applicable) ### To Reproduce Configure Nextcloud and run domain check. ### Expected Behavior IT should pass the ssl check.
GiteaMirror added the stale label 2026-05-18 17:41:49 -05:00
Author
Owner

@LaurenceJJones commented on GitHub (Apr 10, 2026):

Please share a bit more detail. Saying you “run Nextcloud” is not enough for us to reliably reproduce the issue, as a real production setup may include additional configuration or behaviour that is relevant here.

To help us investigate, please provide actionable logs and clear reproduction steps. Without that, we are likely to miss important context, and we are not going to set up Nextcloud from scratch just to guess at the cause.

<!-- gh-comment-id:4223498551 --> @LaurenceJJones commented on GitHub (Apr 10, 2026): Please share a bit more detail. Saying you “run Nextcloud” is not enough for us to reliably reproduce the issue, as a real production setup may include additional configuration or behaviour that is relevant here. To help us investigate, please provide actionable logs and clear reproduction steps. Without that, we are likely to miss important context, and we are not going to set up Nextcloud from scratch just to guess at the cause.
Author
Owner

@abanliver commented on GitHub (Apr 14, 2026):

OP see: https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md#6-how-to-debug-things

This is most likely a NC issue rather than a Pangolin one. I personally experienced this (without pangolin) with NC and had to disable the domain check to proceed with the installation. Good luck.

<!-- gh-comment-id:4243019368 --> @abanliver commented on GitHub (Apr 14, 2026): OP see: https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md#6-how-to-debug-things This is most likely a NC issue rather than a Pangolin one. I personally experienced this (without pangolin) with NC and had to disable the domain check to proceed with the installation. Good luck.
Author
Owner

@AstralDestiny commented on GitHub (Apr 18, 2026):

Well was hoping the discord part would be put where the actual user was.

Do you have the

entryPoints:
  web:
    address: ":80"
  websecure:
    address: ":443"
    transport:
      respondingTimeouts:
        readTimeout: "30m"
    http:
      tls:
        certResolver: "letsencrypt"
      encodedCharacters:
        allowEncodedSlash: true # this
        allowEncodedQuestionMark: true # this

From within your traefik ? or can you provide some images or logs?

<!-- gh-comment-id:4272425652 --> @AstralDestiny commented on GitHub (Apr 18, 2026): Well was hoping the discord part would be put where the actual user was. Do you have the ``` entryPoints: web: address: ":80" websecure: address: ":443" transport: respondingTimeouts: readTimeout: "30m" http: tls: certResolver: "letsencrypt" encodedCharacters: allowEncodedSlash: true # this allowEncodedQuestionMark: true # this ``` From within your traefik ? or can you provide some images or logs?
Author
Owner

@github-actions[bot] commented on GitHub (May 3, 2026):

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

<!-- gh-comment-id:4365069433 --> @github-actions[bot] commented on GitHub (May 3, 2026): This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#17230