<![CDATA[Error in apps accessing NFS volume after upgrade to v9.1.6]]>Hi, our Cloudron instance automatically upgraded from v.9.1.5 to v9.1.6 last night. Today many of our apps are in the Error state, showing the following error message:

BoxError: Storage volume "NetCup RS voln639290a1" is not active. Could not determine mount failure reason.

All these apps have their data storage located on that volume. I have remounted the volume and restarted the server and individual apps multiple times, with no effect.

On logging onto the server I found that nfs-server service was not running (did not exist), and the nfs-kernel-server apt package was not installed. This is strange as the NFS mount has been fine for many months/years, and how would it be running without that service? Had Cloudron uninstalled it? I might be wrong about that, I'm not great with Linux but I installed the nfs-kernel-server:

root@-REDACTED-:~# sudo apt list nfs-*
Listing... Done
nfs-common/jammy-updates,now 1:2.6.1-1ubuntu1.2 amd64 [installed]
nfs-ganesha-ceph/jammy-updates 3.5-1ubuntu1 amd64
nfs-ganesha-doc/jammy-updates 3.5-1ubuntu1 all
nfs-ganesha-gluster/jammy-updates 3.5-1ubuntu1 amd64
nfs-ganesha-gpfs/jammy-updates 3.5-1ubuntu1 amd64
nfs-ganesha-mem/jammy-updates 3.5-1ubuntu1 amd64
nfs-ganesha-mount-9p/jammy-updates 3.5-1ubuntu1 all
nfs-ganesha-nullfs/jammy-updates 3.5-1ubuntu1 amd64
nfs-ganesha-proxy/jammy-updates 3.5-1ubuntu1 amd64
nfs-ganesha-rados-grace/jammy-updates 3.5-1ubuntu1 amd64
nfs-ganesha-rgw/jammy-updates 3.5-1ubuntu1 amd64
nfs-ganesha-vfs/jammy-updates 3.5-1ubuntu1 amd64
nfs-ganesha/jammy-updates 3.5-1ubuntu1 amd64
nfs-kernel-server/jammy-updates,now 1:2.6.1-1ubuntu1.2 amd64 [installed]

The nfs-server service is now running:

root@-REDACTED-:~# sudo systemctl status nfs-server
● nfs-server.service - NFS server and services
     Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled)
     Active: active (exited) since Fri 2026-04-24 12:57:35 UTC; 3h 53min ago
    Process: 887 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
    Process: 888 ExecStart=/usr/sbin/rpc.nfsd (code=exited, status=0/SUCCESS)
   Main PID: 888 (code=exited, status=0/SUCCESS)
        CPU: 11ms

Apr 24 12:57:35 -REDACTED- systemd[1]: Starting NFS server and services...
Apr 24 12:57:35 -REDACTED-systemd[1]: Finished NFS server and services.

But the above issue still remains after rebooting the server.

Here is the output of cloudron-support --troubleshoot:

root@-REDACTED-:~# cloudron-support --troubleshoot
Vendor: netcup Product: KVM Server
Linux: 5.15.0-176-generic
Ubuntu: jammy 22.04
Execution environment: kvm
Processor: AMD EPYC 9634 84-Core Processor x 8
RAM: 16371020KB
Disk: /dev/vda3       130G
[OK]    node version is correct
[OK]    IPv6 is enabled and public IPv6 address is working
[OK]    docker is running
[OK]    docker version is correct
[OK]    MySQL is running
[OK]    netplan is good
[OK]    DNS is resolving via systemd-resolved
[OK]    unbound is running
[OK]    nginx is running
[OK]    dashboard cert is valid
[OK]    dashboard is reachable via loopback
[OK]    No pending database migrations
[OK]    Service 'mysql' is running and healthy
[OK]    Service 'postgresql' is running and healthy
[OK]    Service 'mongodb' is running and healthy
[FAIL]  Service 'mail' container is not running (state: created)!
[OK]    Service 'graphite' is running and healthy
[OK]    Service 'sftp' is running and healthy
[OK]    box v9.1.6 is running
[OK]    Dashboard is reachable via domain name
        Domain stirchley.coop expiry check skipped because whois is not installed. Run 'apt install whois' to check

I'm seeing these errors in /home/yellowtent/platformdata/logs/box.log:

2026-04-23T21:03:00.049Z shell: mounts: mountpoint -q -- /mnt/volumes/00fd99454f384c91a83326ad3097bb1e errored BoxError: mountpoint exited with code 32 signal null
    at ChildProcess.<anonymous> (file:///home/yellowtent/box/src/shell.js:70:23)
    at ChildProcess.emit (node:events:508:28)
    at maybeClose (node:internal/child_process:1101:16)
    at Socket.<anonymous> (node:internal/child_process:457:11)
    at Socket.emit (node:events:508:28)
    at Pipe.<anonymous> (node:net:346:12) {
  reason: 'Shell Error',
  details: {},
  stdout: '',
  stdoutString: '',
  stdoutLineCount: 0,
  stderr: '',
  stderrString: '',
  stderrLineCount: 0,
  code: 32,
  signal: null,
  timedOut: false,
  terminated: false
}
2026-04-23T21:03:00.050Z shell: mounts: systemd-escape -p --suffix=mount /mnt/volumes/00fd99454f384c91a83326ad3097bb1e
2026-04-23T21:03:00.062Z shell: mounts: journalctl -u mnt-volumes-00fd99454f384c91a83326ad3097bb1e.mount\n -n 10 --no-pager -o json
2026-04-23T21:03:00.074Z apphealthmonitor: app health: 6 running / 5 stopped / 7 unresponsive
2026-04-23T21:03:00.084Z scheduler: BoxError: Storage volume "NetCup RS voln639290a1" is not active. Could not determine mount failure reason.
    at getAddonMounts (file:///home/yellowtent/box/src/docker.js:247:54)
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
    at async getMounts (file:///home/yellowtent/box/src/docker.js:297:25)
    at async Object.createSubcontainer (file:///home/yellowtent/box/src/docker.js:649:20) {
  reason: 'Bad State',
  details: {}
}
...
2026-04-24T12:31:28.345Z shell: mounts: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/remountmount.sh /mnt/volumes/00fd99454f384c91a83326ad3097bb1e
2026-04-24T12:31:28.397Z shell: mounts: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/remountmount.sh /mnt/volumes/00fd99454f384c91a83326ad3097bb1e errored BoxError: /usr/bin/sudo exited with code 1 signal null
    at ChildProcess.<anonymous> (file:///home/yellowtent/box/src/shell.js:70:23)
    at ChildProcess.emit (node:events:508:28)
    at maybeClose (node:internal/child_process:1101:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5) {
  reason: 'Shell Error',
  details: {},
  stdout: '',
  stdoutString: '',
  stdoutLineCount: 0,
  stderr: 'Job failed. See "journalctl -xe" for details.\n',
  stderrString: 'Job failed. See "journalctl -xe" for details.\n',
  stderrLineCount: 1,
  code: 1,
  signal: null,
  timedOut: false,
  terminated: false
}
2026-04-24T12:31:28.454Z shell: mounts: mountpoint -q -- /mnt/volumes/00fd99454f384c91a83326ad3097bb1e
...
2026-04-24T12:58:00.215Z scheduler: BoxError: (HTTP code 400) bad parameter - No such container: null
    at Object.createSubcontainer (file:///home/yellowtent/box/src/docker.js:770:28)
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5) {
  reason: 'Docker Error',
  details: {},
  nestedError: Error: (HTTP code 400) bad parameter - No such container: null
      at /home/yellowtent/box/node_modules/docker-modem/lib/modem.js:383:17
      at getCause (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:418:7)
      at Modem.buildPayload (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:379:5)
      at IncomingMessage.<anonymous> (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:347:16)
      at IncomingMessage.emit (node:events:520:35)
      at endReadableNT (node:internal/streams/readable:1701:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:89:21) {
    reason: 'bad parameter',
    statusCode: 400,
    json: { message: 'No such container: null' }
  }
}

This was the output for journalctl -xe when remounting the volume:

Apr 24 16:35:55 -REDACTED-systemd[1]: var-lib-docker-overlay2-2e77e0df312b7a38d974f58ce03709aeb8f5b83a3a95b6560a74c107d7e68417-merged.mount: Deactivated success>
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit var-lib-docker-overlay2-2e77e0df312b7a38d974f58ce03709aeb8f5b83a3a95b6560a74c107d7e68417-merged.mount has successfully entered the 'dead' state.
Apr 24 16:36:01 -REDACTED-kernel: Packet dropped: IN=eth0 OUT= MAC=6a:80:31:09:cf:8d:84:03:28:62:58:1a:08:00 SRC=185.242.226.71 DST=152.53.33.202 LEN=40 TOS=0x0>
Apr 24 16:36:22 -REDACTED-sshd[29055]: Connection closed by authenticating user -REDACTED- 77.90.185.40 port 46604 [preauth]
Apr 24 16:36:25 -REDACTED-kernel: Packet dropped: IN=eth0 OUT= MAC=6a:80:31:09:cf:8d:84:03:28:62:58:1a:08:00 SRC=51.148.95.245 DST=152.53.33.202 LEN=60 TOS=0x00>
Apr 24 16:36:57 -REDACTED-kernel: Packet dropped: IN=eth0 OUT= MAC=6a:80:31:09:cf:8d:84:03:28:62:58:1a:08:00 SRC=51.148.95.245 DST=152.53.33.202 LEN=60 TOS=0x00>
Apr 24 16:37:04 -REDACTED-sudo[29078]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=998)
Apr 24 16:37:04 -REDACTED-systemd[1]: Unmounting NetCup RS voln639290a1...
░░ Subject: A stop job for unit mnt-volumes-00fd99454f384c91a83326ad3097bb1e.mount has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit mnt-volumes-00fd99454f384c91a83326ad3097bb1e.mount has begun execution.
░░
░░ The job identifier is 1013.
Apr 24 16:37:04 -REDACTED-systemd[1]: mnt-volumes-00fd99454f384c91a83326ad3097bb1e.mount: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit mnt-volumes-00fd99454f384c91a83326ad3097bb1e.mount has successfully entered the 'dead' state.
Apr 24 16:37:04 -REDACTED-systemd[1]: Unmounted NetCup RS voln639290a1.
░░ Subject: A stop job for unit mnt-volumes-00fd99454f384c91a83326ad3097bb1e.mount has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A stop job for unit mnt-volumes-00fd99454f384c91a83326ad3097bb1e.mount has finished.
░░
░░ The job identifier is 1013 and the job result is done.
Apr 24 16:37:04 -REDACTED-systemd[1]: mnt-volumes-00fd99454f384c91a83326ad3097bb1e.mount: Directory /mnt/volumes/00fd99454f384c91a83326ad3097bb1e to mount over >
░░ Subject: Mount point is not empty
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The directory /mnt/volumes/00fd99454f384c91a83326ad3097bb1e is specified as the mount point (second field in
░░ /etc/fstab or Where= field in systemd unit file) and is not empty.
░░ This does not interfere with mounting, but the pre-exisiting files in
░░ this directory become inaccessible. To see those over-mounted files,
░░ please manually mount the underlying file system to a secondary
░░ location.
Apr 24 16:37:04 -REDACTED-systemd[1]: Mounting NetCup RS voln639290a1...
░░ Subject: A start job for unit mnt-volumes-00fd99454f384c91a83326ad3097bb1e.mount has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit mnt-volumes-00fd99454f384c91a83326ad3097bb1e.mount has begun execution.
░░
░░ The job identifier is 1014.
Apr 24 16:37:04 -REDACTED-systemd[1]: Mounted NetCup RS voln639290a1.
░░ Subject: A start job for unit mnt-volumes-00fd99454f384c91a83326ad3097bb1e.mount has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit mnt-volumes-00fd99454f384c91a83326ad3097bb1e.mount has finished successfully.
░░
░░ The job identifier is 1014.
Apr 24 16:37:04 -REDACTED-sudo[29078]: pam_unix(sudo:session): session closed for user root
Apr 24 16:37:23 -REDACTED-kernel: Packet dropped: IN=eth0 OUT= MAC=6a:80:31:09:cf:8d:84:03:28:62:58:1a:08:00 SRC=88.210.63.192 DST=152.53.33.202 LEN=40 TOS=0x00>

Here are the logs from one of the erroring apps:

Apr 24 13:57:12 13:M 24 Apr 2026 12:57:12.786 # Redis is now ready to exit, bye bye...
Apr 24 13:57:12 13:M 24 Apr 2026 12:57:12.786 * DB saved on disk
Apr 24 13:57:12 13:M 24 Apr 2026 12:57:12.786 * Removing the pid file.
Apr 24 13:57:12 13:signal-handler (1777035432) Received SIGTERM scheduling shutdown...
Apr 24 13:57:12 2026-04-24 12:57:12,759 INFO waiting for redis, redis-service to die
Apr 24 13:57:12 2026-04-24 12:57:12,759 WARN received SIGTERM indicating exit request
Apr 24 13:57:12 2026-04-24 12:57:12,762 WARN stopped: redis-service (terminated by SIGTERM)
Apr 24 13:57:12 2026-04-24 12:57:12,788 INFO stopped: redis (exit status 0)
Apr 24 13:57:37 2026-04-24 12:57:37,995 INFO Included extra file "/etc/supervisor/conf.d/redis-service.conf" during parsing
Apr 24 13:57:37 2026-04-24 12:57:37,996 INFO Included extra file "/etc/supervisor/conf.d/redis.conf" during parsing
Apr 24 13:57:37 2026-04-24 12:57:37,996 INFO Set uid to user 0 succeeded
Apr 24 13:57:37 ==> Starting supervisor
Apr 24 13:57:38 2026-04-24 12:57:38,002 CRIT Server 'inet_http_server' running without any HTTP authentication checking
Apr 24 13:57:38 2026-04-24 12:57:38,002 INFO RPC interface 'supervisor' initialized
Apr 24 13:57:38 2026-04-24 12:57:38,002 INFO supervisord started with pid 1
Apr 24 13:57:39 13:C 24 Apr 2026 12:57:39.029 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
Apr 24 13:57:39 13:C 24 Apr 2026 12:57:39.029 * Configuration loaded
Apr 24 13:57:39 13:C 24 Apr 2026 12:57:39.029 * Redis version=8.4.0, bits=64, commit=00000000, modified=1, pid=13, just started
Apr 24 13:57:39 13:C 24 Apr 2026 12:57:39.029 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Apr 24 13:57:39 13:M 24 Apr 2026 12:57:39.030 * Increased maximum number of open files to 10032 (it was originally set to 1024).
Apr 24 13:57:39 13:M 24 Apr 2026 12:57:39.030 * monotonic clock: POSIX clock_gettime
Apr 24 13:57:39 13:M 24 Apr 2026 12:57:39.032 # Failed to write PID file: Permission denied
Apr 24 13:57:39 13:M 24 Apr 2026 12:57:39.032 * Running mode=standalone, port=6379.
Apr 24 13:57:39 13:M 24 Apr 2026 12:57:39.033 * Server initialized
Apr 24 13:57:39 13:M 24 Apr 2026 12:57:39.036 * Loading RDB produced by version 8.4.0
Apr 24 13:57:39 13:M 24 Apr 2026 12:57:39.036 * RDB age 27 seconds
Apr 24 13:57:39 13:M 24 Apr 2026 12:57:39.036 * RDB memory usage when created 4.76 Mb
Apr 24 13:57:39 13:M 24 Apr 2026 12:57:39.086 * Done loading RDB, keys loaded: 175, keys expired: 0.
Apr 24 13:57:39 13:M 24 Apr 2026 12:57:39.087 * DB loaded from disk: 0.053 seconds
Apr 24 13:57:39 13:M 24 Apr 2026 12:57:39.087 * Ready to accept connections tcp
Apr 24 13:57:39 2026-04-24 12:57:39,004 INFO spawned: 'redis' with pid 13
Apr 24 13:57:39 2026-04-24 12:57:39,006 INFO spawned: 'redis-service' with pid 14
Apr 24 13:57:39 Redis service endpoint listening on http://:::3000
Apr 24 13:57:40 2026-04-24 12:57:40,639 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Apr 24 13:57:40 2026-04-24 12:57:40,639 INFO success: redis-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Apr 24 14:01:38 [GET] /healthcheck
Apr 24 14:01:38 BoxError: Storage volume "NetCup RS voln639290a1" is not active. Could not determine mount failure reason.
Apr 24 14:01:38 }
Apr 24 14:01:38 }

The volume in the Cloudron /volumes view looks like it has mounted successfully. It has a green circle next to it.
3753f033-9cfd-4750-b181-30190e429bd0-image.jpeg

Clicking on File manager allows me to browse the files within it:
b340954d-4126-4734-b728-c481c322859a-image.jpeg

I'm out of ideas, and searching online isn't turning up anything helpful I can see. Is it possible the update has done something to our NFS settings or has there been a bug introduced where apps with their data hosted on an NFS volume don't work? This issue has come at a critical time for our organisation so would really appreciate any help you can give!

Thanks,
Stu

]]>https://forum.cloudron.io/topic/15439/error-in-apps-accessing-nfs-volume-after-upgrade-to-v9.1.6RSS for NodeFri, 24 Apr 2026 21:49:02 GMTFri, 24 Apr 2026 16:56:59 GMT60<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 18:52:10 GMT]]>Hello @stirchley.coop
I also had a look and redacted some content.
Also, the content that was not redacted are not critical since Cloudron ensures that non of the Cloudron services are accessible from the internet.

But if you still feel more comfortable to delete the whole topic, I can do that.

]]>https://forum.cloudron.io/post/124002https://forum.cloudron.io/post/124002Fri, 24 Apr 2026 18:52:10 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 18:41:11 GMT]]>@james there's usernames and passwords in there, I'm going through and redacting them but I'd rather delete the thread completely if possible in case I've missed something

]]>https://forum.cloudron.io/post/124001https://forum.cloudron.io/post/124001Fri, 24 Apr 2026 18:41:11 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 18:39:51 GMT]]>Hello @stirchley.coop
Since this topic could be of value to other people, I would like to keep the topic.
You can edit your posts to redact any details, mainly the domain name I see, but I personally would not consider that sensitive.

]]>https://forum.cloudron.io/post/124000https://forum.cloudron.io/post/124000Fri, 24 Apr 2026 18:39:51 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 18:38:14 GMT]]>@james can we delete this thread? Realising there's sensitive info in all the log messages

]]>https://forum.cloudron.io/post/123999https://forum.cloudron.io/post/123999Fri, 24 Apr 2026 18:38:14 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 18:34:16 GMT]]>Hello @stirchley.coop
Great I could help and everything is resolving back to normal.
When everything is resolved, please leave a comment so I can mark this topic as solved.

]]>https://forum.cloudron.io/post/123998https://forum.cloudron.io/post/123998Fri, 24 Apr 2026 18:34:16 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 18:33:08 GMT]]>The wordpress site above eventually started responding:

Apr 24 19:28:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:28:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:28:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:29:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:29:08 => Updating db settings
Apr 24 19:29:08 Success: Updated the constant 'DB_HOST' in the 'wp-config.php' file with the value 'mysql:3306'.
Apr 24 19:29:08 Success: Updated the constant 'DB_NAME' in the 'wp-config.php' file with the value 'xxx'.
Apr 24 19:29:09 Success: Updated the constant 'DB_USER' in the 'wp-config.php' file with the value 'xxx'.
Apr 24 19:29:09 Success: Updated the constant 'DB_PASSWORD' in the 'wp-config.php' file with the value 'xxx'.
Apr 24 19:29:09 ==> Updating wordpress database
Apr 24 19:29:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:29:10 Success: WordPress database already at latest db version 60717.
Apr 24 19:29:10 ==> Updating domain related settings
Apr 24 19:29:10 Success: Updated the constant 'WP_HOME' in the 'wp-config.php' file with the value 'https://www.stirchley.coop'.
Apr 24 19:29:11 Success: Updated the constant 'WP_SITEURL' in the 'wp-config.php' file with the value 'https://www.stirchley.coop'.
Apr 24 19:29:11 Success: Updated the constant 'WP_CONTENT_DIR' in the 'wp-config.php' file with the value '/app/data/wp-content'.
Apr 24 19:29:12 Success: Value passed for 'siteurl' option is unchanged.
Apr 24 19:29:12 Success: Value passed for 'home' option is unchanged.
Apr 24 19:29:12 ==> Configuring smtp mail
Apr 24 19:29:14 Success: Value passed for 'smtp_mailer_options' option is unchanged.
Apr 24 19:29:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:29:20 Unpacking the package...
Apr 24 19:29:20 Installing the plugin...
Apr 24 19:29:20 Removing the old version of the plugin...
Apr 24 19:29:20 Plugin updated successfully.
Apr 24 19:29:23 Success: Installed 1 of 1 plugins.
Apr 24 19:29:24 Warning: Plugin 'cloudron-sso' is already active.
Apr 24 19:29:24 Success: Plugin already activated.
Apr 24 19:29:25 ==> Configuring OIDC
Apr 24 19:29:25 Success: Value passed for 'openid_connect_generic_settings' option is unchanged.
Apr 24 19:29:25 ==> Starting apache
Apr 24 19:29:26 [Fri Apr 24 18:29:26.197242 2026] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.58 (Ubuntu) mod_perl/2.0.13 Perl/v5.38.2 configured -- resuming normal operations
Apr 24 19:29:26 [Fri Apr 24 18:29:26.197291 2026] [core:notice] [pid 1] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND'
Apr 24 19:29:30 - - - [24/Apr/2026:18:29:30 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"
Apr 24 19:29:40 - - - [24/Apr/2026:18:29:40 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"
Apr 24 19:29:50 - - - [24/Apr/2026:18:29:50 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"
Apr 24 19:29:57 104.23.208.140 - - [24/Apr/2026:18:29:32 +0000] "GET /wp-login.php HTTP/1.1" 200 2980 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36"
Apr 24 19:29:58 172.68.229.208 - - [24/Apr/2026:18:29:46 +0000] "GET / HTTP/1.1" 200 14761 "-" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:29:58 172.69.224.18 - - [24/Apr/2026:18:29:58 +0000] "GET /wp-content/themes/twentytwenty-child/style.css?ver=1.0.1 HTTP/1.1" 200 582 "https://www.stirchley.coop/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:29:58 162.158.216.166 - - [24/Apr/2026:18:29:58 +0000] "GET /wp-content/themes/twentytwenty/style.css?ver=3.0 HTTP/1.1" 200 23204 "https://www.stirchley.coop/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:29:58 141.101.98.55 - - [24/Apr/2026:18:29:58 +0000] "GET /wp-content/themes/twentytwenty/assets/css/font-inter.css?ver=1.0.1 HTTP/1.1" 200 268 "https://www.stirchley.coop/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:29:58 172.69.224.29 - - [24/Apr/2026:18:29:58 +0000] "GET /wp-content/uploads/2026/03/cropped-SCD-logo-1.png HTTP/1.1" 304 - "https://www.stirchley.coop/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:29:58 172.71.178.90 - - [24/Apr/2026:18:29:58 +0000] "GET /wp-content/uploads/2023/06/16-06-23_-_GSA_Stirchley-43-1200x801.jpg HTTP/1.1" 304 - "https://www.stirchley.coop/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:29:58 162.158.216.38 - - [24/Apr/2026:18:29:58 +0000] "GET /wp-content/uploads/2025/12/DSC08223-1200x800.jpg HTTP/1.1" 304 - "https://www.stirchley.coop/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:29:58 172.71.241.139 - - [24/Apr/2026:18:29:58 +0000] "GET /wp-content/themes/twentytwenty/assets/js/index.js?ver=1.0.1 HTTP/1.1" 200 7401 "https://www.stirchley.coop/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:29:58 162.158.216.213 - - [24/Apr/2026:18:29:58 +0000] "GET /wp-content/uploads/2024/05/29-04-2024_GSA_Stirchley-81-1-1200x801.jpg HTTP/1.1" 200 271929 "https://www.stirchley.coop/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:29:58 172.71.178.15 - - [24/Apr/2026:18:29:58 +0000] "GET /wp-content/themes/twentytwenty/print.css?ver=1.0.1 HTTP/1.1" 200 1006 "https://www.stirchley.coop/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:29:58 162.158.216.140 - - [24/Apr/2026:18:29:58 +0000] "GET /wp-content/themes/twentytwenty/assets/fonts/inter/Inter-upright-var.woff2 HTTP/1.1" 304 - "https://www.stirchley.coop/wp-content/themes/twentytwenty/assets/css/font-inter.css?ver=1.0.1" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:29:58 162.158.216.209 - - [24/Apr/2026:18:29:53 +0000] "GET / HTTP/1.1" 200 14761 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:149.0) Gecko/20100101 Firefox/149.0"
Apr 24 19:29:58 172.69.43.177 - - [24/Apr/2026:18:29:58 +0000] "GET /wp-content/uploads/2026/03/cropped-cropped-SCD-logo-1-180x180.png HTTP/1.1" 304 - "-" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:29:59 172.71.178.109 - - [24/Apr/2026:18:29:59 +0000] "GET /wp-includes/js/wp-emoji-release.min.js?ver=6.9.4 HTTP/1.1" 200 5375 "https://www.stirchley.coop/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:29:59 172.71.178.89 - - [24/Apr/2026:18:29:59 +0000] "GET /wp-content/uploads/2023/06/16-06-23_-_GSA_Stirchley-43-1980x1322.jpg HTTP/1.1" 304 - "https://www.stirchley.coop/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:149.0) Gecko/20100101 Firefox/149.0"
Apr 24 19:29:59 172.69.194.198 - - [24/Apr/2026:18:29:59 +0000] "GET /wp-content/uploads/2025/12/DSC08223-1536x1024.jpg HTTP/1.1" 304 - "https://www.stirchley.coop/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:149.0) Gecko/20100101 Firefox/149.0"
Apr 24 19:29:59 141.101.98.52 - - [24/Apr/2026:18:29:59 +0000] "GET /wp-content/uploads/2024/05/29-04-2024_GSA_Stirchley-81-1-1536x1025.jpg HTTP/1.1" 304 - "https://www.stirchley.coop/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:149.0) Gecko/20100101 Firefox/149.0"
Apr 24 19:30:00 - - - [24/Apr/2026:18:30:00 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"
Apr 24 19:30:00 172.69.43.165 - - [24/Apr/2026:18:30:00 +0000] "GET /wp-content/uploads/2026/03/cropped-cropped-SCD-logo-1-192x192.png HTTP/1.1" 304 - "https://www.stirchley.coop/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:149.0) Gecko/20100101 Firefox/149.0"
Apr 24 19:30:00 172.71.178.104 - - [24/Apr/2026:18:30:00 +0000] "GET /wp-content/uploads/2026/03/cropped-cropped-SCD-logo-1-32x32.png HTTP/1.1" 304 - "https://www.stirchley.coop/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:149.0) Gecko/20100101 Firefox/149.0"
Apr 24 19:30:00 172.68.186.17 - - [24/Apr/2026:18:30:00 +0000] "GET /wp-content/uploads/2024/05/29-04-2024_GSA_Stirchley-89-1024x683.jpg HTTP/1.1" 304 - "https://www.stirchley.coop/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:30:03 172.71.178.31 - - [24/Apr/2026:18:30:03 +0000] "GET /wp-content/uploads/2020/05/powertochange-e1642966595878.png HTTP/1.1" 200 89055 "https://www.stirchley.coop/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:30:03 172.71.178.6 - - [24/Apr/2026:18:30:03 +0000] "GET /wp-content/uploads/2023/05/CHARM-logo-1024x426.png HTTP/1.1" 304 - "https://www.stirchley.coop/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:30:10 - - - [24/Apr/2026:18:30:10 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"
Apr 24 19:30:14 104.23.248.105 - - [24/Apr/2026:18:30:08 +0000] "POST /xmlrpc.php HTTP/1.1" 200 225 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; BOIE9;ENCA; rv:11.0) like Gecko"
Apr 24 19:30:20 - - - [24/Apr/2026:18:30:20 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"
Apr 24 19:30:22 172.70.86.175 - - [24/Apr/2026:18:30:15 +0000] "GET /blog/ HTTP/1.1" 200 31864 "https://www.stirchley.coop/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:30:22 172.71.178.109 - - [24/Apr/2026:18:30:22 +0000] "GET /wp-content/uploads/2025/12/signal-2025-12-22-171922_002-1200x900.jpeg HTTP/1.1" 304 - "https://www.stirchley.coop/blog/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:30:22 172.69.194.85 - - [24/Apr/2026:18:30:22 +0000] "GET /wp-content/uploads/2026/03/2505_stirchley-website-image-DRAFT-colour-2.pdf-1200x910.jpg HTTP/1.1" 304 - "https://www.stirchley.coop/blog/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:30:22 172.69.194.46 - - [24/Apr/2026:18:30:22 +0000] "GET /wp-content/uploads/2025/12/AA-43-1200x800.jpg HTTP/1.1" 304 - "https://www.stirchley.coop/blog/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:30:22 172.70.162.13 - - [24/Apr/2026:18:30:22 +0000] "GET /wp-content/themes/twentytwenty/assets/fonts/inter/Inter-italic-var.woff2 HTTP/1.1" 304 - "https://www.stirchley.coop/wp-content/themes/twentytwenty/assets/css/font-inter.css?ver=1.0.1" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:30:22 172.69.195.246 - - [24/Apr/2026:18:30:22 +0000] "GET /wp-content/uploads/2023/05/CHARM-logo-1200x499.png HTTP/1.1" 304 - "https://www.stirchley.coop/blog/" "Mozilla/5.0 (Android 16; Mobile; rv:150.0) Gecko/150.0 Firefox/150.0"
Apr 24 19:30:30 - - - [24/Apr/2026:18:30:30 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"
Apr 24 19:30:30 162.158.162.68 - - [24/Apr/2026:18:30:24 +0000] "GET /robots.txt HTTP/1.1" 200 113 "-" "Mozilla/5.0 (compatible;PetalBot;+https://webmaster.petalsearch.com/site/petalbot)"
Apr 24 19:30:33 => Run cron job
Apr 24 19:30:40 - - - [24/Apr/2026:18:30:40 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"
Apr 24 19:30:42 Executed the cron event 'wp_privacy_delete_old_export_files' in 0.041s.
Apr 24 19:30:45 172.68.229.208 - - [24/Apr/2026:18:30:39 +0000] "GET / HTTP/1.1" 200 14761 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:149.0) Gecko/20100101 Firefox/149.0"
Apr 24 19:30:45 141.101.98.120 - - [24/Apr/2026:18:30:45 +0000] "GET /wp-content/uploads/2024/05/29-04-2024_GSA_Stirchley-81-1-1024x683.jpg HTTP/1.1" 304 - "https://www.stirchley.coop/" "Mozilla/5.0 (X11; Linux x86_64; rv:149.0) Gecko/20100101 Firefox/149.0"
Apr 24 19:30:45 172.70.162.207 - - [24/Apr/2026:18:30:45 +0000] "GET /wp-content/uploads/2025/12/DSC08223-1024x683.jpg HTTP/1.1" 304 - "https://www.stirchley.coop/" "Mozilla/5.0 (X11; Linux x86_64; rv:149.0) Gecko/20100101 Firefox/149.0"
Apr 24 19:30:50 - - - [24/Apr/2026:18:30:50 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"
Apr 24 19:30:51 Executed the cron event 'wp_cache_gc' in 8.484s.
Apr 24 19:30:51 Executed the cron event 'jetpack_clean_nonces' in 0.003s.
Apr 24 19:30:51 Executed the cron event 'wc_admin_process_orders_milestone' in 0.002s.
Apr 24 19:31:00 - - - [24/Apr/2026:18:31:00 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"
Apr 24 19:31:10 - - - [24/Apr/2026:18:31:10 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"
Apr 24 19:31:13 Executed the cron event 'wp_version_check' in 21.979s.
Apr 24 19:31:13 Executed the cron event 'wp_update_plugins' in 0.066s.
Apr 24 19:31:13 Executed the cron event 'wp_update_themes' in 0.013s.
Apr 24 19:31:13 Executed the cron event 'recovery_mode_clean_expired_keys' in 0.004s.
Apr 24 19:31:13 Executed the cron event 'wp_scheduled_delete' in 0.005s.
Apr 24 19:31:13 Executed the cron event 'delete_expired_transients' in 0.046s.
Apr 24 19:31:13 Executed the cron event 'wp_scheduled_auto_draft_delete' in 0.002s.
Apr 24 19:31:13 Executed the cron event 'simple_history/maybe_purge_db' in 0.003s.
Apr 24 19:31:13 Executed the cron event 'wp_update_user_counts' in 0.009s.
Apr 24 19:31:13 Executed the cron event 'woocommerce_marketplace_cron_fetch_promotions' in 0.007s.
Apr 24 19:31:15 Executed the cron event 'wp_cache_full_preload_hook' in 1.923s.
Apr 24 19:31:16 Executed the cron event 'simple_history/core_files_integrity_check' in 1.323s.
Apr 24 19:31:17 Executed the cron event 'mc4wp_refresh_mailchimp_lists' in 0.387s.
Apr 24 19:31:17 Executed the cron event 'openid-connect-generic-cron-daily' in 0.005s.
Apr 24 19:31:17 Executed the cron event 'jetpack_v2_heartbeat' in 0.005s.
Apr 24 19:31:17 Executed the cron event 'wp_delete_temp_updater_backups' in 0.004s.
Apr 24 19:31:17 Success: Executed a total of 20 cron events.
Apr 24 19:31:20 - - - [24/Apr/2026:18:31:20 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"
Apr 24 19:31:30 - - - [24/Apr/2026:18:31:30 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"
Apr 24 19:31:40 - - - [24/Apr/2026:18:31:40 +0000] "GET /wp-includes/version.php HTTP/1.1" 200 - "-" "Mozilla (CloudronHealth)"
]]>https://forum.cloudron.io/post/123997https://forum.cloudron.io/post/123997Fri, 24 Apr 2026 18:33:08 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 18:31:11 GMT]]>Yes the mount is active and working. The remaining apps are slowly coming back online with all their data

]]>https://forum.cloudron.io/post/123996https://forum.cloudron.io/post/123996Fri, 24 Apr 2026 18:31:11 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 18:30:06 GMT]]>Hello @stirchley.coop

@Stirchley.coop said:

Apr 24 19:17:50 BoxError: Storage volume "NetCup RS voln639290a1" is not active. Could not determine mount failure reason.

Can you validate if the mount is actually active and working?
You can use the mount -l command to show you all mounts on your system.

There is also this log entry:

Apr 24 19:17:06 shell: mounts: mountpoint -q -- /mnt/volumes/00fd99454f384c91a83326ad3097bb1e

Do these mounts exist and are accessible?

]]>https://forum.cloudron.io/post/123995https://forum.cloudron.io/post/123995Fri, 24 Apr 2026 18:30:06 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 18:37:52 GMT]]>@james the other apps seem to be stuck in an error state:

Apr 24 19:17:05 taskworker: Starting task 14154. Logs are at /home/yellowtent/platformdata/logs/74f9b0b7-8fb9-4805-9057-5d3bcf33d36b/apptask.log
Apr 24 19:17:05 taskworker: Running task of type app
Apr 24 19:17:05 apptask: run: startTask installationState: pending_configure runState: running
Apr 24 19:17:05 tasks: updating task 14154 with: {"percent":10,"message":"Deleting old containers"}
Apr 24 19:17:05 shell: reverseproxy: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/restartservice.sh nginx
Apr 24 19:17:05 apptask: deleteContainer: deleting app containers (app, scheduler)
Apr 24 19:17:05 shell: apptask: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/configurelogrotate.sh remove 74f9b0b7-8fb9-4805-9057-5d3bcf33d36b
Apr 24 19:17:05 tasks: updating task 14154 with: {"percent":20,"message":"Downloading icon"}
Apr 24 19:17:05 apptask: downloadIcon: Downloading icon of org.wordpress.cloudronapp@3.16.3
Apr 24 19:17:06 tasks: updating task 14154 with: {"percent":40,"message":"Downloading image"}
Apr 24 19:17:06 shell: df: df -B1 --output=source,fstype,size,used,avail,pcent,target /var/lib/docker
Apr 24 19:17:06 docker: downloadImage: cloudron/org.wordpress.cloudronapp:202603120114210000
Apr 24 19:17:06 tasks: updating task 14154 with: {"percent":50,"message":"Ensuring app data directory"}
Apr 24 19:17:06 tasks: updating task 14154 with: {"percent":55,"message":"Setting up addons"}
Apr 24 19:17:06 services: Setting up mysql
Apr 24 19:17:06 services: setupAddons: Setting up ["mysql","localstorage","sendmail","oidc","scheduler"]
Apr 24 19:17:06 services: setupAddons: setting up addon mysql with options {}
Apr 24 19:17:06 services: Setting mysql addon config to [{"name":"CLOUDRON_MYSQL_USERNAME","value":"xxx"},{"name":"CLOUDRON_MYSQL_PASSWORD","value":"xxx"},{"name":"CLOUDRON_MYSQL_HOST","value":"mysql"},{"name":"CLOUDRON_MYSQL_PORT","value":"3306"},{"name":"CLOUDRON_MYSQL_URL","value":"xxx"},{"name":"CLOUDRON_MYSQL_DATABASE","value":"xxx"}]
Apr 24 19:17:06 services: setupAddons: setting up addon localstorage with options {"ftp":{"uid":33,"uname":"www-data"}}
Apr 24 19:17:06 services: setupLocalStorage
Apr 24 19:17:06 shell: services: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/setupvolume.sh /mnt/volumes/00fd99454f384c91a83326ad3097bb1e/www
Apr 24 19:17:06 services: setupAddons: setting up addon sendmail with options {"optional":true,"supportsDisplayName":true}
Apr 24 19:17:06 services: Setting sendmail addon config to [{"name":"CLOUDRON_MAIL_SMTP_SERVER","value":"mail"},{"name":"CLOUDRON_MAIL_SMTP_PORT","value":"2525"},{"name":"CLOUDRON_MAIL_SMTPS_PORT","value":"2465"},{"name":"CLOUDRON_MAIL_STARTTLS_PORT","value":"2587"},{"name":"CLOUDRON_MAIL_SMTP_USERNAME","value":"xxx"},{"name":"CLOUDRON_MAIL_SMTP_PASSWORD","value":"xxx"},{"name":"CLOUDRON_MAIL_FROM","value":"xxx"},{"name":"CLOUDRON_MAIL_DOMAIN","value":"stirchley.coop"},{"name":"CLOUDRON_MAIL_FROM_DISPLAY_NAME","value":""}]
Apr 24 19:17:06 services: Setting up SendMail
Apr 24 19:17:06 services: setupAddons: setting up addon oidc with options {"loginRedirectUri":"/wp-admin/admin-ajax.php?action=openid-connect-authorize"}
Apr 24 19:17:06 services: Setting up OIDC
Apr 24 19:17:06 services: setupAddons: setting up addon scheduler with options {"wpcron":{"schedule":"*/5 * * * *","command":"/app/pkg/cron.sh"}}
Apr 24 19:17:06 tasks: updating task 14154 with: {"percent":60,"message":"Creating container"}
Apr 24 19:17:06 apptask: createContainer: creating container
Apr 24 19:17:06 shell: mounts: mountpoint -q -- /mnt/volumes/00fd99454f384c91a83326ad3097bb1e
Apr 24 19:17:06 shell: apptask: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/configurelogrotate.sh add 74f9b0b7-8fb9-4805-9057-5d3bcf33d36b /tmp/74f9b0b7-8fb9-4805-9057-5d3bcf33d36b.logrotate
Apr 24 19:17:06 apptask: startApp: starting container
Apr 24 19:17:06 tasks: updating task 14154 with: {"percent":90,"message":"Configuring reverse proxy"}
Apr 24 19:17:06 shell: openssl: openssl x509 -noout -subject -issuer
Apr 24 19:17:06 reverseproxy: providerMatches: subject=CN = *.stirchley.coop domain=*.stirchley.coop issuer=C = US, O = Let's Encrypt, CN = E7 wildcard=true/true prod=true/true issuerMismatch=false wildcardMismatch=false match=true
Apr 24 19:17:06 shell: openssl: openssl x509 -startdate -enddate -subject -noout
Apr 24 19:17:06 openssl: expiryDate: subject=CN = *.stirchley.coop notBefore=Apr  5 18:12:13 2026 GMT notAfter=Jul  4 18:12:12 2026 GMT daysLeft=70.9965897337963
Apr 24 19:17:06 reverseproxy: ensureCertificate: www.stirchley.coop acme cert exists and is up to date
Apr 24 19:17:06 reverseproxy: needsRenewal: false. ARI {"start":"Wed, 03 Jun 2026 20:56:17 GMT","end":"Fri, 05 Jun 2026 16:07:06 GMT","rt":"Thu, 04 Jun 2026 03:54:39 GMT","valid":"Fri, 24 Apr 2026 22:54:51 GMT","url":"https://acme-v02.api.letsencrypt.org/acme/renewal-info","ts":"Fri, 24 Apr 2026 17:57:02 GMT"}
Apr 24 19:17:06 shell: openssl: openssl x509 -noout -subject -issuer
Apr 24 19:17:06 reverseproxy: getRenewalInfo: stirchley.coop refreshing
Apr 24 19:17:06 reverseproxy: providerMatches: subject=CN = stirchley.coop domain=stirchley.coop issuer=C = US, O = Let's Encrypt, CN = E7 wildcard=false/true prod=true/true issuerMismatch=false wildcardMismatch=false match=true
Apr 24 19:17:06 shell: openssl: openssl x509 -noout -text
Apr 24 19:17:06 shell: openssl: openssl x509 -noout -serial
Apr 24 19:17:06 ==> Changing permissions
Apr 24 19:17:07 reverseproxy: getRenewalInfo: stirchley.coop updated: {"start":"Wed, 27 May 2026 20:56:10 GMT","end":"Fri, 29 May 2026 16:06:59 GMT","rt":"Fri, 29 May 2026 01:30:42 GMT","valid":"Fri, 24 Apr 2026 23:46:26 GMT","url":"https://acme-v02.api.letsencrypt.org/acme/renewal-info","ts":"Fri, 24 Apr 2026 18:17:06 GMT"}
Apr 24 19:17:07 shell: openssl: openssl x509 -startdate -enddate -subject -noout
Apr 24 19:17:07 openssl: expiryDate: subject=CN = stirchley.coop notBefore=Mar 29 18:12:06 2026 GMT notAfter=Jun 27 18:12:05 2026 GMT daysLeft=63.99650290509259
Apr 24 19:17:07 reverseproxy: ensureCertificate: stirchley.coop acme cert exists and is up to date
Apr 24 19:17:07 reverseproxy: needsRenewal: false. ARI {"start":"Wed, 27 May 2026 20:56:10 GMT","end":"Fri, 29 May 2026 16:06:59 GMT","rt":"Fri, 29 May 2026 01:30:42 GMT","valid":"Fri, 24 Apr 2026 23:46:26 GMT","url":"https://acme-v02.api.letsencrypt.org/acme/renewal-info","ts":"Fri, 24 Apr 2026 18:17:06 GMT"}
Apr 24 19:17:07 reverseproxy: writeAppLocationNginxConfig: writing config for "www.stirchley.coop" to /home/yellowtent/platformdata/nginx/applications/74f9b0b7-8fb9-4805-9057-5d3bcf33d36b/www.stirchley.coop.conf with options {"sourceDir":"/home/yellowtent/box","vhost":"www.stirchley.coop","hasIPv6":true,"ip":"172.18.16.234","port":80,"endpoint":"app","redirectTo":null,"certFilePath":"/home/yellowtent/platformdata/nginx/cert/_.stirchley.coop.cert","keyFilePath":"/home/yellowtent/platformdata/nginx/cert/_.stirchley.coop.key","robotsTxtQuoted":null,"cspQuoted":null,"hideHeaders":[],"proxyAuth":{"id":"74f9b0b7-8fb9-4805-9057-5d3bcf33d36b","location":"/"},"upstreamUri":"","hstsPreload":false}
Apr 24 19:17:07 reverseproxy: writeAppLocationNginxConfig: writing config for "stirchley.coop" to /home/yellowtent/platformdata/nginx/applications/74f9b0b7-8fb9-4805-9057-5d3bcf33d36b/stirchley.coop.conf with options {"sourceDir":"/home/yellowtent/box","vhost":"stirchley.coop","hasIPv6":true,"ip":null,"port":null,"endpoint":"redirect","redirectTo":"www.stirchley.coop","certFilePath":"/home/yellowtent/platformdata/nginx/cert/stirchley.coop.cert","keyFilePath":"/home/yellowtent/platformdata/nginx/cert/stirchley.coop.key","robotsTxtQuoted":null,"cspQuoted":null,"hideHeaders":[],"proxyAuth":{"enabled":false,"id":"74f9b0b7-8fb9-4805-9057-5d3bcf33d36b","location":"/"},"upstreamUri":"","hstsPreload":false}
Apr 24 19:17:07 shell: reverseproxy: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/restartservice.sh nginx
Apr 24 19:17:07 tasks: updating task 14154 with: {"percent":100,"message":"Done"}
Apr 24 19:17:07 tasks: setCompleted - 14154: {"result":null,"error":null,"percent":100}
Apr 24 19:17:07 tasks: updating task 14154 with: {"completed":true,"result":null,"error":null,"percent":100}
Apr 24 19:17:07 taskworker: Task took 1.755 seconds
Apr 24 19:17:07 Exiting with code 0
Apr 24 19:17:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:17:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:17:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:17:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:17:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:17:50 BoxError: Storage volume "NetCup RS voln639290a1" is not active. Could not determine mount failure reason. 
Apr 24 19:17:50 }
Apr 24 19:17:50 }
Apr 24 19:18:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:18:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:18:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:18:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:18:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:18:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:19:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:19:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:19:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:19:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:19:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:19:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:20:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:20:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:20:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:20:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:20:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:20:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:21:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:21:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:21:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:21:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:21:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:21:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:22:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:22:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:22:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:22:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:22:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:22:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:23:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:23:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:23:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:23:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:23:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:23:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:24:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:24:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:24:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:24:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:24:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:24:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
Apr 24 19:25:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
]]>https://forum.cloudron.io/post/123994https://forum.cloudron.io/post/123994Fri, 24 Apr 2026 18:37:52 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 18:21:18 GMT]]>@james that app is now up and seems to be functioning correctly, all the data is there. Waiting for the rest to start up

]]>https://forum.cloudron.io/post/123993https://forum.cloudron.io/post/123993Fri, 24 Apr 2026 18:21:18 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 18:18:28 GMT]]>Hello @stirchley.coop
That is good to hear but also a little odd.
Just make sure that the app is in a functional state and does indeed have its data due to the still printed mount error.

]]>https://forum.cloudron.io/post/123992https://forum.cloudron.io/post/123992Fri, 24 Apr 2026 18:18:28 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 18:16:25 GMT]]>The volume has always had a green dot:

6f87b999-d1f4-4329-813e-3a25c51b5741-image.jpeg

Retry task has sorted it thank you (for one app anyway) - it still showed the mount error in the logs, but it carried on past the error this time and the app has started successfully

]]>https://forum.cloudron.io/post/123991https://forum.cloudron.io/post/123991Fri, 24 Apr 2026 18:16:25 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 18:10:04 GMT]]>Hello @stirchley.coop
Can you check in your Cloudron dashboard under Volumes?
If the volume has a red dot, please press the ... button to the right side and then press Remount.
When the remount works signalled by a green dot, you can go to your apps that are unresponsive into the Repair section and press Retry task.
This should repair the unresponsive apps back into a working state.

]]>https://forum.cloudron.io/post/123990https://forum.cloudron.io/post/123990Fri, 24 Apr 2026 18:10:04 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 18:06:08 GMT]]>It seems to have settled into this state:

2026-04-24T18:01:40.032Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:01:50.030Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:02:00.043Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:02:10.027Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:02:20.032Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:02:30.028Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:02:40.034Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:02:50.028Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:03:00.040Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:03:10.027Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:03:20.029Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:03:30.027Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:03:40.030Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:03:50.031Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:04:00.037Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:04:10.029Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:04:20.035Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:04:30.029Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
2026-04-24T18:04:40.037Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive

There are 5 apps in Error state with the same mount error above. I assume they correspond to the 5 unresponsive apps in the logs. There are also 5 other stopped apps

]]>https://forum.cloudron.io/post/123989https://forum.cloudron.io/post/123989Fri, 24 Apr 2026 18:06:08 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 18:01:11 GMT]]>Sure will do

]]>https://forum.cloudron.io/post/123988https://forum.cloudron.io/post/123988Fri, 24 Apr 2026 18:01:11 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 17:59:48 GMT]]>The log looks correct so far.
It is recreating the containers due to the update and this can take some time.
Can you observe this for maybe 5 minutes and report back?

]]>https://forum.cloudron.io/post/123987https://forum.cloudron.io/post/123987Fri, 24 Apr 2026 17:59:48 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 17:58:05 GMT]]>That's fine I spotted and corrected it

]]>https://forum.cloudron.io/post/123986https://forum.cloudron.io/post/123986Fri, 24 Apr 2026 17:58:05 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 17:58:12 GMT]]>Apologies, I did a typo.

systemctl restart box.service

But I see you fixed the typo.

]]>https://forum.cloudron.io/post/123985https://forum.cloudron.io/post/123985Fri, 24 Apr 2026 17:58:12 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 18:46:21 GMT]]>@james a lot of network errors so far:

root@v2202403157799261297:~# systemcrtl restart box.service
Command 'systemcrtl' not found, did you mean:
  command 'systemctl' from deb systemd (249.11-0ubuntu3.20)
  command 'systemctl' from deb systemctl (1.4.4181-1.1)
Try: apt install <deb name>
root@v2202403157799261297:~# systemctl restart box.service
root@v2202403157799261297:~# tail -f /home/yellowtent/platformdata/logs/box.log
2026-04-24T17:54:34.309Z docker: deleteContainer: deleting turn
2026-04-24T17:54:34.310Z services: startTurn: starting turn container
2026-04-24T17:54:34.310Z shell: services: /bin/bash -c docker run --restart=unless-stopped -d --name=turn                 --hostname turn                 --net host                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=turn                 -m 268435456                 --memory-swap -1                 -e CLOUDRON_TURN_SECRET=-REDACTED- -e CLOUDRON_REALM=my.stirchley.coop                 -e CLOUDRON_VERBOSE_LOGS=                 --label isCloudronManaged=true                 --read-only -v /tmp -v /run registry.docker.com/cloudron/turn:1.8.2@sha256:9f3609969a5757837505c584c98246a3035a84a273b9be491665ac026423fd5f
2026-04-24T17:54:34.526Z services: startMysql: stopping and deleting previous mysql container
2026-04-24T17:54:34.526Z docker: stopContainer: stopping container mysql
2026-04-24T17:54:34.529Z docker: deleteContainer: deleting mysql
2026-04-24T17:54:34.530Z services: startMysql: starting mysql container
2026-04-24T17:54:34.530Z shell: services: /bin/bash -c docker run --restart=unless-stopped -d --name=mysql                 --hostname mysql                 --net cloudron                 --net-alias mysql                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=mysql                 --ip xxx                 -e CLOUDRON_MYSQL_TOKEN=xxx                 -e CLOUDRON_MYSQL_ROOT_HOST=xxx                 -e CLOUDRON_MYSQL_ROOT_PASSWORD=xxx -v /home/yellowtent/platformdata/mysql:/var/lib/mysql                 --label isCloudronManaged=true                 --cap-add SYS_NICE                 --read-only -v /tmp -v /run registry.docker.com/cloudron/mysql:3.5.3@sha256:615057dbfeb5d979ab17c3e4cef240f11ae63b95feadbaf95a30e730472980aa
2026-04-24T17:54:34.909Z services: Waiting for mysql
2026-04-24T17:54:34.914Z services: Attempt 1 failed. Will retry: Network error waiting for mysql: connect ECONNREFUSED 172.18.30.1:3000
2026-04-24T17:54:50.061Z services: startPostgresql: stopping and deleting previous postgresql container
2026-04-24T17:54:50.061Z docker: stopContainer: stopping container postgresql
2026-04-24T17:54:50.063Z docker: deleteContainer: deleting postgresql
2026-04-24T17:54:50.063Z services: startPostgresql: starting postgresql container
2026-04-24T17:54:50.063Z shell: services: /bin/bash -c docker run --restart=unless-stopped -d --name=postgresql                 --hostname postgresql                 --net cloudron                 --net-alias postgresql                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=postgresql                 --ip 172.18.30.2                 --shm-size=128M                 -e CLOUDRON_POSTGRESQL_ROOT_PASSWORD=xxx                 -e CLOUDRON_POSTGRESQL_TOKEN=xxx                 -v /home/yellowtent/platformdata/postgresql:/var/lib/postgresql                 --label isCloudronManaged=true                 --read-only -v /tmp -v /run registry.docker.com/cloudron/postgresql:6.3.1@sha256:95a2e1e298fb88740c6d1d200657dcce993346ba500870e8e885a1aee519dc20
2026-04-24T17:54:50.455Z services: Waiting for postgresql
2026-04-24T17:54:50.458Z services: Attempt 1 failed. Will retry: Network error waiting for postgresql: connect ECONNREFUSED 172.18.30.2:3000
2026-04-24T17:55:05.613Z services: startMongodb: stopping and deleting previous mongodb container
2026-04-24T17:55:05.613Z docker: stopContainer: stopping container mongodb
2026-04-24T17:55:05.615Z docker: deleteContainer: deleting mongodb
2026-04-24T17:55:05.616Z shell: services: grep -q avx /proc/cpuinfo
2026-04-24T17:55:05.619Z services: startMongodb: starting mongodb container
2026-04-24T17:55:05.619Z shell: services: /bin/bash -c docker run --restart=unless-stopped -d --name=mongodb                 --hostname mongodb                 --net cloudron                 --net-alias mongodb                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=mongodb                 --ip 172.18.30.3                 -e CLOUDRON_MONGODB_ROOT_PASSWORD=xxx                 -e CLOUDRON_MONGODB_TOKEN=xxx                 -v /home/yellowtent/platformdata/mongodb:/var/lib/mongodb                 --label isCloudronManaged=true                 --read-only -v /tmp -v /run registry.docker.com/cloudron/mongodb:6.3.0@sha256:8757111970a99fb9a9880f02a2a77fe9cb7368745fcff555bf528471ecb50ec3
2026-04-24T17:55:05.995Z services: Waiting for mongodb
2026-04-24T17:55:05.998Z services: Attempt 1 failed. Will retry: Network error waiting for mongodb: connect ECONNREFUSED 172.18.30.3:3000
2026-04-24T17:55:21.502Z services: Attempt 2 failed. Will retry: Error waiting for mongodb. Status code: 200 message: Not ready yet: uptime=3
2026-04-24T17:55:36.979Z services: startRedis: stopping and deleting previous redis container redis-1502ffae-d38e-4b8a-a75d-c833b1355a4d
2026-04-24T17:55:36.979Z docker: stopContainer: stopping container redis-1502ffae-d38e-4b8a-a75d-c833b1355a4d
2026-04-24T17:55:36.981Z docker: deleteContainer: deleting redis-1502ffae-d38e-4b8a-a75d-c833b1355a4d
2026-04-24T17:55:36.982Z services: startRedis: starting redis container redis-1502ffae-d38e-4b8a-a75d-c833b1355a4d
2026-04-24T17:55:36.988Z shell: services: /bin/bash -c docker create --restart=unless-stopped --name=redis-1502ffae-d38e-4b8a-a75d-c833b1355a4d                 --hostname redis-1502ffae-d38e-4b8a-a75d-c833b1355a4d                 --label=location=data2.stirchley.coop                 --net cloudron                 --net-alias redis-1502ffae-d38e-4b8a-a75d-c833b1355a4d                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=redis-1502ffae-d38e-4b8a-a75d-c833b1355a4d                 -m 268435456                 --memory-swap -1                 -e CLOUDRON_REDIS_PASSWORD=xxx                 -e CLOUDRON_REDIS_TOKEN=xxx                 -v /home/yellowtent/platformdata/redis/1502ffae-d38e-4b8a-a75d-c833b1355a4d:/var/lib/redis                 --label isCloudronManaged=true                 --read-only -v /tmp -v /run registry.docker.com/cloudron/redis:3.8.0@sha256:54a12252edbc326fd4d10e8c00836cc68776f3463f22366279f7cd8d4dafd20f
2026-04-24T17:55:37.211Z services: startRedis: stopping and deleting previous redis container redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73
2026-04-24T17:55:37.211Z docker: stopContainer: stopping container redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73
2026-04-24T17:55:37.213Z docker: deleteContainer: deleting redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73
2026-04-24T17:55:37.213Z services: startRedis: starting redis container redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73
2026-04-24T17:55:37.217Z shell: services: /bin/bash -c docker run -d --restart=unless-stopped --name=redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73                 --hostname redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73                 --label=location=docs2.stirchley.coop                 --net cloudron                 --net-alias redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73                 -m 268435456                 --memory-swap -1                 -e CLOUDRON_REDIS_PASSWORD=                 -e CLOUDRON_REDIS_TOKEN=xxx                 -v /home/yellowtent/platformdata/redis/1aa55af7-48e4-4f6f-816f-46185ef4cf73:/var/lib/redis                 --label isCloudronManaged=true                 --read-only -v /tmp -v /run registry.docker.com/cloudron/redis:3.8.0@sha256:54a12252edbc326fd4d10e8c00836cc68776f3463f22366279f7cd8d4dafd20f
2026-04-24T17:55:37.465Z services: Waiting for redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73
2026-04-24T17:55:37.468Z services: Attempt 1 failed. Will retry: Network error waiting for redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73: connect ECONNREFUSED 172.18.0.2:3000
]]>https://forum.cloudron.io/post/123984https://forum.cloudron.io/post/123984Fri, 24 Apr 2026 18:46:21 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 17:54:02 GMT]]>Hello @stirchley.coop

@Stirchley.coop said:

I'm thinking I uninstall Cloudron from the server and reinstall version 9.1.5 with yesterday's backup

This would be the easy / safe route.
I think we can figure out this issue together and fix your server without restoring from a backup.
But the decision is up to you.

This output:

root@v2202403157799261297:~# docker ps -a
CONTAINER ID   IMAGE                                      COMMAND                CREATED          STATUS    PORTS     NAMES
f472efd072b2   registry.docker.com/cloudron/mail:3.18.2   "/app/code/start.sh"   17 minutes ago   Created             mail

is very suspicious.
No other docker container running from cloudron except this one.

Can you try to restart the box.service with:

systemcrtl restart box.service

Then you can also observe the box.log with:

tail -f /home/yellowtent/platformdata/logs/box.log

To see all log messages from Cloudron.

]]>https://forum.cloudron.io/post/123983https://forum.cloudron.io/post/123983Fri, 24 Apr 2026 17:54:02 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 17:53:37 GMT]]>@james

root@v2202403157799261297:~# docker ps -a
CONTAINER ID   IMAGE                                      COMMAND                CREATED          STATUS    PORTS     NAMES
f472efd072b2   registry.docker.com/cloudron/mail:3.18.2   "/app/code/start.sh"   17 minutes ago   Created             mail
root@v2202403157799261297:~# docker network list
NETWORK ID     NAME       DRIVER    SCOPE
cbe520222cfe   bridge     bridge    local
e28b8f24a89c   cloudron   bridge    local
f8d98b330cd7   host       host      local
d58248fbb326   none       null      local
root@v2202403157799261297:~#
]]>https://forum.cloudron.io/post/123982https://forum.cloudron.io/post/123982Fri, 24 Apr 2026 17:53:37 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 17:49:38 GMT]]>Hello @stirchley.coop
Can you please share the output of the command:

docker ps -a

and

docker network list
]]>https://forum.cloudron.io/post/123981https://forum.cloudron.io/post/123981Fri, 24 Apr 2026 17:49:38 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 17:49:06 GMT]]>I'm thinking I uninstall Cloudron from the server and reinstall version 9.1.5 with yesterday's backup

]]>https://forum.cloudron.io/post/123980https://forum.cloudron.io/post/123980Fri, 24 Apr 2026 17:49:06 GMT<![CDATA[Reply to Error in apps accessing NFS volume after upgrade to v9.1.6 on Fri, 24 Apr 2026 17:48:37 GMT]]>Ok after installing I get this:

root@v2202403157799261297:~# netstat -tulpen | grep -i 995
root@v2202403157799261297:~# lsof -i :995
root@v2202403157799261297:~#
]]>https://forum.cloudron.io/post/123979https://forum.cloudron.io/post/123979Fri, 24 Apr 2026 17:48:37 GMT