Cloudron Forum

Many many thanks to @james who has providing me a very great support.
Without him I wouldn't have corretcly migrated my Dolibarr.

Thank you again!

I'm using Bunny DNS which are EU based.
And it works like a charm with Cloudron

thank you for all your explanations

Needed to run

cp /etc/docker/daemon.json /etc/docker/daemon.json.bak
printf '{}\n' > /etc/docker/daemon.json
systemctl restart docker
systemctl status docker --no-pager

As per the Hostinger AI, there were an issue aroundlog-driver in conflict

Oh, you're right, I do not remember when the "accelerated" feature has been activated.
I think the issue is solved. !Thanks @james

oh! I'm sorry, i missed @james answer. wp db command works with the full path

https://forum.cloudron.io/topic/14610/not-receiving-tickets-in-freescout-helpdesk-cloudron-419-errors-on-polycast-receive/5?_=1768070658349

Rebooting mail service and then Freescout app is solving the issue.
I will monitor to see if it's definitively fixed.

Changed it simply in the conf.php

Thank you @james
Increasing the part size has fixed the issue.

Hello,
I've just updated my Dolibarr Package to 1.13.3 and restart.
I confirm the install.lock is kept.

Thank for the update.

root@my:~# cloudron-support --troubleshoot
Vendor: QEMU Product: Standard PC (i440FX + PIIX, 1996)
Linux: 6.8.0-110-generic
Ubuntu: noble 24.04
Execution environment: kvm
Processor: AMD EPYC 9354P 32-Core Processor
BIOS pc-i440fx-10.1  CPU @ 2.0GHz x 4
RAM: 16376024KB
Disk: /dev/sda1       141G
[OK]    node version is correct
[OK]    IPv6 is enabled and public IPv6 address is working
        Docker is down. Trying to restart docker ...
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.
root@my:~# 

root@my:~# journalctl -xeu docker.service
░░ Automatic restarting of the unit docker.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Apr 18 07:28:23 my systemd[1]: Starting docker.service - Docker Application Container Engine...
░░ Subject: A start job for unit docker.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit docker.service has begun execution.
░░ 
░░ The job identifier is 624.
Apr 18 07:28:23 my dockerd[1081]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives are specified both as a flag and in the configuration file: log-driver: (from >
Apr 18 07:28:23 my systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit docker.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 18 07:28:23 my systemd[1]: docker.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit docker.service has entered the 'failed' state with result 'exit-code'.
Apr 18 07:28:23 my systemd[1]: Failed to start docker.service - Docker Application Container Engine.
░░ Subject: A start job for unit docker.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit docker.service has finished with a failure.
░░ 
░░ The job identifier is 624 and the job result is failed.
Apr 18 07:28:25 my systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ Automatic restarting of the unit docker.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Apr 18 07:28:25 my systemd[1]: docker.service: Start request repeated too quickly.
Apr 18 07:28:25 my systemd[1]: docker.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit docker.service has entered the 'failed' state with result 'exit-code'.
Apr 18 07:28:25 my systemd[1]: Failed to start docker.service - Docker Application Container Engine.
░░ Subject: A start job for unit docker.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit docker.service has finished with a failure.
░░ 
░░ The job identifier is 741 and the job result is failed.

root@my:~#

I need help to solve this please

Hello,

On Cloudron 9.0.8 and Ubuntu 24.04, Mastodon doesn't work.
In the log, I can see lots of:

Nov 13 10:09:47 {"level":"error","time":1763024987095,"pid":42,"hostname":"0698ee0d-3f40-4fc5-acfd-1a78f21a450c","name":"streaming","err":{"type":"Error","message":"getaddrinfo EAI_AGAIN redis-0698ee0d-3f40-4fc5-acfd-1a78f21a450c","stack":"Error: getaddrinfo EAI_AGAIN redis-0698ee0d-3f40-4fc5-acfd-1a78f21a450c\n at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26)","errno":-3001,"code":"EAI_AGAIN","syscall":"getaddrinfo","hostname":"redis-0698ee0d-3f40-4fc5-acfd-1a78f21a450c"},"msg":"Redis Client Error!"}

How to fix please ?

@p44 tip works but it's really easier to launch a wp db import backup.sql command.

The issue was around RAM value to Redis service.
Issue solved

Hello,
On https://docs.cloudron.io/guides/upgrade-ubuntu-24/ it is said to use the cli command:

# do-release-upgrade -d

which is resulting

$ do-release-upgrade -d
Checking for a new Ubuntu release
There is no development version of an LTS available.
To upgrade to the latest non-LTS development release 
set Prompt=normal in /etc/update-manager/release-upgrades.
$ 

Because Cloudron 9 will prompt to update to Ubuntu 24.04, I think the documentaiton should be corrected.
Maybe without the -d

Hello,
I've a Dolibarr hosted on another hosting provider.
How to migrate / import my DB & Dolibarr install to Cloudron ?

regards

Hello,

Mails from @gmail.com are often blocked by Spamassasiin on my Cloudron with the erroro 903 "Plugin Timeout".
The email is not delivered.

Is someone know how to fix this ?

Logs

{
    "ts": 1767292158277,
    "type": "denied",
    "direction": "inbound",
    "uuid": "82609B82-F473-4CB7-A1F4-688EAFBF38E3.1",
    "messageId": "<CAL90chqLCd3J6iisXg4XXXXGuhV0dsGxzOSvupbFMKjQ@mail.gmail.com>",
    "mailFrom": "<XXXXstien@gmail.com>",
    "spamStatus": null,
    "mailbox": null,
    "quotaPercent": null,
    "rcptTo": [
        "<seb@stXXXe.com>" ## Cloudron hosted email address
    ],
    "remote": {
        "ip": "209.85.216.49",
        "port": 54471,
        "host": "mail-pj1-f49.google.com",
        "info": "mail-pj1-f49.google.com",
        "closed": false,
        "is_private": false,
        "is_local": false
    },
    "authUser": null,
    "relaying": false,
    "pluginName": "spamassassin",
    "errorCode": 903,
    "message": "plugin timeout",
    "rejectionCountLastHour": 0,
    "_id": "82609B82-F473-4CB7-A1F4-688EAFBF38E3.1-1767292158277",
    "isOpen": true
}

Issue also reported at https://forum.cloudron.io/topic/7150/mails-plugin-timeout-spamassassin-from-time-to-time

Hello,

Is there some of you who are backuping their Cloudron to their Synology NAS ?
I have a DS720+ and I wonder how I could setup a backup on Cloudron to save it on my NAS.

Do you have some tips ?

Regards

Hello

Yes it seems to work thank you

Thanks

I'm running Cloudron 9.0.15, and I wonder if having nothing in Backup > App Archive is normal ?