Cloudron Forum

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

Hello,

From some days, I have some "504" errors on my Mastodon app.
This evening I can't post a message => 504
How to know what is wrong ?

Mastodon 4.5.11 / 1.17.12
Cloudron 9.20
https://paste.cloudron.io/upload/bear-goose-pig

OK, so I had mail.thivinfo.com as PTR but the cloudron troubleshot report in 1st comment, said

[FAIL]	IPv6: could not load https://my.thivinfo.com

So I do not understand....

Moreover the Cloudron Trouble shoot command is asking me something different from the Cloudron mail settings....

How can I have a PTR on my.thivinfo.com asked by the troubleshot command and to mail.thivinfo.com ?
Mail.* is my mailserver location on the settings due to long time setup before I migrated to Cloudron)

It now seems OK https://www.whatsmydns.net/#PTR/2a02:4780:28:cf44::1 but Cloudron always fail in the Troubleshot command

But one is set on the bunny DNS (created through the API directly by Cloudron)
https://mxtoolbox.com/SuperTool.aspx?action=aaaa%3Amy.thivinfo.com&run=toolpage

root@my:~# cloudron-support --troubleshoot
Vendor: QEMU Product: Standard PC (i440FX + PIIX, 1996)
Linux: 6.8.0-124-generic
Ubuntu: noble 24.04
Cloudron: 9.2.0
Execution environment: kvm
Processor: AMD EPYC 9354P 32-Core Processor
BIOS pc-i440fx-10.1  CPU @ 2.0GHz x 2
RAM: 8131468KB
Disk: /dev/sda1        50G
[OK]	Root disk usage is OK (49%)
[OK]	Memory usage is OK (67%)
[OK]	Clock is NTP-synchronized
[OK]	node version is correct
[OK]	IPv6 is enabled in kernel. Public IPv6 address detected
[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]	IPv4 HTTPS to api.cloudron.io/api/v1/helper/public_ip
[OK]	IPv6 HTTPS to api.cloudron.io/api/v1/helper/public_ip
[OK]	IPv4 HTTPS to auth.docker.io/token
[OK]	IPv6 HTTPS to auth.docker.io/token
[OK]	IPv4 HTTPS to acme-v02.api.letsencrypt.org
[OK]	IPv6 HTTPS to acme-v02.api.letsencrypt.org
[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
[WARN]	Service 'mongodb' is not running (may be lazy-stopped)
[OK]	Service 'mail' is running and healthy
[OK]	Service 'graphite' is running and healthy
[OK]	Service 'sftp' is running and healthy
[OK]	box v9.2.0 is running
[OK]	Dashboard is reachable via IPv4 (https://my.thivinfo.com)
[FAIL]	IPv6: could not load https://my.thivinfo.com
[OK]	Domain thivinfo.com is valid and has not expired

======== Summary ========
PASS:  29
WARN:  1
FAIL:  1
SKIP:  0

Failures:
  - IPv6: could not load https://my.thivinfo.com

Warnings:
  - Service 'mongodb' is not running (may be lazy-stopped)

For troubleshooting tips, see https://docs.cloudron.io/troubleshooting
To share a full diagnostic dump on the forum, run: cloudron-support --send-diagnostics
root@my:~# 

Hello,

For some days, I have had several emails not delivered.
In the logs, I can read:

{
    "ts": 1781015387801,
    "type": "deferred",
    "direction": "outbound",
    "uuid": "3118C384-EC0C-43D8-B705-41F57EEC074B.1",
    "messageId": null,
    "mailFrom": "<>",
    "spamStatus": null,
    "mailbox": null,
    "quotaPercent": null,
    "rcptTo": [
        "<communication@XXX.com>"
    ],
    "message": "Tried all MXs",
    "delay": 65536,
    "failRecips": null,
    "mx": null,
    "_id": "3118C384-EC0C-43D8-B705-41F57EEC074B.1-1781015387801",
    "isOpen": true
}

Any idea what is happening ?

Cloudron 9.20

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.

Hello,

Today, scheduled invoices haven't been created due to a permission error on the folder storing them in /app/data/dolibarr/facture/FA2604-0802
Also, I have set the cron job to run with ww-data but it still rotates the log on root user:

Hello

I thought this issue has been fixed, but we always have the issue. (which is a security one)
I do not know why the Cloudron Dolibarr app runs the cron as root and not as www-data user.

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

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

Fixed by setting my own cron job https://forum.cloudron.io/topic/14965/which-user-for-cron-task/4?_=1773687776018

Sorry for my late answers. Yes, yes it fixes it. Thank you

Hello,
Is a solution has been found because I'm experiencing the same issue.
Video => https://www.loom.com/share/a526c2ccf8ff46108d791ae6e4d862e8
Logs => https://file.thivinfo.com/Cloudron/82a18dde-001d-4c51-a69b-5ac33376e6b5 (1).log

Hello,

In Dolibarr App, I'm trying to change my profile language and receive this message:

Access refused to 172.18.0.1 by SQL or Script injection protection in main.inc.php:analyseVarsForSqlAndScriptsInjection type=0
Try to go back, fix data of your form and resubmit it. You can contact also your technical support.

Do you know how to solve this ?

Regards

Hello @james
I have an recurrent invoice created each 28th of the month and yesterday, it has not been created (first 28th after migrating to Cloudron).
So I thought the Cron task was not run.
i've added it on the Cron tab from the panel but the pdf generated by Dolibarr was owned by root user.

I've just perform the same test on my two weeks old Dolibarr installed on another host and the Link are correct.
So they are modified by the Dolibarr Cloudron app.
In both cases, the emails are sent by the same SMTP located on my cloudron

Hello,

I first thought to post on the Dolibarr forum but I think it's more generic.... but I'm not sure

OK, in Dolibarr, I can issue some payment link which llos like to https://example.com/public/payment/newpayment.php?source=invoice&ref=FA2601-0768&securekey=my-key

Once sent by email, my customers received https://example.com/public/payment/newpayment.php?source=invoice&ref=FA2601-0768&securekey=my-key

As you can see the & have been escaped to & which is of course breaking the link.

• Do you know from what this is issue is from ?

When I received the email, the "from" header is "Matomo" which is another apps I'm running on the Cloudron.

Both are sending emails through address managed by my cloudron.
Do you know why the from is Matomo on my Dolibarr ?

Regards