@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 But yes Cloudron use the API maybe you could run https://github.com/linuxserver/docker-ddclient

@girish said in Multi Domain for the same app such as Nextcloud: Indeed, I replied there - https://forum.cloudron.io/topic/2202/multi-domain-for-the-same-app-such-as-nextcloud You mean here: https://forum.cloudron.io/post/6315

@will said in domain alias (not redirect): @zedomingues Have you considered other ways to achieve this goal? How would you do this ? Personally I would try to add a new nginx config in /etc/nginx/applications/ which contain server_name other.domain.tld proxy_pass http://127.0.0.1:35611; but the proxy_pass port seams to be non static. Another way, I would two time the apps and pointing them to the same data directory

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 Currently, Cloudron does not support IPv6 and requires an IPv4. You can, of course, configure your server to have IPv6 address additionally and configure DNS AAAA records manually and that should work. Goes without saying, we want to add IPv6 support at some point (I know it's 2020!! )

@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.

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.

@uiharu Ah, thanks!

@TheNils For new domains, the NS record sometimes takes to propagate. That error message means that it's not propagated to the Cloudron server yet. You can try this: SSH into the Cloudron host -t NS mydomaine.net (This should not display NXDOMAIN) If the above works, it should work on Cloudron as well. If not, can try sudo systemctl restart unbound and then try adding the domain again? We will improve the error message to be more descriptive (https://git.cloudron.io/cloudron/box/issues/548).

It works. Thanks.