Upgrade to 31.0.5 Failed due to Notify_Push

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

  • Nextcloud Server version (e.g., 29.x.x):
    • 31.0.4
  • Operating system and version (e.g., Ubuntu 24.04):
    • Armbian 24.11.1 for Raspberry Pi 5, NextcloudPi vapa1.55.4
  • Web server and version (e.g, Apache 2.4.25):
    • apache2-2.4.62-1~deb12u2.arm64
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • replace me
  • PHP version (e.g, 8.3):
    • php8.3-fpm-8.3.21-1+0~20250509.62+debian12~1.gbpd2ac5c.arm64
  • Is this the first time you’ve seen this error? (Yes / No):
    • No
  • When did this problem seem to first start?
    • Upgrade from 31.0.2 to 31.0.4
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • NCP
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • No

Summary of the issue you are facing:

During the recent attempts of using ncp-config to upgrade Nextcloud instance( by invoking nc-update-nextcloud), I encountered below error to fetch updates for notifiy_push.

...
Error: cURL error 28: Failed to connect to github.com port 443 after 134230 ms: Couldn't connect to server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://github.com/nextcloud-releases/notify_push/releases/download/v1.1.0/notify_push-v1.1.0.tar.gz
Abort
Clean up...
Rolling back to backup /var/www/nextcloud-bkp_20250604_1748991479-31.0.4.tar.gz...
...

The instance already have the most up-to-date version installed, hence this app update seems to be quite redundant:

sudo -u www-data ncc app:list
Enabled:
...
- notify_push: 1.1.0
...

The error itself surely related with my network condition. Trying in another time would probably do the wonder, like what I had with 31.0.3 to 31.0.4. But this step of trying to get the update of the same version installed again, seems to be counterintuitive. Does anyone know the reason?

Or should I proceed to file a bug to NCP?

Thanks in advance!

Apps

Enabled:
  - activity: 4.0.0
  - admin_audit: 1.21.0
  - app_api: 5.0.2
  - bruteforcesettings: 4.0.0
  - calendar: 5.3.1
  - carnet: 0.25.6
  - circles: 31.0.0
  - cloud_federation_api: 1.14.0
  - comments: 1.21.0
  - contacts: 7.1.3
  - contactsinteraction: 1.12.0
  - dashboard: 7.11.0
  - dav: 1.33.0
  - federatedfilesharing: 1.21.0
  - federation: 1.21.0
  - files: 2.3.1
  - files_downloadlimit: 4.0.0
  - files_external: 1.23.0
  - files_pdfviewer: 4.0.0
  - files_reminders: 1.4.0
  - files_sharing: 1.23.1
  - files_trashbin: 1.21.0
  - files_versions: 1.24.0
  - firstrunwizard: 4.0.0
  - forms: 5.1.0
  - logreader: 4.0.0
  - lookup_server_connector: 1.19.0
  - nextcloud_announcements: 3.0.0
  - nextcloudpi: 0.0.2
  - notes: 4.12.1
  - notifications: 4.0.0
  - notify_push: 1.1.0
  - oauth2: 1.19.1
  - password_policy: 3.0.0
  - privacy: 3.0.0
  - profile: 1.0.0
  - provisioning_api: 1.21.0
  - recommendations: 4.0.0
  - related_resources: 2.0.0
  - serverinfo: 3.0.0
  - settings: 1.14.0
  - sharebymail: 1.21.0
  - support: 3.0.0
  - survey_client: 3.0.0
  - suspicious_login: 9.0.1
  - systemtags: 1.21.1
  - tasks: 0.16.1
  - text: 5.0.0
  - theming: 2.6.1
  - twofactor_backupcodes: 1.20.0
  - user_ldap: 1.22.0
  - user_status: 1.11.0
  - viewer: 4.0.0
  - weather_status: 1.11.0
  - webhook_listeners: 1.2.0
  - workflowengine: 2.13.0
Disabled:
  - encryption: 2.19.0 (installed 2.4.0)
  - photos: 4.0.0-dev.1 (installed 4.0.0-dev.1)
  - previewgenerator: 99.99.99 (installed 3.1.1)
  - twofactor_nextcloud_notification: 5.0.0
  - twofactor_totp: 13.0.0-dev.0
  - updatenotification: 1.21.0 (installed 1.21.0)

Have you tried the following…?

  1. disable notify_push by occ command

  2. remove notify_push by occ command

  3. re-try the update by …/nextcloud/updater/updater.phar
    → Upgrade via built-in updater — Nextcloud latest Administration Manual latest documentation

  4. after (possible successful) update check integrity by occ

  5. re-install notify_push by occ command

  6. check if everything works fine now.

Hope this helps.
Cheers :slight_smile:

Many thanks for the quick reply!

From the search results of existing posts, it seems to suggest the NCP updater is preferred over the built-in updater. Is it still the case?

Nevertheless, I did try your suggested approach of disabling and removing notify_push before using NCP updater.
It failed at the same part.

It appears that this notify_push app was a hard dependency for NCP updater. Quite strange…

Well, just as predicted, it works in another day when the network reliability was better:

Running nc-update-nextcloud
Running as unit: ncp-update-nc.service
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  885k    0  885k    0     0   225k      0 --:--:--  0:00:03 --:--:--  225k
Current   Nextcloud version 31.0.4
Requested Nextcloud version latest
Selected  Nextcloud version 31.0.5
INFO: You have requested an update to the latest available version that can be performed directly, which is '31.0.5'. Updates can only performed to the next major version (or the latest minor version of the current major version). If you run ncp-update-nc again after this update completes, a new version might be available.
Download Nextcloud 31.0.5...
Back up current instance...
check free space...
Maintenance mode enabled
backup database...
backup files...
backup /var/www/nextcloud-bkp_20250608_1749383000.tar.gz generated
Maintenance mode disabled
Storing backup at '/var/www/nextcloud-bkp_20250608_1749383000-31.0.4.tar.gz'...
Install Nextcloud 31.0.5...
Fix permissions...
Upgrade...
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Setting log level to debug
Turned on maintenance mode
Updating database schema
Updated database
Disabled incompatible app: calendar
Disabled incompatible app: contacts
Disabled incompatible app: forms
Disabled incompatible app: notes
Disabled incompatible app: notify_push
Disabled incompatible app: tasks
Starting code integrity check...
Finished code integrity check
Update successful
Turned off maintenance mode
Resetting log level
Adding additional cards_prop_abid_name_value index to the oc_cards_properties table, this can take some time...
Removing cards_prop_abid index from the oc_cards_properties table
oc_cards_properties table updated successfully.
Done.
Done.
All tables already up to date!
 - Repair MySQL collation
     - All tables already have the correct collation -> nothing to do
 - Clean tags and favorites
     - 0 tags of deleted users have been removed.
     - 0 tags for delete files have been removed.
     - 0 tag entries for deleted tags have been removed.
     - 0 tags with no entries have been removed.
 - Repair invalid shares
 - Move .step file of updater to backup location
 - Add move avatar background job
     - Repair step already executed
 - Add preview cleanup background jobs
 - Migrate oauth2_clients table to nextcloud schema
     - Update the oauth2_access_tokens table schema.
     - Update the oauth2_clients table schema.
     - Delete clients (and their related access tokens) with the redirect_uri starting with oc:// or ending with *
 - Repair language codes
 - Add log rotate job
 - Clear frontend caches
     - Image cache cleared
     - JS cache cleared
 - Clear every generated avatar
 - Add preview background cleanup job
 - Queue a one-time job to cleanup old backups of the updater
 - Cleanup invalid photocache files for carddav
 - Add background job to cleanup login flow v2 tokens
 - Remove potentially over exposing share links
     - No need to remove link shares.
 - Clear access cache of projects
 - Reset generated avatar flag
 - Keep legacy encryption enabled
 - Check encryption key format
 - Remove old dashboard app config data
 - Add job to cleanup the bruteforce entries
 - Queue a one-time job to check for user uploaded certificates
 - Repair DAV shares
 - Add background job to set the lookup server share state for users
 - Add token cleanup job
 - Clean up abandoned apps
 - Add possibly missing system config
 - Add AI tasks cleanup jobs
 - Queue a job to generate metadata
 - migrate lazy config values
 - Cache logo dimension to fix size in emails on Outlook
     - Logo dimensions are already known
 - Remove legacy ".ocdata" file
 - Add cleanup-deleted-users background job
 - Validate account properties and store phone numbers in a known format for search
     - Queued background to validate account properties.
 - Remove shares of old group memberships
 - Remove broken DAV object properties
     - 0 broken object properties removed
 - Repair mime types
 - Handle outdated scheduling events
     - Cleaning up old scheduling events
 - AppAPI Daemons configuration GPU params update
     - Daemons configuration GPU params updated: 0
 - Upgrading Circles App
 - Fix component of birthday calendars
     - 8 birthday calendars updated.
 - Regenerating birthday calendars to use new icons and fix old birthday events without year
     - Repair step already executed
 - Fix broken values of calendar objects
    0 [>---------------------------]
 - Registering building of calendar search index as background job
     - Repair step already executed
 - Register building of social profile search index as background job
     - Repair step already executed
 - Registering background jobs to update cache for webcal calendars
     - Added 0 background jobs to update webcal calendars
 - Registering building of calendar reminder index as background job
     - Repair step already executed
 - Clean up orphan event and contact data
     - 0 events without a calendar have been cleaned up
     - 0 properties without an events have been cleaned up
     - 0 changes without a calendar have been cleaned up
     - 0 cached events without a calendar subscription have been cleaned up
     - 0 changes without a calendar subscription have been cleaned up
     - 0 contacts without an addressbook have been cleaned up
     - 0 properties without a contact have been cleaned up
     - 0 changes without an addressbook have been cleaned up
 - Remove activity entries of private events
     - Removed 0 activity entries
 - Clean up old calendar subscriptions from deleted users that were not cleaned-up
    0 [->--------------------------]
     - 0 calendar subscriptions without an user have been cleaned up
 - Remove invalid object properties
     - 0 invalid object properties removed.
 - Fix the share type of guest shares when migrating from ownCloud
 - Copy the share password into the dedicated column
 - Set existing shares as accepted
 - Update OAuth token expiration times
 - Switches from default updater server to the customer one if a valid subscription is available
     - Repair step already executed
 - Migrate some config values to lazy loading
 - Send an admin notification if monthly report is disabled
 - Force-reset all Text document sessions
 - Initialize migration of background images from dashboard to theming app
 - Add background job to check for backup codes
 - Insert UUIDFix background job for user and group in batches
 - Remove deprecated refresh time markers for LDAP user records
 - Populating added database structures for workflows
**notify_push 1.1.0 installed**
**notify_push enabled**
**notify_push already enabled**
Installing template 'nextcloud.conf.sh'...
INFO: Metrics enabled: no
Apache self check:
Syntax OK
Module proxy already enabled
Considering dependency proxy for proxy_http:
Module proxy already enabled
Module proxy_http already enabled
Considering dependency proxy for proxy_wstunnel:
Module proxy already enabled
Module proxy_wstunnel already enabled
Installing template 'systemd/notify_push.service.sh'...
System config value trusted_domains => 3 set to string nextcloudpi
System config value overwrite.cli.url set to string https://nextcloudpi/
System config value trusted_proxies => 11 set to string 127.0.0.1
System config value trusted_proxies => 12 set to string ::1
Setup notify_push (attempt 1/5)
âś“ redis is configured
âś“ push server is receiving redis messages
âś“ push server can load mount info from database
âś“ push server can connect to the Nextcloud server
âś“ push server is a trusted proxy
âś“ push server is running the same version as the app
  configuration saved
Update completed successfully.
Backup stored at /mnt/ncdata/data/ncp-update-backups/nextcloud-bkp_20250608_1749383000-31.0.4.tar.gz
Clean up...
Nextcloud update finished successfully.
Done. Press any key...

Note how the notify_push was forcedly downloaded and installed(?) by the updater.

This topic was automatically closed after 90 days. New replies are no longer allowed.