Cloudron Forum

@girish yes, that’s a much better idea. Essentially the ability to “swap” app instances, or in other words the ability to easily promote from staging app instance to production app instance on the same server. That’d be ideal. 🙂

Thanks for the reply, @girish.

Doing a

host -t NS

lead me to find that the NS records were not added in DigitalOcean.
Adding them in fixed the problem.

@davisdre The feature is available. Linode DNS is only not available in the initial Cloudron setup screen. This is only because user's were complaining nothing is happening for 15 minutes when they use Linode DNS.

You can later go to Domains view and change it from wildcard to Linode DNS.

2c612232-f588-48cc-9383-45bc9d82ef8e-image.png

I will put a note in the docs.

@necrevistonnezr said in Best domain provider for Cloudron for a server with non-static IP?:

Namecheap offers dynamic DNS update but requires an API key

For the DynDNS, Namecheap provide a password by domain
b4f8894b-346e-4204-a837-91ddbecf18ce-image.png

But yes Cloudron use the API

maybe you could run https://github.com/linuxserver/docker-ddclient

I am very interested in this. Hope we can have domain aliases very soon for applications that support it, like WP or Nextcloud.

Please!!!

I created a new topic for reset of the conversation at https://forum.cloudron.io/topic/6191/wp-alias-domains

Thanks for the thorough reply @girish , I've updated my DNS accordingly and the certificates renewed! I'll figure something out with the Github Pages (or self host on Cloudron!)

@jodumont from experience I know MX doesn’t work because the mailserver doesn’t respond to IPv6. That way we’ve lost some mails before we discovered that.

@girish WOrked like a charm, thanks!

@girish As far as I know, it's correct - unless DKIM has the IP included, since that did change during the migration. Unfortunately, the Email section of Cloudron wasn't properly giving the needed information - previously it was saying DKIM was incorrect, but the display just said something like "expected null to equal null". DKIM isn't showing in the Email status page at all with the workaround I added here.

I'll put that in as a separate issue, though, once the update comes out and I see the proper message.

Also, note that changing the nameserver sometimes takes a bit of time. So, you might have to wait a bit between step 2 and step 3.

@PRajShar To clarify what this error is trying to say: Let's assume that you have an existing website app (i.e external to Cloudron) on app.domain.com. Now, you go to Cloudron and try to install an app in the domain app.domain.com. Cloudron will detect that the DNS already has an entry for this and fail with the above error. To fix this, go to your DNS provider and remove the app.domain.com entry. Then in Cloudron, click the Repair (wrench icon) and it should work.

Alternately, just use another subdomain app2.domain.com or something.

Done, added notification for the next release.

@murgero Thanks for reporting, this was indeed a regression. Fixed now for the next release.

Indeed, missed that. Just making a blog post for 4.1 release which will include it.

I tried to reply via your support email already. The cert on your domain looks valid to me, so please clear your history and cache locally for that domain first.

This is awesome!!! Thanks @nebulon

From what you wrote, are you running the server behind your home server in a NAT by any chance?

Yes indeed.

@uiharu Does host cloudflare.com 127.0.0.1 work?

I'll update later

Had this issue on support couple of times already: https://git.cloudron.io/cloudron/box/issues/610

Oh I pasted the wrong link apparently, fixed it now.