# Nextcloud not running, please help

**URL:** https://community.umbrel.com/t/nextcloud-not-running-please-help/21777
**Category:** Support and Troubleshooting
**Created:** [March 10, 2025, 7:13am UTC](https://community.umbrel.com/t/nextcloud-not-running-please-help/21777 "2025-03-10T07:13:08Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Jejje](https://avatars.discourse-cdn.com/v4/letter/j/c37758/32.png) [@Jejje](https://community.umbrel.com/u/Jejje)
#### Post date: [March 10, 2025, 7:13am UTC](https://community.umbrel.com/t/nextcloud-not-running-please-help/21777/1 "2025-03-10T07:13:08Z")

</div>

What can i do? This happened after upgrading to 1.4

nextcloud\_app\_proxy\_1 | Retrying…  
nextcloud\_db\_1 | 2025-03-09 13:42:36+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.6.21+maria~ubu2004 started.  
nextcloud\_db\_1 | 2025-03-09 13:42:59+00:00 [Note] [Entrypoint]: MariaDB upgrade not required  
nextcloud\_db\_1 | 2025-03-09 13:42:59 0 [Note] Starting MariaDB 10.6.21-MariaDB-ubu2004 source revision 066e8d6aeabc13242193780341e0f845528105de server\_uid VO55khx2FtSu+ib8LdZ5NOwgKz8= as process 1  
nextcloud\_db\_1 | 2025-03-09 13:42:59 0 [Warning] You need to use --log-bin to make --binlog-format work.  
nextcloud\_db\_1 | 2025-03-09 13:43:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.11  
nextcloud\_db\_1 | 2025-03-09 13:43:00 0 [Note] InnoDB: Number of pools: 1  
nextcloud\_db\_1 | 2025-03-09 13:43:00 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions  
nextcloud\_db\_1 | 2025-03-09 13:43:00 0 [Note] mariadbd: O\_TMPFILE is not supported on /tmp (disabling future attempts)  
nextcloud\_db\_1 | 2025-03-09 13:43:00 0 [Note] InnoDB: Using Linux native AIO  
nextcloud\_db\_1 | 2025-03-09 13:43:00 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728  
nextcloud\_db\_1 | 2025-03-09 13:43:00 0 [Note] InnoDB: Completed initialization of buffer pool  
nextcloud\_db\_1 | 2025-03-09 13:43:00 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=133871166,133871166  
nextcloud\_db\_1 | 2025-03-09 13:43:02 0 [Note] InnoDB: 128 rollback segments are active.  
nextcloud\_db\_1 | 2025-03-09 13:43:02 0 [Note] InnoDB: Removed temporary tablespace data file: “./ibtmp1”  
nextcloud\_db\_1 | 2025-03-09 13:43:02 0 [Note] InnoDB: Creating shared tablespace for temporary tables  
nextcloud\_db\_1 | 2025-03-09 13:43:02 0 [Note] InnoDB: Setting file ‘./ibtmp1’ size to 12 MB. Physically writing the file full; Please wait …  
nextcloud\_db\_1 | 2025-03-09 13:43:02 0 [Note] InnoDB: File ‘./ibtmp1’ size is now 12 MB.  
nextcloud\_db\_1 | 2025-03-09 13:43:02 0 [Note] InnoDB: 10.6.21 started; log sequence number 133871178; transaction id 584652  
nextcloud\_db\_1 | 2025-03-09 13:43:02 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib\_buffer\_pool  
nextcloud\_db\_1 | 2025-03-09 13:43:02 0 [Note] Plugin ‘FEEDBACK’ is disabled.  
nextcloud\_db\_1 | 2025-03-09 13:43:04 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.  
nextcloud\_db\_1 | 2025-03-09 13:43:07 0 [Note] Server socket created on IP: ‘0.0.0.0’.  
nextcloud\_db\_1 | 2025-03-09 13:43:07 0 [Note] Server socket created on IP: ‘::’.  
nextcloud\_db\_1 | 2025-03-09 13:43:11 0 [Warning] ‘proxies\_priv’ entry ‘@% root@6309287ce868’ ignored in --skip-name-resolve mode.  
nextcloud\_db\_1 | 2025-03-09 13:43:12 0 [Note] InnoDB: Buffer pool(s) load completed at 250309 13:43:12  
nextcloud\_db\_1 | 2025-03-09 13:43:18 0 [Note] mariadbd: ready for connections.  
nextcloud\_db\_1 | Version: ‘10.6.21-MariaDB-ubu2004’ socket: ‘/run/mysqld/mysqld.sock’ port: 3306 [mariadb.org](http://mariadb.org) binary distribution  
nextcloud\_redis\_1 | 1:C 09 Mar 2025 13:42:33.533 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo  
nextcloud\_redis\_1 | 1:C 09 Mar 2025 13:42:33.533 # Redis version=6.2.2, bits=64, commit=00000000, modified=0, pid=1, just started  
nextcloud\_redis\_1 | 1:C 09 Mar 2025 13:42:33.533 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf  
nextcloud\_redis\_1 | 1:M 09 Mar 2025 13:42:33.534 \* monotonic clock: POSIX clock\_gettime  
nextcloud\_redis\_1 | 1:M 09 Mar 2025 13:42:33.768 \* Running mode=standalone, port=6379.  
nextcloud\_redis\_1 | 1:M 09 Mar 2025 13:42:33.769 # Server initialized  
nextcloud\_redis\_1 | 1:M 09 Mar 2025 13:42:33.769 # WARNING overcommit\_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit\_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit\_memory=1’ for this to take effect.  
nextcloud\_redis\_1 | 1:M 09 Mar 2025 13:42:34.097 \* Loading RDB produced by version 6.2.2  
nextcloud\_redis\_1 | 1:M 09 Mar 2025 13:42:34.097 \* RDB age 10972 seconds  
nextcloud\_redis\_1 | 1:M 09 Mar 2025 13:42:34.097 \* RDB memory usage when created 0.77 Mb  
nextcloud\_redis\_1 | 1:M 09 Mar 2025 13:42:34.097 \* DB loaded from disk: 0.328 seconds  
nextcloud\_redis\_1 | 1:M 09 Mar 2025 13:42:34.097 \* Ready to accept connections  
nextcloud\_app\_proxy\_1 | Error waiting for port: “The address ‘nextcloud\_web\_1’ cannot be found”  
nextcloud\_app\_proxy\_1 | Retrying…  
nextcloud\_app\_proxy\_1 | Error waiting for port: “The address ‘nextcloud\_web\_1’ cannot be found”  
nextcloud\_app\_proxy\_1 | Retrying…  
nextcloud\_app\_proxy\_1 | Error waiting for port: “The address ‘nextcloud\_web\_1’ cannot be found”  
nextcloud\_app\_proxy\_1 | Retrying…  
nextcloud\_app\_proxy\_1 | Error waiting for port: “The address ‘nextcloud\_web\_1’ cannot be found”

this keeps on repeating…

---

<div class="post-metadata">

### Author: ![denny](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/denny/32/6330_2.png) [@denny](https://community.umbrel.com/u/denny)
#### Post date: [March 11, 2025, 10:37pm UTC](https://community.umbrel.com/t/nextcloud-not-running-please-help/21777/2 "2025-03-11T22:37:57Z")

</div>

Try restarting Nextcloud first and see if that helps. If the issue persists, check with `docker ps` whether the nextcloud\_web\_1 container is running. If it’s missing or has crashed, checking the logs with `docker logs nextcloud_web_1 --tail=50` might give more insight.
