Our docs currently use the default settings for https://squidfunk.github.io/mkdocs-material/setup/setting-up-site-search/ and its only okish in my perspective. Unfortunately we can't do much about the duplicates unless we would be using some other search provider.

Oh, wow, that password restriction is what I need, thank you! And, yes, the download should be public, that is sort of the idea.

@therealwebmaster Email -> Domain -> Status . You can click on each of the records there and it will tell you what you should setup.

image.png

As @robi said, need more context here. What are you trying to do? Which app is this?

For namecheap, look at their docs - https://www.namecheap.com/support/knowledgebase/article.aspx/434/2237/how-do-i-set-up-host-records-for-a-domain/

Wildcard - In wildcard, you setup subdomains to point to the server IP. So, when you install an app or change it's location, Cloudron won't remind you to point the DNS to the server IP.

Manual - When installing an app or changing it's location, Cloudron will remind you to point the DNS to the server IP.

Why prefer one over the other?

Wildcard is one time setup. Manual is something you have to do on each app install. People also sometimes ignore the "instructions" it shows to adjust the DNS and click Install.

Depending on your DNS provider, DNS propagation can take long. So, let's say if it takes 15 mins or something, then when installing the app, Cloudron will be unable to get certs. This can lead to a bad UX.

@girish , thank you!

I don't know to be honest... I would rather put it in the client<->server protocol as well, especially since it's not something I would like to expose to everyone. Guess it's because of the mixed model Element took - they are targeting at wide communities as well as closed groups, which is kind of hard to mix.

Anyway, from what I remember (and I might be wrong) I've seen something at NextCloud as well, so placing it at the app level feels right.
The only reason why I would consider placing in a general location - it's to ease implementation, as it doesn't seem to be a very often used feature. And for it to work, I'm perfectly fine to go the console or whenever, just to make it work.

No harm - just a bit of trash - if it will remain after the app removed either.

@girish Thank you!

Hooray! Thank you, @girish ! 🙂

@q__nt_n The VPS blocks port outbound 25. You have to reach out to contabo again and tell them that you can't connect with the above command.

@hiramfromthechi thanks, I replied. Looks like MySQL is down.

@Mad_Mattho The deskop version while not supported should work. I think the issue here is something else though.

I think the issue is that the mount is mounted with some strange permissions. Did you use gnome to mount the disk? I think gnome mounts the external disk as the ubuntu user you logged in as. This would prevent the yellowtent user (that cloudron runs as) from accessing that mountpoint.

So, can you please try this:

Unmount the disk in gome Mount the disk in the Backups view as an ext4 disk . You can use blkid or lsblk to get the uuid of the disk . Then, /dev/disk/by-uuid/<uuid> is the Disk path.

@jonslab did you find what it was?

@girish thanks for pointing out to code.

As always:
In vino veritas - and in Source-Code

The collabora app image is fairly large due to all the language support packages. So far we haven't found a way to make those dynamically selectable.

Also it appears you have a lot of data for the system itself, possibly you have some old leftover backups in /var/backups which could be purged, if you have configured a proper backup storage?

I see. Thanks for the update.

@roofboard said in unable to recieve mail sent to admin@cloudron.local:

In wordpress for example - to change an email address you must click on a confirmation email

cloudron.local is just an example/template as @privsec pointed out. You should not use the .local , it is not a publicly routable domain. See https://en.wikipedia.org/wiki/.local

Sometimes it's browser cache related as well, so make sure to use Shift-reload after major changes like this.

can you validate with nginx as the proxy instead?

That's what I call an answer 🙂
Thank you very much. Very helpful and my question is answered.