Cloudron down after Ubuntu/Docker update (Docker service fails to start)

[Valexico]

@james
So, should we do something to restore our cloudron to nominal configuration ? Recreate this cloudron.conf file somehow ?

[james]

Hello @valexico

@Valexico said:

So, should we do something to restore our cloudron to nominal configuration ? Recreate this cloudron.conf file somehow ?

That would be best I think.
If this would reproduce the previous issue, that be interesting to get an understanding what is causing this.

The default content from /etc/systemd/system/docker.service.d/cloudron.conf is:

[Service]
ExecStart=
ExecStart=/usr/bin/dockerd -H fd:// --log-driver=journald --exec-opt native.cgroupdriver=cgroupfs --storage-driver=overlay2 --experimental --ip6tables --userland-proxy=false

[Valexico]

hi @james

I tried to restore this file but docker won't start.

Claude analysis :

• systemd (file cloudron.conf) passes --log-driver=journald
• But /etc/docker/daemon.json also defines log-driver: json-file

So what is the official fix ?

Here are some logs :

tail -n 40 ../yellowtent/platformdata/logs/box.log
  stdout: '',
  stdoutString: '',
  stdoutLineCount: 0,
  stderr: 'Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?\n',
  stderrString: 'Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?\n',
  stderrLineCount: 1,
  code: 1,
  signal: null,
  timedOut: false,
  terminated: false
}
2026-04-20T20:18:28.212Z shell: docker: docker update --memory 268435456 --memory-swap -1 redis-9d1726c8-d217-45ab-ac30-0ec5c01c4cf0 errored BoxError: docker 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 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: 'Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?\n',
  stderrString: 'Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?\n',
  stderrLineCount: 1,
  code: 1,
  signal: null,
  timedOut: false,
  terminated: false
}
2026-04-20T20:18:28.213Z cron: handleAutoupdateConfigChanged: schedule - 00 00 1,2,3,4,5 * * 0,4/Europe/Paris, policy - platform_and_apps
2026-04-20T20:18:28.215Z cron: Dynamic DNS setting changed to false
2026-04-20T20:18:28.216Z dockerproxy: start: listening on 172.18.0.1:3003
2026-04-20T20:18:28.216Z From uncaughtException handler.
2026-04-20T20:18:28.216Z Error: listen EADDRNOTAVAIL: address not available 172.18.0.1:3003
2026-04-20T20:18:28.216Z     at Server.setupListenHandle [as _listen2] (node:net:1918:21)
2026-04-20T20:18:28.216Z     at listenInCluster (node:net:1997:12)
2026-04-20T20:18:28.216Z     at node:net:2206:7
2026-04-20T20:18:28.216Z     at process.processTicksAndRejections (node:internal/process/task_queues:89:21)

sudo journalctl -u docker --since "today" | grep -A5 "error\|Error\|failed\|Failed" | head -60
Apr 20 09:14:20 srv565755 dockerd[928]: time="2026-04-20T09:14:20.051807769Z" level=warning msg="ShouldRestart failed, container will not be restarted" container=4f0cb8c35e7ba64d6a081361646cb651cc3956442e62c97946f0d15edd6de455 daemonShuttingDown=false error="restart canceled" execDuration=13h52m56.033484743s exitStatus="{0 2026-04-20 09:14:19.681121204 +0000 UTC}" hasBeenManuallyStopped=true restartCount=0
Apr 20 09:16:48 srv565755 dockerd[928]: time="2026-04-20T09:16:48.421429471Z" level=info msg="Configured log driver does not support reads, enabling local file cache for container logs" container=951df08d2fe64f854504c7f945d526f99347a3b7ffc6b5742479f18ee8595776 driver=syslog
Apr 20 09:16:48 srv565755 dockerd[928]: time="2026-04-20T09:16:48.647044948Z" level=info msg="Skipping check for route to send NA, EMSGSIZE" eid=587f20e087dc ep=1c5d0773-9eca-48f8-945e-83733391299d net=cloudron nid=b08cee04d967
Apr 20 09:16:48 srv565755 dockerd[928]: time="2026-04-20T09:16:48.653269180Z" level=info msg="sbJoin: gwep4 ''->'587f20e087dc', gwep6 ''->'587f20e087dc'" eid=587f20e087dc ep=1c5d0773-9eca-48f8-945e-83733391299d net=cloudron nid=b08cee04d967
Apr 20 11:33:17 srv565755 dockerd[928]: time="2026-04-20T11:33:17.566840739Z" level=info msg="ignoring event" container=951df08d2fe64f854504c7f945d526f99347a3b7ffc6b5742479f18ee8595776 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Apr 20 11:33:17 srv565755 dockerd[928]: time="2026-04-20T11:33:17.626250628Z" level=warning msg="ShouldRestart failed, container will not be restarted" container=951df08d2fe64f854504c7f945d526f99347a3b7ffc6b5742479f18ee8595776 daemonShuttingDown=false error="restart canceled" execDuration=2h16m29.209514787s exitStatus="{0 2026-04-20 11:33:17.50260464 +0000 UTC}" hasBeenManuallyStopped=true restartCount=0
Apr 20 11:33:31 srv565755 dockerd[928]: time="2026-04-20T11:33:31.302996371Z" level=info msg="Configured log driver does not support reads, enabling local file cache for container logs" container=5cd41c6952e0e4a57df020a068ba8d8ad03a1962cf5166c16def923db4a19678 driver=syslog
Apr 20 11:33:31 srv565755 dockerd[928]: time="2026-04-20T11:33:31.544418039Z" level=info msg="Skipping check for route to send NA, EMSGSIZE" eid=cc6732021dd2 ep=1c5d0773-9eca-48f8-945e-83733391299d net=cloudron nid=b08cee04d967
Apr 20 11:33:31 srv565755 dockerd[928]: time="2026-04-20T11:33:31.550239968Z" level=info msg="sbJoin: gwep4 ''->'cc6732021dd2', gwep6 ''->'cc6732021dd2'" eid=cc6732021dd2 ep=1c5d0773-9eca-48f8-945e-83733391299d net=cloudron nid=b08cee04d967
Apr 20 20:17:06 srv565755 systemd[1]: Stopping docker.service - Docker Application Container Engine...
Apr 20 20:17:06 srv565755 dockerd[928]: time="2026-04-20T20:17:06.327530091Z" level=info msg="Processing signal 'terminated'"
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.546853647Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.555695229Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.555782219Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.555813540Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.566229495Z" level=info msg="ignoring event" container=0b8f6fb173a1d0e2d4dedcbfba65145ed2a57c720caab9bbe67f404771fc0c88 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.568576383Z" level=info msg="ignoring event" container=b84eb548ee71992483f45e56428929b79bcc8aad1f7023b195c60f659780d168 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.582046353Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.582069903Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.582693859Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.589390793Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.632285602Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.659873666Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.704349637Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.730620892Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.730674482Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.730804793Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.751950246Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.766076720Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.774481318Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.792120681Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.792250913Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.820107909Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.842432751Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.842499741Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.842352570Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.889893867Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.898854650Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.905530513Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.914025273Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.914073723Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.915739917Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.917869824Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.921901237Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.921959517Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.940298087Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.940385708Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.940415097Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.957654048Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.984816919Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.984879059Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:07 srv565755 dockerd[928]: time="2026-04-20T20:17:07.984904639Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:08 srv565755 dockerd[928]: time="2026-04-20T20:17:08.002561723Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:08 srv565755 dockerd[928]: time="2026-04-20T20:17:08.002633953Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:08 srv565755 dockerd[928]: time="2026-04-20T20:17:08.002662174Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:08 srv565755 dockerd[928]: time="2026-04-20T20:17:08.002688504Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:08 srv565755 dockerd[928]: time="2026-04-20T20:17:08.023282142Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:08 srv565755 dockerd[928]: time="2026-04-20T20:17:08.032926700Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:08 srv565755 dockerd[928]: time="2026-04-20T20:17:08.052743052Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=
Apr 20 20:17:08 srv565755 dockerd[928]: time="2026-04-20T20:17:08.052817351Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=

[james]

Hello @valexico
So this is the actuall error:

Apr 20 20:17:08 srv565755 dockerd[928]: time="2026-04-20T20:17:08.052817351Z" level=error msg="Error writing log message" driver=syslog error="dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: no such file or directory" message=

Can you please check the status of:

systemctl status cloudron-syslog.service

[Valexico]

hi @james

Here the status on my fixed (cloudron.conf deleted). I can't check with the error as this server is used in production... I would have to test at night this not very convenient

systemctl status cloudron-syslog.service
WARNING: terminal is not fully functional
Press RETURN to continue
● cloudron-syslog.service - Cloudron Syslog
     Loaded: loaded (/etc/systemd/system/cloudron-syslog.service; enabled; preset: enabled)
     Active: active (running) since Mon 2026-04-20 20:20:34 UTC; 12h ago
   Main PID: 734 (MainThread)
      Tasks: 11 (limit: 19092)
     Memory: 71.9M (peak: 72.4M)
        CPU: 9.000s
     CGroup: /system.slice/cloudron-syslog.service
             └─734 node /home/yellowtent/box/syslog.js

[james]

Hello @valexico
Can you check if the sock file does really not exist?

/home/yellowtent/platformdata/logs/syslog.sock

[Valexico]

@james

ls -l /home/yellowtent/platformdata/logs/syslog.sock
srwxr-xr-x 1 yellowtent yellowtent 0 Apr 20 20:20 /home/yellowtent/platformdata/logs/syslog.sock

[Valexico]

@james
For what it's worth, it is also an Hostinger VPS

[ntnsndr]

@osobo Thank you so much for posting this! I also had the same issue on Hostinger this morning after a manual reboot, and the OP instructions worked.

[Valexico]

@james
Any idea what could be specific to Hostinger in this issue ? I mean It's just a raw ubuntu installation in my case where I installed manually Cloudron

[james]

Hello @ntnsndr and @valexico
That two times a Hostinger set up is having the same issue is not a coincidence.
Still, I am not sure what is going on.
The file in question exists. So why does the docker daemon suddenly act in this way.

[Valexico]

Hi @james
So what should we do at the end? My cloudron server is quite critical for my business, and deleting a config file to make it up sounds a bit scary. I would be glad to have an official fix or recommendation on this.

[james]

Hello @valexico
Can you please write a mail to support@cloudron.io and enable remote support?
Also, please give us a timeframe when we can restart processes like the docker and the box service to analyse the issue.

[joseph]

Thanks for the access @valexico . The issue has to do with the faulty ubuntu kernel update . Updating the firewall makes it work.

Technical details: Cloudron configures docker and containers to log using the syslog service (cloudron-syslog) . Because of the kernel regression, docker is unable to reach the syslog service and doesn't start anymore. The cgroupfs was not the issue.

We are making a patch release for Cloudron which fixes the firewall rules .

[Valexico]

@joseph
At the end is it related to hostinger config or any user would face this issue upon reboot ? Where does the faulty update comes from ?

[joseph]

@valexico issue is not specific to hostinger . Ubuntu has pushed a new kernel which is causing problems with Cloudron's firewall. We are making a new release to workaround this issue.

[AndyCPNW]

Just experienced this today. Also on Hostinger. Requested reboot and system will not come back online. Have not applied the fix yet so if you want a system that is still broken and you want to investigate, let me know.

[joseph]

@AndyCPNW please check the ubuntu kernel versions. It's 110 probably?

The quick fix:

• Edit /etc/systemd/system/docker.service.d/cloudron.conf . Change --log-driver=json-file .
• systemctl daemon-reload and systemctl restart docker box

Cloudron 9.1.7 is being rolled out. You can update once the system is up and it will fix the firewall.

[AndyCPNW]

@joseph Thanks - I tried the cloudron-firewall.sh patch and restarting but did not get docker to come up so I deleted the conf file like the original solution suggested and it came right back again. Yes it was kernel 110. Everything seems to be running now. Bummer that kernel upgrade caused all of this. Thanks for the help.

[phil_b]

Hello,

I am experiencing the same issue, which appeared suddenly. I have tried the different fixes suggested in this thread, but none of them really worked.

Last night, I was able to restart the server and everything seemed to be working fine. However, this morning when I checked again, the system was unresponsive once more.

I am currently traveling for the next 10 days, away from my office, and I only have an iPad with me. I connect to a computer at my office remotely, and from there I access my Cloudron. However, the internet connection where I am is very unstable, which makes troubleshooting extremely difficult.

Thank you in advance for any help you can provide.

Best regards,
Philippe