Cloudron Forum

@girish said in Cloudron 9.0 (beta) bug reports:

which service or set up specifically?

It seems the issue isn’t with my local provider after all. As an experiment, I set up Garage on a server in my local network and configured it as an s3-v4–compatible provider for backups.

I adjusted the Memory Limit and Upload Part Size settings, then started a backup task. After that, I once again noticed in the logs that each part was 10 MB instead of 512 MB, as specified in the configuration. Additionally, I wasn’t able to set a custom S3 Region.
After saving the configuration, the region kept reverting to us-east-1, so I had to configure Garage to use that region identifier instead.

2025-11-11T14:57:13.843Z box:taskworker Starting task 2171. Logs are at /home/yellowtent/platformdata/logs/tasks/2171.log
2025-11-11T14:57:13.865Z box:taskworker Running task of type backup
2025-11-11T14:57:13.893Z box:tasks updating task 2171 with: {"percent":5.761904761904762,"message":"Backing up ***.***.ru (1/18). Waiting for lock"}
2025-11-11T14:57:13.899Z box:locks write: current locks: {"full_backup_task_a1cb8769-ccfb-4107-b574-ab4c7afef2b6":null,"app_backup_07fd2189-9378-4a35-b18d-5cef77461fb1":"2171"}
2025-11-11T14:57:13.899Z box:locks acquire: app_backup_07fd2189-9378-4a35-b18d-5cef77461fb1
2025-11-11T14:57:13.900Z box:tasks updating task 2171 with: {"percent":5.761904761904762,"message":"Snapshotting app ***.***.ru"}
2025-11-11T14:57:13.901Z box:services backupAddons
2025-11-11T14:57:13.901Z box:services backupAddons: backing up ["localstorage","postgresql","sendmail","oidc","redis"]
2025-11-11T14:57:13.902Z box:services Backing up postgresql
2025-11-11T14:57:14.139Z box:services pipeRequestToFile: connected with status code 200
2025-11-11T14:57:17.617Z box:services Backing up redis
2025-11-11T14:57:17.672Z box:services pipeRequestToFile: connected with status code 200
2025-11-11T14:57:17.682Z box:backuptask snapshotApp: ***.***.ru took 3.782 seconds
2025-11-11T14:57:17.697Z box:tasks updating task 2171 with: {"percent":5.761904761904762,"message":"Uploading app snapshot ***.***.ru"}
2025-11-11T14:57:17.697Z box:backuptask runBackupUpload: adjusting heap size to 2816M
2025-11-11T14:57:17.697Z box:shell backuptask: /usr/bin/sudo --non-interactive -E --close-from=4 /home/yellowtent/box/src/scripts/backupupload.js snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz a1cb8769-ccfb-4107-b574-ab4c7afef2b6 {"localRoot":"/home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1","layout":[{"localDir":"/mnt/md0/IApps/photos","remoteDir":"data"}]}
2025-11-11T14:57:18.216Z box:backupupload Backing up {"localRoot":"/home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1","layout":[{"localDir":"/mnt/md0/IApps/photos","remoteDir":"data"}]} to snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz
2025-11-11T14:57:18.218Z box:backuptask upload: path snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz site a1cb8769-ccfb-4107-b574-ab4c7afef2b6 dataLayout {"localRoot":"/home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1","layout":[{"localDir":"/mnt/md0/IApps/photos","remoteDir":"data"}]}
2025-11-11T14:57:18.357Z box:backuptask checkPreconditions: mount point status is {"state":"active"}
2025-11-11T14:57:18.357Z box:backuptask checkPreconditions: getting disk usage of /home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1
2025-11-11T14:57:18.357Z box:shell backuptask: du --dereference-args --summarize --block-size=1 --exclude=*.lock --exclude=dovecot.list.index.log.* /home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1
2025-11-11T14:57:18.365Z box:backuptask checkPreconditions: getting disk usage of /mnt/md0/IApps/photos
2025-11-11T14:57:18.365Z box:shell backuptask: du --dereference-args --summarize --block-size=1 --exclude=*.lock --exclude=dovecot.list.index.log.* /mnt/md0/IApps/photos
2025-11-11T14:57:19.311Z box:backuptask checkPreconditions: total required=125243674624 available=Infinity
2025-11-11T14:57:19.317Z box:backupformat/tgz upload: uploading to site a1cb8769-ccfb-4107-b574-ab4c7afef2b6 path snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz (encrypted: false) dataLayout {"localRoot":"/home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1","layout":[{"localDir":"/mnt/md0/IApps/photos","remoteDir":"data"}]}
2025-11-11T14:57:19.318Z box:tasks updating task 2171 with: {"percent":5.761904761904762,"message":"Uploading backup snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz (***.***.ru)"}
2025-11-11T14:57:19.323Z box:backupformat/tgz tarPack: processing /home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1
2025-11-11T14:57:19.330Z box:backupformat/tgz addToPack: added ./config.json file
2025-11-11T14:57:19.385Z box:backupformat/tgz addToPack: added ./dump.rdb file
2025-11-11T14:57:19.396Z box:backupformat/tgz addToPack: added ./fsmetadata.json file
2025-11-11T14:57:20.874Z box:storage/s3 Upload progress: {"loaded":10485760,"part":1,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz","Bucket":"lvcl-backup"}
2025-11-11T14:57:22.826Z box:storage/s3 Upload progress: {"loaded":20971520,"part":2,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz","Bucket":"lvcl-backup"}
2025-11-11T14:57:24.909Z box:storage/s3 Upload progress: {"loaded":31457280,"part":3,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz","Bucket":"lvcl-backup"}
2025-11-11T14:57:26.524Z box:storage/s3 Upload progress: {"loaded":41943040,"part":4,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz","Bucket":"lvcl-backup"}
2025-11-11T14:57:27.785Z box:storage/s3 Upload progress: {"loaded":52428800,"part":5,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz","Bucket":"lvcl-backup"}
2025-11-11T14:57:29.329Z box:tasks updating task 2171 with: {"percent":5.761904761904762,"message":"Uploading backup 59M@6MBps (***.***.ru)"}
2025-11-11T14:57:29.652Z box:storage/s3 Upload progress: {"loaded":62914560,"part":6,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz","Bucket":"lvcl-backup"}
2025-11-11T14:57:31.626Z box:storage/s3 Upload progress: {"loaded":73400320,"part":7,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz","Bucket":"lvcl-backup"}
2025-11-11T14:57:33.614Z box:storage/s3 Upload progress: {"loaded":83886080,"part":8,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz","Bucket":"lvcl-backup"}
2025-11-11T14:57:35.396Z box:storage/s3 Upload progress: {"loaded":94371840,"part":9,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz","Bucket":"lvcl-backup"}

@mononym said in Is it possible/safe to install Client Push App ?:

does the setup work when running sudo -u www-data php -f /app/code/occ notify_push:setup

I don’t think this is possible within Cloudron. For push to work, you need to create a daemon at /etc/systemd/system/notify_push.service and make some changes to Apache or Nginx.
The occ notify_push:setup command assumes that all of this is done on the same server where Nextcloud itself is installed.
However, based on the information from https://github.com/nextcloud/notify_push, it seems that it might be possible to set it up on a separate server — though exactly how to do that is another question.

@girish said in Cloudron 9.0 (beta) bug reports:

Yes please, if that's possible

I’ve sent the details from my email address vlishchenko****@gmail.com

@girish said in Cloudron 9.0 (beta) bug reports:

which service or set up specifically

It’s a local provider for me, and there’s no specific configuration for it in Cloudron.
For convenience, I can create a bucket and send you the access details by email so that you can try to reproduce the issue.
However, if the problem lies in how this provider implements S3 compatibility, I don’t think it’s worth spending too much time on it.
Initially, I thought the issue was related to the generic S3 configuration itself.

@girish said in Cloudron 9.0 (beta) bug reports:

Which storage provider are you using?

I’m trying to use an S3 API Compatible (v4) provider.

It looks like the multipart upload settings for S3-compatible storage aren’t working as expected.
Last night, I enabled a backup of around 150 GB of data in TGZ format. In the configuration, I set the part size to 256 MB.
This morning, when checking the logs, I found that the upload had stopped at 100 GB because the 10,000-part limit was reached. Based on simple math, that would only make sense if each part were 10 MB — which is Cloudron’s default minimum part size.

I double-checked the settings and confirmed that my 256 MB value had been saved correctly. Then I set it to the maximum (1 GB), restarted the server, and manually triggered another backup. Watching the logs again, I noticed the same behavior — a new part was created every 10 MB and uploaded to S3.

Has anyone else run into this issue?

2025-11-09T07:23:19.605Z box:taskworker Starting task 2146. Logs are at /home/yellowtent/platformdata/logs/tasks/2146.log
2025-11-09T07:23:19.624Z box:taskworker Running task of type backup
2025-11-09T07:23:19.644Z box:tasks updating task 2146 with: {"percent":5.761904761904762,"message":"Backing up ***.***.ru (1/18). Waiting for lock"}
2025-11-09T07:23:19.656Z box:locks write: current locks: {"full_backup_task_10b1282f-f0e2-400d-a074-b183f08c16f5":null,"app_backup_07fd2189-9378-4a35-b18d-5cef77461fb1":"2146"}
2025-11-09T07:23:19.656Z box:locks acquire: app_backup_07fd2189-9378-4a35-b18d-5cef77461fb1
2025-11-09T07:23:19.657Z box:tasks updating task 2146 with: {"percent":5.761904761904762,"message":"Snapshotting app ***.***.ru"}
2025-11-09T07:23:19.660Z box:services backupAddons
2025-11-09T07:23:19.660Z box:services backupAddons: backing up ["localstorage","postgresql","sendmail","oidc","redis"]
2025-11-09T07:23:19.661Z box:services Backing up postgresql
2025-11-09T07:23:19.878Z box:services pipeRequestToFile: connected with status code 200
2025-11-09T07:23:23.447Z box:services Backing up redis
2025-11-09T07:23:23.514Z box:services pipeRequestToFile: connected with status code 200
2025-11-09T07:23:23.528Z box:backuptask snapshotApp: ***.***.ru took 3.871 seconds
2025-11-09T07:23:23.564Z box:tasks updating task 2146 with: {"percent":5.761904761904762,"message":"Uploading app snapshot ***.***.ru"}
2025-11-09T07:23:23.564Z box:backuptask runBackupUpload: adjusting heap size to 3840M
2025-11-09T07:23:23.565Z box:shell backuptask: /usr/bin/sudo --non-interactive -E --close-from=4 /home/yellowtent/box/src/scripts/backupupload.js snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc 10b1282f-f0e2-400d-a074-b183f08c16f5 {"localRoot":"/home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1","layout":[{"localDir":"/mnt/md0/IApps/photos","remoteDir":"data"}]}
2025-11-09T07:23:24.304Z box:backupupload Backing up {"localRoot":"/home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1","layout":[{"localDir":"/mnt/md0/IApps/photos","remoteDir":"data"}]} to snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc
2025-11-09T07:23:24.306Z box:backuptask upload: path snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc site 10b1282f-f0e2-400d-a074-b183f08c16f5 dataLayout {"localRoot":"/home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1","layout":[{"localDir":"/mnt/md0/IApps/photos","remoteDir":"data"}]}
2025-11-09T07:23:24.524Z box:backuptask checkPreconditions: mount point status is {"state":"active"}
2025-11-09T07:23:24.524Z box:backuptask checkPreconditions: getting disk usage of /home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1
2025-11-09T07:23:24.524Z box:shell backuptask: du --dereference-args --summarize --block-size=1 --exclude=*.lock --exclude=dovecot.list.index.log.* /home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1
2025-11-09T07:23:24.531Z box:backuptask checkPreconditions: getting disk usage of /mnt/md0/IApps/photos
2025-11-09T07:23:24.531Z box:shell backuptask: du --dereference-args --summarize --block-size=1 --exclude=*.lock --exclude=dovecot.list.index.log.* /mnt/md0/IApps/photos
2025-11-09T07:23:29.436Z box:backuptask checkPreconditions: total required=125109989376 available=Infinity
2025-11-09T07:23:29.448Z box:backupformat/tgz upload: uploading to site 10b1282f-f0e2-400d-a074-b183f08c16f5 path snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc (encrypted: true) dataLayout {"localRoot":"/home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1","layout":[{"localDir":"/mnt/md0/IApps/photos","remoteDir":"data"}]}
2025-11-09T07:23:29.450Z box:tasks updating task 2146 with: {"percent":5.761904761904762,"message":"Uploading backup snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc (***.***.ru)"}
2025-11-09T07:23:29.457Z box:backupformat/tgz tarPack: processing /home/yellowtent/appsdata/07fd2189-9378-4a35-b18d-5cef77461fb1
2025-11-09T07:23:29.471Z box:backupformat/tgz addToPack: added ./config.json file
2025-11-09T07:23:29.528Z box:backupformat/tgz addToPack: added ./dump.rdb file
2025-11-09T07:23:29.540Z box:backupformat/tgz addToPack: added ./fsmetadata.json file
2025-11-09T07:23:32.318Z box:storage/s3 Upload progress: {"loaded":10485760,"part":1,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc","Bucket":"25fc748e-lvcl-backup"}
2025-11-09T07:23:34.405Z box:storage/s3 Upload progress: {"loaded":20971520,"part":2,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc","Bucket":"25fc748e-lvcl-backup"}
2025-11-09T07:23:37.143Z box:storage/s3 Upload progress: {"loaded":31457280,"part":3,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc","Bucket":"25fc748e-lvcl-backup"}
2025-11-09T07:23:39.234Z box:storage/s3 Upload progress: {"loaded":41943040,"part":4,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc","Bucket":"25fc748e-lvcl-backup"}
2025-11-09T07:23:39.425Z box:storage/s3 Upload progress: {"loaded":52428800,"part":5,"Key":"snapshot/app_07fd2189-9378-4a35-b18d-5cef77461fb1.tar.gz.enc","Bucket":"25fc748e-lvcl-backup"}

• Title: Termix — SSH server manager, alternative to Termius

---

• Main Page: https://github.com/Termix-SSH/Termix
• Licence: Apache License Version 2.0
• Dockerfile: Yes

---

• Summary: Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities.

---

• Alternative to: Termius

@nebulon said in Nextcloud Mail issues:

Or are you worried about something else?

Nope, not at all. Thanks again for your help and explanation.

@jdaviescoates said in Nextcloud Mail issues:

I guess it must've / might've had something to do with you moving the docker stuff around

Yeah, I think that's the case. If I didn't already have a complex setup, I might consider just reinstalling Cloudron, but for now that's not an option.
And to be honest, it doesn't make much sense to reinstall the whole system just because of a single Nextcloud app If it works for now, it works.

@nebulon said in Nextcloud Mail issues:

So all you should have to do is to configure nextcloud mail to use that port instead of 993.

Thanks @nebulon for the help!

Mail app works again after a few changes to the Nextcloud config.

First, I added these parameters to /app/data/config/config.php:

'allow_local_remote_servers' => true,

(because by default, Nextcloud doesn’t allow local hostnames or IP addresses as remote servers)

'app.mail.verify-tls-peer' => false,

(this just turns off TLS verification for IMAP/SMTP)

Then, in the Nextcloud Mail settings, I set the host to mail, IMAP SSL/TLS port to 9993, and SMTP SSL/TLS port to 2465.

After that, the app finally connected to my server!

Without these steps, nothing worked. I tried different combinations of IPs, hostnames, and even disabled SSL/TLS and STARTTLS — no luck.

The thing is, I still don’t know why my Mail app worked perfectly with the old settings for months and suddenly stopped now. And yeah, I’m a bit concerned about the security of this workaround.

@nebulon said in Nextcloud Mail issues:

Is port 993 even publicly open on your system

Yes, of course. I also can connect from a remote machine:

vladislav@MINIPC:~/git$ telnet my.***.ru 993
Trying 91.214.***.***...
Connected to my.***.ru.
Escape character is '^]'.
Connection closed by foreign host.

cloudron-support --troubleshoot

wisemetalhead@lvhome:~$ sudo cloudron-support --troubleshoot
[sudo] password for wisemetalhead: 
Vendor: AZW Product: ME mini
Linux: 6.14.0-33-generic
Ubuntu: noble 24.04
Processor: Intel(R) N150
BIOS Intel(R) N150 To Be Filled By O.E.M. CPU @ 2.8GHz x 4
RAM: 12001808KB
Disk: /dev/mmcblk0p2   48G
[OK]	node version is correct
[FAIL]	Server has an IPv6 address but api.cloudron.io is unreachable via IPv6 (ping6 -q -c 1 api.cloudron.io)
Instead of disabling IPv6 globally, you can disable it at an interface level.
	sysctl -w net.ipv6.conf.enp1s0.disable_ipv6=1
	sysctl -w net.ipv6.conf.enp2s0.disable_ipv6=1
For the above configuration to persist across reboots, you have to add below to /etc/sysctl.conf
	net.ipv6.conf.enp1s0.disable_ipv6=1
	net.ipv6.conf.enp2s0.disable_ipv6=1
wisemetalhead@lvhome:~$ sudo sysctl -w net.ipv6.conf.enp1s0.disable_ipv6=1
net.ipv6.conf.enp1s0.disable_ipv6 = 1
wisemetalhead@lvhome:~$ sudo sysctl -w net.ipv6.conf.enp2s0.disable_ipv6=1
net.ipv6.conf.enp2s0.disable_ipv6 = 1
wisemetalhead@lvhome:~$ sudo cloudron-support --troubleshoot
Vendor: AZW Product: ME mini
Linux: 6.14.0-33-generic
Ubuntu: noble 24.04
Processor: Intel(R) N150
BIOS Intel(R) N150 To Be Filled By O.E.M. CPU @ 2.8GHz x 4
RAM: 12001808KB
Disk: /dev/mmcblk0p2   48G
[OK]	node version is correct
[OK]	IPv6 is enabled in kernel. No public IPv6 address
[OK]	docker is running
[OK]	docker version is correct
[OK]	MySQL is running
[OK]	nginx is running
[OK]	dashboard cert is valid
[OK]	dashboard is reachable via loopback
[OK]	box v8.3.2 is running
[OK]	netplan is good
[OK]	DNS is resolving via systemd-resolved
[OK]	Dashboard is reachable via domain name
[WARN]	Domain ***.ru expiry check skipped because whois does not have this information
[OK]	unbound is running

@nebulon said in Nextcloud Mail issues:

telnet mail 9993

root@71780ea5-011c-4c09-886e-5f7e17e0b670:/app/code# telnet mail 9993
Trying fd00:c107:d509::2...
Connected to mail.
Escape character is '^]'.
Connection closed by foreign host.

@nebulon said in Nextcloud Mail issues:

telnet <yourpublicmaildomain> 993

root@71780ea5-011c-4c09-886e-5f7e17e0b670:/app/code# telnet my.***.ru 993
Trying 172.18.0.1...
telnet: Unable to connect to remote host: Connection timed out

@nebulon said in Nextcloud Mail issues:

there any more error or debug logs

Here’s all I could find in the logs:

2025-10-16T11:32:21Z 212.152.**.*** - - [16/Oct/2025:11:32:16 +0000] "POST /apps/mail/api/accounts HTTP/1.1" 400 104 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36"

{"reqId":"B2gTLx5mgFvdhfASC2sM","level":3,"time":"2025-10-16T10:07:35+00:00","remoteAddr":"212.152.**.***","user":"vladislav","app":"index","method":"GET","url":"/apps/mail/api/accounts/1/quota","message":"Error connecting to mail server.","userAgent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36","version":"31.0.9.1","exception":{"Exception":"Horde_Imap_Client_Exception","Message":"Error connecting to mail server.","Code":11,"Trace":[{"file":"/app/data/apps/mail/vendor/bytestream/horde-imap-client/lib/Horde/Imap/Client/Socket.php","line":375,"function":"_connect","class":"Horde_Imap_Client_Socket","type":"->"},{"file":"/app/data/apps/mail/lib/IMAP/HordeImapClient.php","line":60,"function":"_login","class":"Horde_Imap_Client_Socket","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"/app/data/apps/mail/vendor/bytestream/horde-imap-client/lib/Horde/Imap/Client/Base.php","line":853,"function":"_login","class":"OCA\\Mail\\IMAP\\HordeImapClient","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"/app/data/apps/mail/vendor/bytestream/horde-imap-client/lib/Horde/Imap/Client/Base.php","line":1404,"function":"login","class":"Horde_Imap_Client_Base","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"/app/data/apps/mail/lib/IMAP/FolderMapper.php","line":52,"function":"listMailboxes","class":"Horde_Imap_Client_Base","type":"->"},{"file":"/app/data/apps/mail/lib/Service/MailManager.php","line":594,"function":"getFolders","class":"OCA\\Mail\\IMAP\\FolderMapper","type":"->"},{"file":"/app/data/apps/mail/lib/Controller/AccountsController.php","line":470,"function":"getQuota","class":"OCA\\Mail\\Service\\MailManager","type":"->"},{"file":"/app/code/lib/private/AppFramework/Http/Dispatcher.php","line":200,"function":"getQuota","class":"OCA\\Mail\\Controller\\AccountsController","type":"->"},{"file":"/app/code/lib/private/AppFramework/Http/Dispatcher.php","line":114,"function":"executeController","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->"},{"file":"/app/code/lib/private/AppFramework/App.php","line":161,"function":"dispatch","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->"},{"file":"/app/code/lib/private/Route/Router.php","line":315,"function":"main","class":"OC\\AppFramework\\App","type":"::"},{"file":"/app/code/lib/base.php","line":1063,"function":"match","class":"OC\\Route\\Router","type":"->"},{"file":"/app/code/index.php","line":24,"function":"handleRequest","class":"OC","type":"::"}],"File":"/app/data/apps/mail/vendor/bytestream/horde-imap-client/lib/Horde/Imap/Client/Socket.php","Line":607,"message":"Error connecting to mail server.","exception":{"details":"[110] Connection timed out","logged":false,"raw_msg":"Error connecting to mail server."},"CustomMessage":"Error connecting to mail server."}}
{"reqId":"V6QGeCfvi4X7PdvxiDiE","level":3,"time":"2025-10-16T10:07:26+00:00","remoteAddr":"212.152.**.***","user":"vladislav","app":"mail","method":"GET","url":"/apps/mail/","message":"Could not load account mailboxes: IMAP error synchronizing account 1: Error connecting to mail server.","userAgent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36","version":"31.0.9.1","exception":{"Exception":"OCA\\Mail\\Exception\\ServiceException","Message":"IMAP error synchronizing account 1: Error connecting to mail server.","Code":11,"Trace":[{"file":"/app/data/apps/mail/lib/Service/MailManager.php","line":139,"function":"sync","class":"OCA\\Mail\\IMAP\\MailboxSync","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"/app/data/apps/mail/lib/Controller/PageController.php","line":154,"function":"getMailboxes","class":"OCA\\Mail\\Service\\MailManager","type":"->"},{"file":"/app/code/lib/private/AppFramework/Http/Dispatcher.php","line":200,"function":"index","class":"OCA\\Mail\\Controller\\PageController","type":"->"},{"file":"/app/code/lib/private/AppFramework/Http/Dispatcher.php","line":114,"function":"executeController","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->"},{"file":"/app/code/lib/private/AppFramework/App.php","line":161,"function":"dispatch","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->"},{"file":"/app/code/lib/private/Route/Router.php","line":315,"function":"main","class":"OC\\AppFramework\\App","type":"::"},{"file":"/app/code/lib/base.php","line":1063,"function":"match","class":"OC\\Route\\Router","type":"->"},{"file":"/app/code/index.php","line":24,"function":"handleRequest","class":"OC","type":"::"}],"File":"/app/data/apps/mail/lib/IMAP/MailboxSync.php","Line":110,"Previous":{"Exception":"Horde_Imap_Client_Exception","Message":"Error connecting to mail server.","Code":11,"Trace":[{"file":"/app/data/apps/mail/vendor/bytestream/horde-imap-client/lib/Horde/Imap/Client/Socket.php","line":375,"function":"_connect","class":"Horde_Imap_Client_Socket","type":"->"},{"file":"/app/data/apps/mail/lib/IMAP/HordeImapClient.php","line":60,"function":"_login","class":"Horde_Imap_Client_Socket","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"/app/data/apps/mail/vendor/bytestream/horde-imap-client/lib/Horde/Imap/Client/Base.php","line":853,"function":"_login","class":"OCA\\Mail\\IMAP\\HordeImapClient","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"/app/data/apps/mail/vendor/bytestream/horde-imap-client/lib/Horde/Imap/Client/Base.php","line":1404,"function":"login","class":"Horde_Imap_Client_Base","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"/app/data/apps/mail/lib/IMAP/FolderMapper.php","line":52,"function":"listMailboxes","class":"Horde_Imap_Client_Base","type":"->"},{"file":"/app/data/apps/mail/lib/IMAP/MailboxSync.php","line":107,"function":"getFolders","class":"OCA\\Mail\\IMAP\\FolderMapper","type":"->"},{"file":"/app/data/apps/mail/lib/Service/MailManager.php","line":139,"function":"sync","class":"OCA\\Mail\\IMAP\\MailboxSync","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"/app/data/apps/mail/lib/Controller/PageController.php","line":154,"function":"getMailboxes","class":"OCA\\Mail\\Service\\MailManager","type":"->"},{"file":"/app/code/lib/private/AppFramework/Http/Dispatcher.php","line":200,"function":"index","class":"OCA\\Mail\\Controller\\PageController","type":"->"},{"file":"/app/code/lib/private/AppFramework/Http/Dispatcher.php","line":114,"function":"executeController","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->"},{"file":"/app/code/lib/private/AppFramework/App.php","line":161,"function":"dispatch","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->"},{"file":"/app/code/lib/private/Route/Router.php","line":315,"function":"main","class":"OC\\AppFramework\\App","type":"::"},{"file":"/app/code/lib/base.php","line":1063,"function":"match","class":"OC\\Route\\Router","type":"->"},{"file":"/app/code/index.php","line":24,"function":"handleRequest","class":"OC","type":"::"}],"File":"/app/data/apps/mail/vendor/bytestream/horde-imap-client/lib/Horde/Imap/Client/Socket.php","Line":607},"message":"Could not load account mailboxes: IMAP error synchronizing account 1: Error connecting to mail server.","exception":{},"CustomMessage":"Could not load account mailboxes: IMAP error synchronizing account 1: Error connecting to mail server."}}

@nebulon said in Nextcloud Mail issues:

So SnappyMail or Roundcube on the same Cloudron still work fine?

Yes, Roundcube is also working just fine.

@jdaviescoates The same app on an external server connects to my IMAP without any issues. I also tried installing older versions of the Mail app on my new Nextcloud (ones that I know used to work before ).

Well… I’m out of ideas. Here’s what I’ve tried to fix this problem (from easy to hard):

• Restarted the mail service
• Turned incoming mail off and on for my domain
• Re-saved the mail domain settings (didn’t change anything, just clicked “Save”)
• Synced DNS
• Renewed certificates
• Regenerated the Mail app password
• Ran cloudron-support --recreate-containers
• Ran cloudron-support --recreate-docker

Here’s what I tried to check if IMAP is working at all:

• Connected from Thunderbird client → works
• Connected from Snappy Mail installed on the same server → works
• Connected from an external Nextcloud instance with the latest Mail app installed → works!
• Installed a new Nextcloud app on my server and tried connecting from its Mail app → doesn’t work

From what I can see in my old Nextcloud logs, IMAP errors started appearing yesterday, while I wasn’t doing anything with either Nextcloud or Cloudron.

I know that Mail app from Nextcloud isn't the best deal, but for now I'm really concerned that the IMAP connection doesn’t work just between two Docker containers.

Strange, but Nextcloud Mail suddenly stopped working:

[index] Ошибка: Error connecting to mail server.
	GET /apps/mail/api/accounts/1/quota
	на 31.173.80.134 от vladislav в 15 окт. 2025 г., 18:56:28

[mail] Ошибка: Cron mail sync failed for account 1
	на ? от -- в 15 окт. 2025 г., 19:40:48

If I connect from external apps like Thunderbird Mobile, everything works as expected. Snappy Mail app also works fine.
But when I try to log in to the mail server from Nextcloud Mail (both the latest version and 5.4.0), this error appears in the Mail log:

Oct 15 19:58:45 [NOTICE] [FF7E0883-2134-4B12-8030-062F0017AB0A] [core] connect ip=158.94.209.47 port=58086 local_ip=172.18.30.4 local_port=2587
Oct 15 19:58:45 [INFO] [FF7E0883-2134-4B12-8030-062F0017AB0A] [dns-list]
Oct 15 19:58:46 [INFO] [FF7E0883-2134-4B12-8030-062F0017AB0A] [helo.checks] helo_host: User, pass:bare_ip, rdns_match(org_dom), host_mismatch, literal_mismatch, fail:valid_hostname(no_dot), skip:dynamic(no dots)
Oct 15 19:58:46 [INFO] [FF7E0883-2134-4B12-8030-062F0017AB0A] [spf] identity=helo ip=158.94.209.47 domain="User" mfrom=<postmaster@User> result=None
Oct 15 19:58:46 [INFO] [FF7E0883-2134-4B12-8030-062F0017AB0A] [spf] scope: helo, result: None, domain: User
Oct 15 19:58:46 [INFO] [FF7E0883-2134-4B12-8030-062F0017AB0A] [limit] concurrent_count: 1, concurrent: 1/200, rate_conn: 1:60/1m, unrec_cmds: AUTH,LOGIN
Oct 15 19:58:46 [NOTICE] [FF7E0883-2134-4B12-8030-062F0017AB0A] [core] disconnect ip=158.94.209.47 rdns=NXDOMAIN helo=User relay=N early=N esmtp=Y tls=N pipe=N errors=1 txns=0 rcpts=0/0/0 msgs=0/0/0 bytes=0 lr="500 Unrecognized command" time=1.391

I’m not sure if this is somehow related to the Docker image migration, but I didn’t do anything else with Cloudron today.

@james
Fortunately, I took care of this issue almost right after installing Ubuntu, but thanks a lot for sharing another interesting approach.

@james said in Running Cloudron on eMMC – How to Reduce Writes?:

Can you please try to pull the image manually?

Thanks a lot for your help and suggestions. I was able to resolve my issue.

My Cloudron had AdGuard Home installed and connected to the router. Even though I set the server’s traffic to go through the provider’s DNS, I probably messed something up in the configuration.

Since AdGuard Home wasn’t working, there was no DNS resolution, and therefore no connection

After I temporarily changed the DNS on the router, everything started working fine. The Docker images are slowly restoring now.

@james said in Running Cloudron on eMMC – How to Reduce Writes?:

docker run --rm hello-world

Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
17eec7bbc9d7: Pull complete 
Digest: sha256:6dc565aa630927052111f823c303948cf83670a3903ffa3849f1488ab517f891
Status: Downloaded newer image for hello-world:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
    (amd64)
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
 https://hub.docker.com/

For more examples and ideas, visit:
 https://docs.docker.com/get-started/

@james said in Running Cloudron on eMMC – How to Reduce Writes?:

dig A registry.docker.com

; <<>> DiG 9.18.30-0ubuntu0.24.04.2-Ubuntu <<>> A registry.docker.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4191
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;registry.docker.com.		IN	A

;; ANSWER SECTION:
registry.docker.com.	60	IN	A	34.197.251.18
registry.docker.com.	60	IN	A	18.206.23.233
registry.docker.com.	60	IN	A	98.86.59.233
registry.docker.com.	60	IN	A	52.22.88.186
registry.docker.com.	60	IN	A	34.225.208.41
registry.docker.com.	60	IN	A	34.237.110.211
registry.docker.com.	60	IN	A	54.165.148.211
registry.docker.com.	60	IN	A	34.232.216.124

;; Query time: 60 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Wed Oct 15 08:52:27 UTC 2025
;; MSG SIZE  rcvd: 176