[BUG] wrong image is set to latest causing issues with upgraded data

Is there an existing issue for this?

I have searched the existing issues

Current Behavior

Hello. It looks like the "latest" tag here is causing issues for users that have "latest" as their image tag. Just making sure someone is aware because it took down my NextCloud instance and I needed to revert to "34.0.0-ls435" to fix the error. I've pasted the logs from before switching my image from latest manually

Expected Behavior

It looks like the CI bumped 33.0.5-ls436 as the latest or perhaps 34.0.0-ls435 shouldn't be latest yet?

Steps To Reproduce

I experienced this because it seems that Watchtower pulled "linuxserver/nextcloud:latest" when 34.0.0-ls435 was the latest version, then 2 hrs later the latest reverted a major version.

Manual recreation:

Manually set your release to "linuxserver/nextcloud:34.0.0-ls435"
Let container start up
Set release to "image: linuxserver/nextcloud:latest"
Observe logs

For those not doing auto-updates, you are likely unaffected.

Environment

- OS:Docker: Ubuntu 22.04
- distro's packagemanager

CPU architecture

x86-64

Docker creation

nextcloud:
    container_name: NextCloud
    environment:
      PGID: '1000'
      PUID: '1000'
      TZ: America/Chicago
    image: linuxserver/nextcloud:latest
    networks:
      proxy: null
    ports:
    - published: 32779
      target: 443
    restart: unless-stopped
    volumes:
    - /var/lib/nextcloud/config:/config:rw
    - /mnt/container_data/nextcloud/data:/data:rw

Container logs

[migrations] started [migrations] 01-nginx-site-confs-default: skipped [migrations] 02-default-location: skipped [migrations] done ─────────────────────────────────────── ██╗ ███████╗██╗ ██████╗ ██║ ██╔════╝██║██╔═══██╗ ██║ ███████╗██║██║ ██║ ██║ ╚════██║██║██║ ██║ ███████╗███████║██║╚██████╔╝ ╚══════╝╚══════╝╚═╝ ╚═════╝ Brought to you by linuxserver.io ─────────────────────────────────────── To support LSIO projects visit: https://www.linuxserver.io/donate/ ─────────────────────────────────────── GID/UID ─────────────────────────────────────── User UID: 1000 User GID: 1000 ─────────────────────────────────────── Linuxserver.io version: 33.0.5-ls436 Build-date: 2026-06-08T16:37:53+00:00 ─────────────────────────────────────── using keys found in /config/keys **** The following active confs have different version dates than the samples that are shipped. **** **** This may be due to user customization or an update to the samples. **** **** You should compare the following files to the samples in the same folder and update them. **** **** Use the link at the top of the file to view the changelog. **** ┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐ │ old date │ new date │ path │ ├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤ │ 2023-08-13 │ 2025-07-18 │ /config/nginx/ssl.conf │ │ 2023-04-13 │ 2025-05-31 │ /config/nginx/nginx.conf │ │ 2023-06-23 │ 2025-07-10 │ /config/nginx/site-confs/default.conf │ └────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘ Can't start Nextcloud because the version of the data (34.0.0.12) is higher than the docker image version (33.0.5.1) and downgrading is not supported. Are you sure you have pulled the newest image version?

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

Unfortunately looks like nextcloud messed up their release as they reversed v34 to a pre-release and our :latest tag reverted to v33. Little we can do about this.

Also, this is an example for why we don't recommend automatic updates and to pin tag versions rather than running latest.

same issue here although v34 has locked me into maintenance mode as well :/

Confirming using tag "34.0.0-ls435" worked for me!

Also, this is an example for why we don't recommend automatic updates and to pin tag versions rather than running latest.

Your're right, but it's also not a good solution to retagging a older version to "latest".

I agree, Nextcloud should have a proper release pipeline. We just relay what their newest non-prerelease is, when they pull a release, a downgrade will happen. It is not the first time Nextcloud has done this great move.

Sigh...I fell for it again and ended up with a new Nextcloud major release on day one...
...when will I learn?

Anyhow - my comments here have nothing to do with the docker image.
Sharing for those, like me, who are waking up to an unpleasant surprise.

I went straight to 34.0.0-ls437 and avoided the shenanigans specified above.
After update, web interface appeared stuck in maintenance mode - but it was not maintenance mode. It was a login error screen.
# grep "ERROR_ID" /data/nextcloud.log to figure out what's happening.
See error related to incompatible apps that the nextcloud update process didn't disable as pasrt of the upgrade process.

# occ app:disable camerarawpreviews
# occ app:disable suspucious_login

I suspect those encountering the same issue are using suspucious_login.
I think that's enabled by default in most installs.

I had the exact same issue after the update and wanted to share what fixed it for me.

The container itself looked healthy, and Nextcloud reported:

version: 34.0.0.12
maintenance: false
needsDbUpgrade: false

The browser only showed a generic "Internal Server Error" page, while the mobile app continued to work normally.

I checked the Nextcloud log with:

tail -100 /data/nextcloud.log

and analyzed the error output with a local LLM. In my case, the actual problem was not Nextcloud itself but the files_3dmodelviewer app.

The log contained errors similar to:

Call to undefined method
OCP\AppFramework\Http\EmptyContentSecurityPolicy::allowEvalScript()

originating from:

apps/files_3dmodelviewer/

I fixed it by disabling the app:

occ app:disable files_3dmodelviewer

and then running:

occ maintenance:repair

After that, Nextcloud started working normally again.

If anyone else is seeing internal server errors after upgrading to NC34, it may be worth checking /data/nextcloud.log for references to incompatible apps before rebuilding the container or rolling back versions.

@HartLander

Thanks @PnjDbq & @HartLander

I also had the same "Internal Server Error" page after logging into Nextcloud on version 34.0.0.12 (34.0.0-ls437).

In my case it was the suspicious_login app causing the issue. Disabling that app with the following line fixed it:

occ app:disable suspicious_login

No occ maintenance:repair or reboot was necessary on my end.

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

Navigation Menu

Repository navigation

[BUG] wrong image is set to latest causing issues with upgraded data #541

Is there an existing issue for this?

Current Behavior

Expected Behavior

Steps To Reproduce

Environment

CPU architecture

Docker creation

Container logs

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[BUG] wrong image is set to latest causing issues with upgraded data #541

Description

Is there an existing issue for this?

Current Behavior

Expected Behavior

Steps To Reproduce

Environment

CPU architecture

Docker creation

Container logs

Activity

github-actions commented on Jun 8, 2026

j0nnymoe commented on Jun 8, 2026

j0nnymoe commented on Jun 8, 2026

Pel1can111 commented on Jun 8, 2026

lbesnard commented on Jun 9, 2026

EiTiFuzzi commented on Jun 9, 2026

Roxedus commented on Jun 9, 2026

Amusable-design commented on Jun 9, 2026

HartLander commented on Jun 13, 2026

cipherings commented on Jun 16, 2026

LinuxServer-CI commented on Jul 17, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions