Upgrading from 33.0.3 to 34.0.1 doesn't work via nextcloudpi

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

I run nextcloud in a nextcloudpi LXC on top of proxmox.

It has haproxy as a reverse proxy in front of it, in a separate LXC.

NextcloudPi version v1.57.1
NextcloudPi image NextcloudPi_lxc_10-15-24
OS Debian GNU/Linux 12 (bookworm). 7.0.12-1-pve (x86_64)
automount no
USB devices sdh sr0
datadir /opt/ncdata/data
data in SD yes
data filesystem zfs
data disk usage 302G/1000G
rootfs usage 302G/1000G
swapfile none
dbdir /var/lib/mysql
Nextcloud check ok
Nextcloud version 33.0.3.2
HTTPD service up
PHP service up
MariaDB service up
Redis service up
HPB service up
Postfix service up
Internet check ok
Public IPv4 not found
Public IPv6 not found
Port 80 [N/A]
Port 443 [N/A]
IP 192.168.1.201
Gateway 192.168.1.1
Interface eth0
Certificates none
NAT loopback no
Uptime 1day

Summary of the issue you are facing:

I can’t update nextcloud to 34.0.1 using nextcloudpi, I get this error:

nc-update-nextcloud write error

I have checked if the disk is full, and have rebooted the LXC, neither of which fixed this issue.

Steps to replicate it (hint: details matter!):slight_smile:

  1. log into ncp admin panels
  2. click on nc-update-nextcloud
  3. enter 0 as the desired version (newest), or 34.0.1 (tried both)
  4. click Apply
  5. the error from the summary shows.

Log entries

Nextcloud

Fatal
	no app in context
	
Capabilities of OCA\Files\DirectEditingCapabilities took 1.87 seconds to generate.
	Jun 27, 2026, 7:07:41 PM
	
Error
	core
	
1 two-factor auth providers failed to load
	Jun 27, 2026, 6:47:01 PM
	
Error
	core
	
two-factor auth provider 'webauthn' failed to load
	Jun 27, 2026, 6:47:01 PM
	
Error
	core
	
1 two-factor auth providers failed to load
	Jun 27, 2026, 6:47:01 PM
	
Error
	core
	
two-factor auth provider 'webauthn' failed to load
	Jun 27, 2026, 6:47:01 PM
	
Error
	core
	
1 two-factor auth providers failed to load
	Jun 27, 2026, 6:46:56 PM
	
Error
	core
	
two-factor auth provider 'webauthn' failed to load
	Jun 27, 2026, 6:46:56 PM
	
Error
	core
	
1 two-factor auth providers failed to load
	Jun 27, 2026, 6:46:54 PM
	
Error
	core
	
two-factor auth provider 'webauthn' failed to load
	Jun 27, 2026, 6:46:54 PM
	
Error
	core
	
1 two-factor auth providers failed to load
	Jun 27, 2026, 6:46:54 PM
	
Error
	core
	
two-factor auth provider 'webauthn' failed to load
	Jun 27, 2026, 6:46:54 PM
	
Warning
	no app in context
	
Capabilities of OCA\Provisioning_API\Capabilities took 0.42 seconds to generate.
	Jun 27, 2026, 6:34:31 PM
	
Warning
	no app in context
	
Capabilities of OCA\Circles\AppInfo\Capabilities took 0.68 seconds to generate.
	Jun 27, 2026, 6:34:31 PM
	
Warning
	no app in context
	
Capabilities of OCA\Circles\AppInfo\Capabilities took 0.49 seconds to generate.
	Jun 27, 2026, 2:19:27 PM
	
Warning
	no app in context
	
Capabilities of OCA\Files\DirectEditingCapabilities took 0.63 seconds to generate.

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

{
    "system": {
        "passwordsalt": "***REMOVED SENSITIVE VALUE***",
        "secret": "***REMOVED SENSITIVE VALUE***",
        "trusted_domains": {
            ***REMOVED SENSITIVE VALUE***
        },
        "overwritehost": ***REMOVED SENSITIVE VALUE***,
        "overwritewebroot": "",
        "htaccess.RewriteBase": "\/",
        "datadirectory": "***REMOVED SENSITIVE VALUE***",
        "dbtype": "mysql",
        "version": "33.0.3.2",
        "overwrite.cli.url": "https:\/\/nextcloudpi\/",
        "dbname": "***REMOVED SENSITIVE VALUE***",
        "dbhost": "***REMOVED SENSITIVE VALUE***",
        "dbport": "",
        "dbtableprefix": "oc_",
        "mysql.utf8mb4": true,
        "dbuser": "***REMOVED SENSITIVE VALUE***",
        "dbpassword": "***REMOVED SENSITIVE VALUE***",
        "installed": true,
        "instanceid": "***REMOVED SENSITIVE VALUE***",
        "memcache.local": "\\OC\\Memcache\\Redis",
        "memcache.locking": "\\OC\\Memcache\\Redis",
        "redis": {
            "host": "***REMOVED SENSITIVE VALUE***",
            "port": 0,
            "timeout": 0,
            "password": "***REMOVED SENSITIVE VALUE***"
        },
        "tempdirectory": "\/opt\/ncdata\/data\/tmp",
        "skeletondirectory": "\/opt\/ncdata\/data\/skeleton",
        "mail_smtpmode": "sendmail",
        "mail_smtpauthtype": "LOGIN",
        "mail_from_address": "***REMOVED SENSITIVE VALUE***",
        "mail_domain": "***REMOVED SENSITIVE VALUE***",
        "preview_max_x": "2048",
        "preview_max_y": "2048",
        "jpeg_quality": "60",
        "overwriteprotocol": "https",
        "maintenance": false,
        "logfile": "\/opt\/ncdata\/data\/nextcloud.log",
        "trusted_proxies": "***REMOVED SENSITIVE VALUE***",
        "loglevel": "2",
        "log_type": "file",
        "theme": "",
        "twofactor_enforced": "true",
        "twofactor_enforced_groups": [
            "admin"
        ],
        "twofactor_enforced_excluded_groups": [],
        "serverid": 692
    }
}

Apps

The output of occ app:list (if possible).

Enabled:

  • activity: 6.0.0
  • admin_audit: 1.23.0
  • bruteforcesettings: 6.0.0
  • circles: 33.0.0
  • cloud_federation_api: 1.17.0
  • comments: 1.23.0
  • contactsinteraction: 1.14.1
  • dashboard: 7.13.0
  • dav: 1.36.0
  • federatedfilesharing: 1.23.0
  • federation: 1.23.0
  • files: 2.5.0
  • files_downloadlimit: 5.1.0
  • files_external: 1.25.1
  • files_pdfviewer: 6.0.0
  • files_reminders: 1.6.0
  • files_sharing: 1.25.2
  • files_trashbin: 1.23.0
  • files_versions: 1.26.0
  • firstrunwizard: 6.0.0
  • logreader: 6.0.0
  • lookup_server_connector: 1.21.0
  • nextcloud_announcements: 5.0.0
  • notifications: 6.0.0
  • notify_push: 1.3.3
  • oauth2: 1.21.0
  • password_policy: 5.0.0
  • photos: 6.0.0
  • previewgenerator: 5.13.0
  • privacy: 5.0.0
  • profile: 1.2.0
  • provisioning_api: 1.23.0
  • recommendations: 6.0.0
  • related_resources: 4.0.0
  • serverinfo: 5.0.0
  • settings: 1.16.0
  • sharebymail: 1.23.0
  • support: 5.0.0
  • survey_client: 5.0.0
  • systemtags: 1.23.0
  • text: 7.0.1
  • theming: 2.8.0
  • twofactor_backupcodes: 1.22.0
  • twofactor_totp: 15.0.0
  • user_status: 1.13.0
  • viewer: 6.0.0
  • weather_status: 1.13.0
  • webhook_listeners: 1.5.0
  • workflowengine: 2.15.0
  • Disabled:
  • app_api: 33.0.0 (installed 32.0.0)
  • encryption: 2.21.0
  • nextcloudpi: 0.0.2 (installed 0.0.2)
  • suspicious_login: 11.0.0
  • testing: 1.23.0
  • twofactor_nextcloud_notification: 7.0.0
  • updatenotification: 1.23.0 (installed 1.19.1)
  • user_ldap: 1.24.0

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.

Nextcloudpi is not ready to update to nc 34.x or to debian 13 trixie yet, I think work is in progress..
You may be able to update to the latest 33.x version on cli
sudo ncp-update-nc 0
or explicit
sudo ncp-update-nc 33.0.6
as long as you get your access thing -webauthn- working.

the pro of NCP is: it’s mostly a no-brainer, you need to answer some basic questions and do some twinkle here and there (they’ll tell you exactly what to do) and you’re done.
the con of it is: you need to wait for it to be ready doing the upgrade. Being ready means… someone needs to adjust the installing procedure and testrun it on several systems first before it’ll be deployed to every NCP-user.

So be patient and wait… as long as it’ll take.

apart from that… pls get away from the idea if upgrading to a new major version immediately. usually it runs smoother from Vx.0.2 on. Trust me

Ok, doing it in CLI instead of the web UI worked, but only to 33.0.6.

@JimmyKater
I usually try it when I get notified of the major release, but I always create a zfs snapshot of the LXC first, so nothing can go awry.

prolly yes. but it could break the ncp.-logic though.