Cloudron not starting Properly After Upgrade to 9.0.13
-
Unfortunately our Cloudron Instance and its Apps are not coming up after last night's upgrade to 9.0.13. (previous version 8.3.2)
The Logs also showed an Error during the upgrade procedure:
Dec 1, 2025, 01:06 AM cron Cloudron update errored. Error: Task 9868 crashed with code null { "taskId": "9868", "errorMessage": "Task 9868 crashed with code null", "timedOut": false }The new v9 GUI And Cloudron Backend itself is up and running as well as the docker and nginx service. The other services are not able to restart.
Cloudron itself indicates that it is "Removing containers for upgrade".
Any idea how to roll back or unblock the upgrade process?
Any help is highly appreciated.
Best regards
Wolfgang -
I was investigating this on support.
2025-12-01T13:53:05.270Z box:shell platform: docker network create --subnet=172.18.0.0/16 --ip-range=172.18.0.0/20 --gateway=172.18.0.1 --ipv6 --subnet=fd00:c107:d509::/64 cloudron errored BoxError: docker exited with code 1 signal null at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:82:23) at ChildProcess.emit (node:events:519:28) at maybeClose (node:internal/child_process:1101:16) at ChildProcess._handle.onexit (node:internal/child_process:304:5) { reason: 'Shell Error', details: {}, stdout: '', stdoutLineCount: 0, stderr: 'Error response from daemon: open /proc/sys/net/bridge/bridge-nf-call-ip6tables: permission denied: set environment variable DOCKER_IGNORE_BR_NETFILTER_ERROR=1 to ignore\n', stderrLineCount: 1, code: 1, signal: null, timedOut: false, terminated: false }Docker in turn shows this message:
Dec 01 09:45:34 xx dockerd[304]: time="2025-12-01T09:45:34.027408826+01:00" level=error msg="Handler for POST /v1.49/networks/create returned error: open /proc/sys/net/bridge/bridge-nf-call-ip6tables: permission denied: set environment variable DOCKER_IGNORE_BR_NETFILTER_ERROR=1 to ignore" -
@woolfdrs3 It seems the server is running on OpenVZ which Cloudron doesn't actively support. However, it works after I added this workaround:
# cat /etc/systemd/system/docker.service.d/openvz.conf [Service] Environment="DOCKER_IGNORE_BR_NETFILTER_ERROR=1" -
J joseph has marked this topic as solved