Nextcloud 32.0.1 Calender App not not available after a few hours of runtime

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):
    • 32.0.1
  • Operating system and version (e.g., Ubuntu 24.04):
    • Ubuntu Server 22.04 LTS
  • Web server and version (e.g, Apache 2.4.25):
    • 2.4.63
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • not in use
  • PHP version (e.g, 8.3):
    • 8.4
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • When updating from 32.0.0 to 32.0.1
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • Bare Metal
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • No

Summary of the issue you are facing:

[…]

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

  1. When trying to open Calender it shows “Site not found“ and I have a button to go to the previous site

  2. When then downgrading the Calender App version it becomes available again for a few hours

  3. After a few hours the same error occurs. Only manually replacing the files of the calender app in /var/www/nextcloud/apps seems to fix the issue for a few hours.

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

No calendar events found for status check

The requested alias "OCP\AppFramework\IAppContainer" is deprecated. Please request "Psr\Container\ContainerInterface" directly. This alias will be removed in a future Nextcloud version.


Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

Im getting a 404 for https://*.*/apps/calendar

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

[Mon Nov 17 00:00:00.622804 2025] [mpm_event:notice] [pid 512485:tid 512485] AH00489: Apache/2.4.63 (Ubuntu) OpenSSL/1.1.1f configured -- resuming normal operations
[Mon Nov 17 00:00:00.622824 2025] [core:notice] [pid 512485:tid 512485] AH00094: Command line: '/usr/sbin/apache2'
[Mon Nov 17 07:54:29.454141 2025] [mpm_event:notice] [pid 512485:tid 512485] AH00492: caught SIGWINCH, shutting down gracefully
[Mon Nov 17 07:54:32.831505 2025] [core:warn] [pid 512485:tid 512485] AH00045: child process 1055527 still did not exit, sending a SIGTERM
[Mon Nov 17 07:54:34.833783 2025] [core:warn] [pid 512485:tid 512485] AH00045: child process 1055527 still did not exit, sending a SIGTERM
[Mon Nov 17 07:54:36.835987 2025] [core:warn] [pid 512485:tid 512485] AH00045: child process 1055527 still did not exit, sending a SIGTERM
[Mon Nov 17 07:54:38.838240 2025] [core:error] [pid 512485:tid 512485] AH00046: child process 1055527 still did not exit, sending a SIGKILL

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***",   
        ],
        "datadirectory": "***REMOVED SENSITIVE VALUE***",
        "dbtype": "pgsql",
        "version": "32.0.1.2",
        "overwrite.cli.url": "https:\/\/***REMOVED SENSITIVE VALUE***\/",
        "dbname": "***REMOVED SENSITIVE VALUE***",
        "dbhost": "***REMOVED SENSITIVE VALUE***",
        "dbport": "",
        "dbtableprefix": "oc_",
        "dbuser": "***REMOVED SENSITIVE VALUE***",
        "dbpassword": "***REMOVED SENSITIVE VALUE***",
        "installed": true,
        "instanceid": "***REMOVED SENSITIVE VALUE***",
        "upgrade.disable-web": "false",
        "log_type": "file",
        "logfile": "\/var\/log\/nextcloud\/nextcloud.log",
        "loglevel": 0,
        "mail_smtpmode": "smtp",
        "remember_login_cookie_lifetime": "43200",
        "log_rotate_size": "10485760",
        "trashbin_retention_obligation": "auto, 180",
        "versions_retention_obligation": "auto, 365",
        "simpleSignUpLink.shown": "false",
        "filelocking.enabled": true,
        "memcache.distributed": "\\OC\\Memcache\\Redis",
        "memcache.locking": "\\OC\\Memcache\\Redis",
        "redis": {
            "host": "***REMOVED SENSITIVE VALUE***",
            "port": 0,
            "timeout": 0.5,
            "dbindex": 0,
            "password": "***REMOVED SENSITIVE VALUE***"
        },
        "logtimezone": "Europe\/Berlin",
        "htaccess.RewriteBase": "\/",
        "share_folder": "\/Shared",
        "enable_previews": true,
        "preview_max_memory": 1280,
        "enabledPreviewProviders": {
            "11": "OC\\Preview\\PNG",
            "12": "OC\\Preview\\JPEG",
            "13": "OC\\Preview\\GIF",
            "14": "OC\\Preview\\BMP",
            "15": "OC\\Preview\\MarkDown",
            "16": "OC\\Preview\\MP3",
            "17": "OC\\Preview\\TXT",
            "18": "OC\\Preview\\Movie"
        },
        "preview_max_x": "2048",
        "preview_max_y": "2048",
        "jpeg_quality": "60",
        "ldapIgnoreNamingRules": false,
        "ldapProviderFactory": "OCA\\User_LDAP\\LDAPProviderFactory",
        "ldapUserCleanupInterval": "25",
        "maintenance": false,
        "mail_from_address": "***REMOVED SENSITIVE VALUE***",
        "mail_sendmailmode": "smtp",
        "mail_domain": "***REMOVED SENSITIVE VALUE***",
        "mail_smtphost": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpport": "587",
        "mail_smtpsecure": "tls",
        "mail_smtpauthtype": "LOGIN",
        "mail_smtpauth": 1,
        "mail_smtpname": "***REMOVED SENSITIVE VALUE***",
        "mail_smtppassword": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpstreamoptions": {
            "ssl": {
                "allow_self_signed": true,
                "verify_peer": false,
                "verify_peer_name": false
            }
        },
        "memcache.local": "\\OC\\Memcache\\Redis",
        "updater.release.channel": "stable",
        "app_install_overwrite": [],
        "maintenance_window_start": 2
    }
}

Apps

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

Enabled:

  • activity: 5.0.0-dev.0
  • admin_audit: 1.22.0
  • app_api: 32.0.0
  • bruteforcesettings: 5.0.0-dev.0
  • calendar: 5.5.6
  • circles: 32.0.0
  • cloud_federation_api: 1.16.0
  • comments: 1.22.0
  • contactsinteraction: 1.13.1
  • dashboard: 7.12.0
  • dav: 1.34.2
  • federatedfilesharing: 1.22.0
  • federation: 1.22.0
  • files: 2.4.0
  • files_downloadlimit: 5.0.0-dev.0
  • files_pdfviewer: 5.0.0-dev.0
  • files_reminders: 1.5.0
  • files_sharing: 1.24.0
  • files_trashbin: 1.22.0
  • files_versions: 1.25.0
  • firstrunwizard: 5.0.0-dev.0
  • logreader: 5.0.0-dev.0
  • lookup_server_connector: 1.20.0
  • nextcloud_announcements: 4.0.0-dev.0
  • notifications: 5.0.0-dev.0
  • oauth2: 1.20.0
  • password_policy: 4.0.0-dev.0
  • privacy: 4.0.0-dev.0
  • profile: 1.1.0
  • provisioning_api: 1.22.0
  • recommendations: 5.0.0-dev.0
  • related_resources: 3.0.0-dev.0
  • serverinfo: 4.0.0-dev.0
  • settings: 1.15.1
  • sharebymail: 1.22.0
  • support: 4.0.0-dev.0
  • survey_client: 4.0.0-dev.0
  • suspicious_login: 10.0.0-dev.0
  • systemtags: 1.22.0
  • text: 6.0.1
  • theming: 2.7.0
  • twofactor_backupcodes: 1.21.0
  • twofactor_totp: 14.0.0
  • updatenotification: 1.22.0
  • user_ldap: 1.23.0
  • user_status: 1.12.0
  • viewer: 5.0.0-dev.0
  • webhook_listeners: 1.3.0
  • workflowengine: 2.14.0
    Disabled:
  • contacts: 8.0.6 (installed 8.0.6)
  • deck: 1.16.1 (installed 1.16.1)
  • documentserver_community: 0.2.0 (installed 0.2.0)
  • encryption: 2.20.0
  • extract: 1.3.6 (installed 1.3.5)
  • files_accesscontrol: 3.0.2 (installed 3.0.2)
  • files_downloadactivity: 1.18.1 (installed 1.18.1)
  • files_external: 1.24.0
  • files_fulltextsearch: 32.0.2 (installed 32.0.2)
  • files_retention: 3.0.0 (installed 3.0.0)
  • fulltextsearch: 32.0.0 (installed 32.0.0)
  • geoblocker: 0.5.18 (installed 0.5.18)
  • groupfolders: 20.1.3 (installed 20.1.3)
  • guests: 4.6.0 (installed 4.6.0)
  • issuetemplate: 0.7.0 (installed 0.7.0)
  • mail: 5.5.15 (installed 5.5.15)
  • photos: 5.0.0-dev.1 (installed 1.0.0)
  • previewgenerator: 5.10.0 (installed 5.10.0)
  • ransomware_protection: 1.14.0 (installed 1.14.0)
  • terms_of_service: 4.6.1 (installed 4.6.1)
  • twofactor_nextcloud_notification: 6.0.0-dev.0
  • weather_status: 1.12.0 (installed 1.5.0)

We have also encountered the error with Ubuntu 20.04 LTS and PHP8.1 aswell as Postgresql12. Updating to Ubuntu 22.04 LTS, PHP8.4 and Postgresql14 had no effect.

Calendar is already at version 6.0.4. You should try updating your apps as well to make sure you have the latest versions installed.

as stated in the post, we need to change the version every few hours so our users cann still open the app. When we update to 6.0.4 the app works for a few hours and then stops working just like any other version.

So the outdated app version of Calendar works but the latest version doesn’t?

Since the update to 32.0.1 every calender Version i have tested (all 6.x versions and the 5.x version listed in the post) do work right after installation but fail after a few hours of runtime. Then to get the calender app to work again I need to downgrade or upgrade. After the version number of the calender app changes it works again for the next few hours somehow.

Very strange - all I can say is that on my Nextcloud 32.0.1 the Calendar app 6.0.4 works fine and my instance is used by more than 50 people. So sorry, I don’t know how to fix your issue.

However - the fact that requests for the Calendar app responds with 404 at some point means, that the app itself got disabled by Nextcloud, probably due to runtime errors. You should try to find out, if there is an error message in the Nextcloud log which might give a hint, what exactly failed.

Edit: this message is only a warning, not an error. So despite this warning, the app should still work, since the warning only says, that the app uses deprecated code which should be replace in the future:

The requested alias "OCP\AppFramework\IAppContainer" is deprecated. Please request "Psr\Container\ContainerInterface" directly. This alias will be removed in a future Nextcloud version.

So it only impacts Calendar? All other aspects/apps in Nextcloud remain functioning?

Hmm.

It appears you’re using PHP-FPM. Can you check your FPM logs?

Also, what specific PHP version?

And what are your opcache settings?

Yes it is only the calendar app that runs into this issue, every other app works fine.

The PHP FPM log file seems ok except for the ressource warnings. The fpm shutdown correlate with actual reboots of the system.

[16-Nov-2025 00:00:00] NOTICE: error log file re-opened
[17-Nov-2025 07:53:39] NOTICE: Terminating …
[17-Nov-2025 07:53:39] NOTICE: exiting, bye-bye!
[17-Nov-2025 07:53:39] NOTICE: fpm is running, pid 1237195
[17-Nov-2025 07:53:39] NOTICE: ready to handle connections
[17-Nov-2025 07:53:39] NOTICE: systemd monitor interval set to 10000ms
[17-Nov-2025 07:54:29] NOTICE: Terminating …
[17-Nov-2025 07:54:29] NOTICE: exiting, bye-bye!
[17-Nov-2025 07:56:36] NOTICE: fpm is running, pid 1370
[17-Nov-2025 07:56:36] NOTICE: ready to handle connections
[17-Nov-2025 07:56:36] NOTICE: systemd monitor interval set to 10000ms
[17-Nov-2025 13:49:19] NOTICE: Terminating …
[17-Nov-2025 13:49:19] NOTICE: exiting, bye-bye!
[17-Nov-2025 13:51:18] NOTICE: fpm is running, pid 1422
[17-Nov-2025 13:51:18] NOTICE: ready to handle connections
[17-Nov-2025 13:51:18] NOTICE: systemd monitor interval set to 10000ms
[17-Nov-2025 14:18:24] NOTICE: Terminating …
[17-Nov-2025 14:18:24] NOTICE: exiting, bye-bye!
[17-Nov-2025 14:20:29] NOTICE: fpm is running, pid 1364
[17-Nov-2025 14:20:29] NOTICE: ready to handle connections
[17-Nov-2025 14:20:29] NOTICE: systemd monitor interval set to 10000ms
[17-Nov-2025 14:21:34] NOTICE: Terminating …
[17-Nov-2025 14:21:34] NOTICE: exiting, bye-bye!
[17-Nov-2025 14:22:03] NOTICE: fpm is running, pid 1330
[17-Nov-2025 14:22:03] NOTICE: ready to handle connections
[17-Nov-2025 14:22:03] NOTICE: systemd monitor interval set to 10000ms
[18-Nov-2025 09:40:47] WARNING: [pool Nextcloud] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 0 idle, and 19 total children
[18-Nov-2025 09:40:48] WARNING: [pool Nextcloud] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 16 children, there are 0 idle, and 21 total children
[18-Nov-2025 09:40:49] WARNING: [pool Nextcloud] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 0 idle, and 23 total children
[18-Nov-2025 10:36:15] NOTICE: Terminating …
[18-Nov-2025 10:36:15] NOTICE: exiting, bye-bye!
[18-Nov-2025 10:36:15] NOTICE: fpm is running, pid 409951
[18-Nov-2025 10:36:15] NOTICE: ready to handle connections
[18-Nov-2025 10:36:15] NOTICE: systemd monitor interval set to 10000ms

We are using PHP 8.4.14 with the following extensions:

Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium, cgi-fcgi, mysqlnd, PDO, xml, apcu, bcmath, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, gmp, iconv, igbinary, imap, intl, ldap, exif, mysqli, pdo_mysql, pdo_pgsql, pgsql, Phar, posix, readline, shmop, SimpleXML, smbclient, soap, sockets, sysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlwriter, xsl, zip, redis, libsmbclient, Zend OPcache

The opcache Settings are as follows:

/etc/php/8.4/cli/conf.d/10-opcache.ini,
opcache.blacklist_filename => no value => no value
opcache.dups_fix => Off => Off
opcache.enable => On => On
opcache.enable_cli => Off => Off
opcache.enable_file_override => Off => Off
opcache.error_log => no value => no value
opcache.file_cache => no value => no value
opcache.file_cache_consistency_checks => On => On
opcache.file_cache_only => Off => Off
opcache.file_update_protection => 2 => 2
opcache.force_restart_timeout => 180 => 180
opcache.huge_code_pages => Off => Off
opcache.interned_strings_buffer => 32 => 32
opcache.jit => no value => no value
opcache.jit_bisect_limit => 0 => 0
opcache.jit_blacklist_root_trace => 16 => 16
opcache.jit_blacklist_side_trace => 8 => 8
opcache.jit_buffer_size => 64M => 64M
opcache.jit_debug => 0 => 0
opcache.jit_hot_func => 127 => 127
opcache.jit_hot_loop => 64 => 64
opcache.jit_hot_return => 8 => 8
opcache.jit_hot_side_exit => 8 => 8
opcache.jit_max_exit_counters => 8192 => 8192
opcache.jit_max_loop_unrolls => 8 => 8
opcache.jit_max_polymorphic_calls => 2 => 2
opcache.jit_max_recursive_calls => 2 => 2
opcache.jit_max_recursive_returns => 2 => 2
opcache.jit_max_root_traces => 1024 => 1024
opcache.jit_max_side_traces => 128 => 128
opcache.jit_max_trace_length => 1024 => 1024
opcache.jit_prof_threshold => 0.005 => 0.005
opcache.lockfile_path => /tmp => /tmp
opcache.log_verbosity_level => 1 => 1
opcache.max_accelerated_files => 10000 => 10000
opcache.max_file_size => 0 => 0
opcache.max_wasted_percentage => 5 => 5
opcache.memory_consumption => 128 => 128
opcache.opt_debug_level => 0 => 0
opcache.optimization_level => 0x7FFEBFFF => 0x7FFEBFFF
opcache.preferred_memory_model => no value => no value
opcache.preload => no value => no value
opcache.preload_user => no value => no value
opcache.protect_memory => Off => Off
opcache.record_warnings => Off => Off
opcache.restrict_api => no value => no value
opcache.revalidate_freq => 2 => 2
opcache.revalidate_path => Off => Off
opcache.save_comments => On => On
opcache.use_cwd => On => On
opcache.validate_permission => Off => Off
opcache.validate_root => Off => Off
opcache.validate_timestamps => On => On

After decluttering the log I have found these entries as soon as the Calender app gives a 404. Still unable to get a possible reason out of the logfile though

Something that may also important to note: today the calender app crashed again. Also today we had a pending update for the contacts apps. After updating the contacts app the calender worked again for a few hours. As if updating an app restarts some part of the app api etc.

Couple thoughts (just brainstorming):

  • Any chance you have some other folders within your apps/ folder named something like calendarNOTINUSE or well, any variations other than just the single calendar/ folder?

  • Does the calendar folder disappear on-disk (or, more specifically, the apps/calendar/appinfo/info.xml file) when you start getting the 404s?

  • I see you’re using Redis for your local memcache too (rather than APCu) and also have dbindex specified in your Redis config. Any chance you’re sharing your Redis cache with another Nextcloud instance accidentally?

After commenting out all lines that start with memcache* in the nextcloud config the Calender doesnt crash anymore. It looks like its an issue with the redis server or the combination of NC version and redis version.

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.