linuxserver/docker-nextcloud

[BUG] CORP Failures - NC 29

kstorbakken opened this issue · 2 comments

kstorbakken commented

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

I recently upgraded from NC 28 to NC 29. Most things are working just fine, but there’s a few pages that fail to load properly. Mainly the map in PhoneTrack, and all the pictures in Memories.

I noticed in my browser console output, I’m receiving errors like this when trying to load images from https://a.tile.openstreetmap.org :
ERR_BLOCKED_BY_RESPONSE.NotSameOriginAfterDefaultedToSameOriginByCoep

For the Memories app, I see this failing to load: https://nextcloud.mydomain.com/apps/memories/js/memories-components_frame_XImgWorkerStub_ts.js?v=c995126c0962cc8aa175
I’m fairly certain that’s why none of my pictures are loading. It’s marked as blocked for a similar cross-origin-embedder-policy missing error.

Nothing has changed in regard to my reverse proxy setup. What could be causing this?

I’ve thoroughly reviewed error logs as outlined below but I’ve found nothing relevant.

Expected Behavior

All the pages load without Cross-Origin-Resource-Policy errors

Steps To Reproduce

NC 28 --> NC29 upgrade

Environment

- OS:Rocky 9
- How docker service was installed: using Podman 4.9.4 from repo

CPU architecture

x86-64

Docker creation

Quadlet file I use, it gets deployed via ansible and fills in the jinja templates below
[Unit]
Description=nextcloud
Requires=nextcloud_postgres.service
After=network-online.target nextcloud_postgres.service

[Container]
ContainerName=nextcloud
Image=docker.io/linuxserver/nextcloud:{{ nextcloud_version }}
PublishPort=8888:443
Network=nextcloud.network
Volume={{ nextcloud_path }}/config:/config:Z
Volume={{ nextcloud_path }}/data:/data:Z
AutoUpdate=registry

[Install]
WantedBy=default.target

Container logs

[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    911
User GID:    911
───────────────────────────────────────
Linuxserver.io version: 29.0.6-ls337
Build-date: 2024-09-03T10:41:56+00:00
───────────────────────────────────────
    
using keys found in /config/keys
Initializing nextcloud 29.0.6.1 (this can take a while) ...
Setting permissions
Initializing finished
[custom-init] No custom files found, skipping...
[ls.io-init] done.
github-actions commented

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

kstorbakken commented

I've reverted my nextcloud from backups to 28 after some testing and making sure it wouldn't cause any kind of data loss. It wasn't too bad to just restore the config folders and the database and then re-scan files and app data to catch any newer data.

Since I can't find anyone else with a similar issue, it's clear to me its a problem on my end. I'll have to do more testing and try it again.