@girish thanks for the explanation! Yeah the change happened ~14 hours ago and the TTL was set to 24 hours I reckon. I'll just wait until tomorrow to continue My plan would have been to lower the TTL a few days prior to the A record, so the caches would invalidate sooner.

Thank you. We use postmark as well. I am able to get in and everything is working. Thanks for your help.

Can just pass --redo to the setup script.

@Shaun-Snapp said in Add an A record manually for the domain: "Add an A record manually for www.abc.com to this Cloudron's public IP" I purchased the domain around 1/2 hour before trying to change an app to that domain. This is the error I received when the app failed to propagate. That message is saying that you have to add the A record manually in your domain provider (not in Cloudron). Cloudron cannot add/remove DNS entries for the domain because it's "manual" mode and thus has no programmatic access to your DNS. The place where you purchased your domain most likely has a Domain/DNS control panel where you can add/remove DNS entries.

@BrutalBirdie Thanks, it worked for me.

Yes, see the instructions at https://docs.cloudron.io/troubleshooting/#expired-domain . If that's too technical, please feel free to mail us at support@cloudron.io and we can help switch it.

@AartJansen Ah ok, looks like a limitation of the domain host. You can also just create entries for each (sub)domain you use. If you have an app at foo.domain.com, create an AAAA record for that subdomain. Repeat for every app. You should also switch to "manual" instead of "wildcard" DNS provider for this. It will remind you to setup A/AAAA records manually when you install an app.

At the bottom of the user edit dialog there is a section for this. If the user has 2fa enabled it would look like this: [image: 1677704070010-ba92d23e-ddaa-4850-bc1b-8078da14c862-image.png]

@girish ok, sounds good to me.

Ignore me. This was an issue with PowerShell apparently. If run from linux it works fine. Thanks again

@girish Oh great, that seems good then, happy to test it when it's available !

The report is quite abstract We need more information on your setup here. Routers having trouble connecting to itself is called "hairpin nat" or "hairpinning" or "loopback nat" . Is that your situation here? Does your router support it or not?

I have given these stable IPs now - https://git.cloudron.io/cloudron/box/-/commit/582994b9d646989b42e27dde1ae0c27bbb964834

@Kubernetes that's correct.

I assigned the subscription accordingly now.

@girish said in Update to version 7.3.6 failed: systemctl kill cloudron-updater This solved it ! Thank you !

@zion please always provide context. As a reader I have to much space to interpret. Do you mean: private Cloudron Cloudron.io account A Cloudron App ?

See this - https://docs.cloudron.io/email/#ptr-record

@macone see https://docs.cloudron.io/email/#firewall