@webvsnet Ah alright 🙂 Remember that when you upgrade Cloudron, you will have to get back to CLI 5.4.0

@girish
opps, my last post was never published…

anycast.me is their geoloaction-aware DNS system.

I opened a ticket with them and after manual pushing DNS updates after disabling DNSSEC (temporarily), it worked and propagated the right entries.

there are still some false positves on spamhouse, but it's working.

Thanks for your support.

@bozza-man We haven't gotten an email from the email that you have registered in the forum with. Can you maybe send again?

@letecho Did you sort this out? We sent you a mail saying we cannot connect but got no response.

Are you also using the domain outside of Cloudron? I am surprised you hit any limit at all, Cloudron API usage is quite low.

@Reveller said in Rudimentary question about how domains work in Cloudron:

@jdaviescoates Thanks. Overthinking is one of my unfortunate specialties. But the docs are very clear that the apps are installed on subdomains - https://docs.cloudron.io/installation/

I see what you mean, I think @staff ought to update this part of the docs which give the wrong impression:

Domain Setup

Provide a domain like example.com. The way Cloudron works is that the dashboard gets installed at my.example.com, and apps are installed under subdomains that you specify like git.example.com, chat.example.com, and so on.

@Reveller said in Rudimentary question about how domains work in Cloudron:

But by looking closer at the demo, I can see how the location can be changed (app's location tab) - so I assume that's how it's done.

Yes, you can always change location there, but you can also just directly install on the root domain in the first instance too.

@Reveller I replaced "many" to "some" 😄

By far the most crucial one is backup/restore related workflows since the database is not included part of the backup of this one app.

So here’s the thing, my router has dual WAN.

Recently, my primary has not been very stable and would failover to my secondary.
I could see that Cloudron has picked up the new public IP Address but hasn’t updated the DNS records for the apps.

Thanks, every 10 mins would be a lot better than 5 mins past the hour.

I created a new SMTP user and that worked like a charm. Not sure why adding an access key for the existing cloudron SMTP user doesn't work.
Either way, important thing is that it is working now.
You may mark this thread as resolved. Thanks!

Fixed for next release with https://git.cloudron.io/cloudron/box/-/commit/93d4271bce299c1d3aba9036f8d15805adaa1f2e

Have you read through https://docs.cloudron.io/networking/#private-dns already? Seems like this outlines your situation.

@girish I think the base installation should have option disabled by default, and then the option to enable it...

@girish said in Best practice for migrating apps from one Cloudron to another?:

Ah! I misread your issue then.

Yeah, I think you missed or misread this bit:

@jdaviescoates said in Best practice for migrating apps from one Cloudron to another?:

But the odd thing is that in the App Email settings on the old server it has always been and is still ghost.app

I can only guess that it was working there because I had set-up the required email addresses that are set in the portal settings in Ghost:

41999d97-12f0-41e3-b47b-b95114bcdca2-image.png

I guess when Cloudron couldn't find that mailbox on the new server it tried to just send as 'ghost.app' instead? 🤷

But yeah, as you say, would be good to somehow remind users this might need to be done too, like you say:

@girish said in Best practice for migrating apps from one Cloudron to another?:

Mmmm... I wonder how the user can be reminded of this. I think for a start having this in the doc page as a checklist (which is what this thread is about!) will help.

Agreed 🙂

But maybe whenever importing an app a pop-up could appear saying something like "you might also need to recreate mailboxes on this domain" or something? 🤷

I have added a workaround in the next release to delete 0 length files on startup.

@girish no it was just on ip:port so i installed today nginx proxy and it worked through that with hrms.domainname.com wild card certificate

@cpa it's being tracked https://git.cloudron.io/cloudron/box/-/issues/822 . Note the issue tracker is internal, so you cannot see it.

Guess we have to improve the slider. I think entering exact values is too precise which might mislead people into thinking this important...

Suddenly, after 1-2 hours, everything started working by itself. My hosting provider confirmed that there is no IP blocking on their end. I'll email you if the problem occurs again.

@necrevistonnezr said in How to remove all mail folder?:

Another thing is that - as usual with Apple - there’s no way to adjust or reset such suggestions. Even without the „all mail“ folder, it was hit & miss. And why would a folder that has been added later override all previously learned suggestions? It’s just stupid.
(BTW, the same goes for login/password suggestions in Safari, even when using Bitwarden - for my Cloudron site, Safari suggests 30 login / password combinations that are out of date. No way to reset that).

I hear you. Apple always does everything the apple way. In this case I think its not really related to "learning". I think its more of a scan and match system. You receive a mail and the mail app is looking up for the folder containing the most mails with the given sender. So in case of Amazon apps there are like two options: The Amazon folder and the all mail folder. As I may have missed a few mails in the past and probably just moved them into the archive, there may be a slightly higher amount of mails in the all mail folder. Also I tend to use folders like "cancellations" or "payments" which may also contain Amazon mails.

The same goes for office mails. The same sender (f.g. boss@work) may end up in folder "Project A" and Project "B", according to its content and topic. But both mails will be found in "all mail". So no matter what, the all mail folder will - due to its nature - always have the biggest and max. possible amount of mails from every given sender and therefor get the highest "rank" from Apple Mail.

At least thats what I assume.