@d19dotca right, the 30d one seems to be 54975 size. I have increased the size of the ipset now to 262144 elements. If these things are growing more, we can look into making this size dynamic .

@girish Great!

@nebulon, after a reboot, I get a connection timeout on the localhost for which my Cloudron resides.

@d19dotca said in Blocked IP addresses in Cloudron but still able to access WordPress sites:

I know that this feature was likely originally intended to be a manual update rather than importing a giant list and works well for that, but as threats/spam become more common place, I think we’ll need Cloudron to keep up. Is it possible to prioritize improving this feature soon for us to allow thousands of IP addresses being added?

Fully agree! A strong network filter / block would be another USP

@foliovision it's in https://docs.cloudron.io/apps/#email 🙂 See the note. But to be fair, it's hard to read through all the docs in detail.

It's the same with SOGo. Use the mailbox name as username and any of the group's credentials as the password.

@TomTom4 said in Help moving Nextcloud data directory:

Can a nfs share of a zfs dataset work ?

as mentioned this has not been tested... But please let us know if it works or not. If you can post logs here it will help. For example, where is it failing in the first place. Did the volume creation work, for a start ?

I have responded from support but we have to figure out why the master Cloudron's LDAP is unreachable. Maybe network related or something else.

Fixed in master branch

@AriusII Ah thanks.

I found that "If the DNS server names end with ovh.net, ovh.ca or anycast.me, your domain name is using the OVHcloud DNS servers. " from https://help.ovhcloud.com/csm/en-dns-secure-domain-dnssec?id=kb_article_view&sysparm_article=KB0051637

@dylightful there is a bug when setting up Linode Object Storage (it's already fixed in next release). For now, you have to choose S3 compatibly Storage in the Storage provider combo box and input the values. It's the same thing internally, the Linode Object Storage is merely a convenience that fills out some fields like the endpoints.

@JLX89 Thanks for the info. I much appreciated it. You made my day 🙂

I hit the same error yesterday when trying to restore the server from backup config file (I moved my Cloudron to a new server).

For it to work I had to connect to CIFS.

Weirdly now, in the restore server, the same storage box connects fine as SSHFS for volumes (and I didn't do anything, Cloudron just restored my Volume config).

So personally, I think there is a bug somewhere in Cloudron that prevents mounting SSHFS for backup on Server restore, because mounting as SSHFS works fine otherwise.

@hakunamatata goto E-Mail => Click the Mail Domain you want => top right
da007e89-1df8-498d-96ba-6503dc59096d-image.png

Thanks for sharing the solution. Maybe there is a corner-case bug in the database migration about the directory server config.

I got the same issue.
Here are my logs:

Dec 02 06:27:28box:shell backup-snapshot/app_00ca9de5-a6cc-45b8-8914-f23a6609a145 code: null, signal: SIGKILL Dec 02 06:27:28box:taskworker Task took 32248.202 seconds Dec 02 06:27:28box:tasks setCompleted - 16719: {"result":null,"error":{"stack":"BoxError: Backuptask crashed\n at runBackupUpload (/home/yellowtent/box/src/backuptask.js:164:15)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async uploadAppSnapshot (/home/yellowtent/box/src/backuptask.js:361:5)\n at async backupAppWithTag (/home/yellowtent/box/src/backuptask.js:383:5)\n at async fullBackup (/home/yellowtent/box/src/backuptask.js:504:29)","name":"BoxError","reason":"Internal Error","details":{},"message":"Backuptask crashed"}} Dec 02 06:27:28box:tasks update 16719: {"percent":100,"result":null,"error":{"stack":"BoxError: Backuptask crashed\n at runBackupUpload (/home/yellowtent/box/src/backuptask.js:164:15)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async uploadAppSnapshot (/home/yellowtent/box/src/backuptask.js:361:5)\n at async backupAppWithTag (/home/yellowtent/box/src/backuptask.js:383:5)\n at async fullBackup (/home/yellowtent/box/src/backuptask.js:504:29)","name":"BoxError","reason":"Internal Error","details":{},"message":"Backuptask crashed"}} Backuptask crashed

And my backup settings are as follows:
307c8569-ff48-4b1f-b40e-c7539d287efb-image.png

Should I increase the memory? Let me bump it to 2 GB.
Looks like Upload Concurrency of 10 is the minimum.
I just changed from Wasabi (the price bump was too much) to iDrive e2.
Thanks for any help and pointers.

Sorry for the frustrating experience but I have to say in several years of using Cloud infrastructure, this is the first time I hear of someone providing a server on non-port 22. This is why such a special case has not made it to the docs. May I ask what VPS provider this is? We test installation over 30 providers, all use port 22 by default.

@nebulon test, as in previous testing proxying across cloudrons, and to other search engines worked just fine, and these tools sites, didn't.