github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-07 05:09:18 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

[GH-ISSUE #2059] Upgrade from 1.12.3 to 1.13.0 Nextcloud Collabra and Calendar fail to connect #8826

New Issue
Closed
opened 2026-04-30 04:53:34 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-30 04:53:34 -05:00
Owner
Copy Link

Originally created by @i-byrana on GitHub (Dec 12, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2059

Describe the Bug

Hello there!

I have been using the latest Nextcloud AIO (Unraid "Homelab") with Pangolin 1.12.3 (OVH VPS) without any problems. Today I did the upgrade to Pangolin 1.13.0 with all requirements, including Traefik from 3.6.2 to 3.6.4. After the upgrade I thought everything went fine, as usual. I was able to log into Nextcloud and use mostly everything. Strangely, I am unable to use Nextcloud Office (Collabora) anymore, and shared calendars won't work either. I am unable to open up or create a document, nor am I able to write an appointment into the calendar. The sync from smartphone via DAVx does not work and shows a 400 error. I get a WebSocket error if I want to open Collabora and add an appointment. I restored an update of the VPS from earlier today, so I am back to Pangolin 1.12.3. Furthermore, I did not change anything with Nextcloud, and all is running just fine.

I've been using Pangolin for around 2 months now and did every upgrade without trouble. I am not sure why the latest version causes problems with WebSocket.

Environment

  • OS Type & Version: Ubuntu 24.04.3 LTS
  • Pangolin Version: 1.13.0
  • Gerbil Version: 1.3.0
  • Traefik Version: 3.6.4
  • Newt Version: 1.7.0
  • Olm Version: (if applicable)

To Reproduce

Just upgraded from 1.12.3 to 1.13.0 with all requirements.

Expected Behavior

Nextcloud Office should open up, and there should be no syncing problems with the Nextcloud calendar.

Originally created by @i-byrana on GitHub (Dec 12, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2059 ### Describe the Bug Hello there! I have been using the latest Nextcloud AIO (Unraid "Homelab") with Pangolin 1.12.3 (OVH VPS) without any problems. Today I did the upgrade to Pangolin 1.13.0 with all requirements, including Traefik from 3.6.2 to 3.6.4. After the upgrade I thought everything went fine, as usual. I was able to log into Nextcloud and use mostly everything. Strangely, I am unable to use Nextcloud Office (Collabora) anymore, and shared calendars won't work either. I am unable to open up or create a document, nor am I able to write an appointment into the calendar. The sync from smartphone via DAVx does not work and shows a 400 error. I get a WebSocket error if I want to open Collabora and add an appointment. I restored an update of the VPS from earlier today, so I am back to Pangolin 1.12.3. Furthermore, I did not change anything with Nextcloud, and all is running just fine. I've been using Pangolin for around 2 months now and did every upgrade without trouble. I am not sure why the latest version causes problems with WebSocket. ### Environment - OS Type & Version: Ubuntu 24.04.3 LTS - Pangolin Version: 1.13.0 - Gerbil Version: 1.3.0 - Traefik Version: 3.6.4 - Newt Version: 1.7.0 - Olm Version: (if applicable) ### To Reproduce Just upgraded from 1.12.3 to 1.13.0 with all requirements. ### Expected Behavior Nextcloud Office should open up, and there should be no syncing problems with the Nextcloud calendar.
GiteaMirror commented 2026-04-30 04:53:35 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Dec 12, 2025):

Hello!

Do you use rules to make this work?

Would you be able to replicate and open the browser console to see what
paths are being blocked thats causing Nextcloud to be unhappy?

Could you also try temporarily disabling auth on the resource to see if
that fixes it?

<!-- gh-comment-id:3647961965 --> @oschwartz10612 commented on GitHub (Dec 12, 2025): Hello! Do you use rules to make this work? Would you be able to replicate and open the browser console to see what paths are being blocked thats causing Nextcloud to be unhappy? Could you also try temporarily disabling auth on the resource to see if that fixes it?
GiteaMirror commented 2026-04-30 04:53:36 -05:00
Author
Owner
Copy Link

@i-byrana commented on GitHub (Dec 12, 2025):

I am not sure if you mean IP rules in Pangolin. If so, I only use geolocation-based rules and no other authentication. I just rolled back the VPS backup. I will try your suggestion tomorrow, as I am a bit fatigued from an infection.

<!-- gh-comment-id:3647998842 --> @i-byrana commented on GitHub (Dec 12, 2025): I am not sure if you mean IP rules in Pangolin. If so, I only use geolocation-based rules and no other authentication. I just rolled back the VPS backup. I will try your suggestion tomorrow, as I am a bit fatigued from an infection.
GiteaMirror commented 2026-04-30 04:53:36 -05:00
Author
Owner
Copy Link

@JonasSchubert commented on GitHub (Dec 12, 2025):

Hi @i-byrana,

I saw your remark regarding the traefik upgrade:

including Traefik from 3.6.2 to 3.6.4.

This included some changes due to some vulnerabilities which could be considered breaking:
https://doc.traefik.io/traefik/v3.6/migrate/v3/#v364

Starting with v3.6.3, for security reasons, Traefik now rejects requests with a path containing a specific set of encoded characters by default.

When such a request is received, Traefik responds with a 400 Bad Request status code.

Also have a look at https://www.reddit.com/r/selfhosted/comments/1ph9jio/traefik_v364_breaks_nextcloud_officecollabora/

Try to configure encodedCharacters as suggested in the reddit link.

<!-- gh-comment-id:3648047408 --> @JonasSchubert commented on GitHub (Dec 12, 2025): Hi @i-byrana, I saw your remark regarding the traefik upgrade: > including Traefik from 3.6.2 to 3.6.4. This included some changes due to some vulnerabilities which could be considered breaking: https://doc.traefik.io/traefik/v3.6/migrate/v3/#v364 > Starting with v3.6.3, for security reasons, Traefik now rejects requests with a path containing a specific set of encoded characters by default. > > When such a request is received, Traefik responds with a 400 Bad Request status code. Also have a look at https://www.reddit.com/r/selfhosted/comments/1ph9jio/traefik_v364_breaks_nextcloud_officecollabora/ Try to configure `encodedCharacters` as suggested in the reddit link.
GiteaMirror commented 2026-04-30 04:53:37 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Dec 12, 2025):

Thanks so much @JonasSchubert I did not know that!

<!-- gh-comment-id:3648051324 --> @oschwartz10612 commented on GitHub (Dec 12, 2025): Thanks so much @JonasSchubert I did not know that!
GiteaMirror commented 2026-04-30 04:53:38 -05:00
Author
Owner
Copy Link

@didotb commented on GitHub (Dec 13, 2025):

Hi all, could this be the reason why the GHCR doesn't have a 1.13.0 tag available?

<!-- gh-comment-id:3649034970 --> @didotb commented on GitHub (Dec 13, 2025): Hi all, could this be the reason why the GHCR doesn't have a 1.13.0 tag available?
GiteaMirror commented 2026-04-30 04:53:39 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Dec 13, 2025):

I am mirroring them now. It was a mistake on build @didotb.

<!-- gh-comment-id:3649514965 --> @oschwartz10612 commented on GitHub (Dec 13, 2025): I am mirroring them now. It was a mistake on build @didotb.
GiteaMirror commented 2026-04-30 04:53:40 -05:00
Author
Owner
Copy Link

@i-byrana commented on GitHub (Dec 13, 2025):

Thanks for the help. Especially Jonas. I have not tried to fix it, but it seems not to be hard. Thanks for the hint. I am only 6 months into the self-hosting journey; I do feel challenged from time to time. :) Thanks again.

<!-- gh-comment-id:3649538314 --> @i-byrana commented on GitHub (Dec 13, 2025): Thanks for the help. Especially Jonas. I have not tried to fix it, but it seems not to be hard. Thanks for the hint. I am only 6 months into the self-hosting journey; I do feel challenged from time to time. :) Thanks again.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#8826
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?