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

[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.