Cloudron Forum

Mm, ok thanks, but I think we need more information to debug. Hopefully, it doesn't happen again!

Looks like there is some DNS issue on your system. Can you run the following via SSH:

host -t A api.cloudflare.com

Also maybe

cloudron-support --troubleshoot

Disabling Cloudflare seemed to work. Thanks.

@salmonetc said in Changing DNS provider and email with minimal downtime.:

I started trying to "add" the domain. However, I get the following error: Zone not found: 200 {"result":[],"result_info":{"page":1,"per_page":20,"total_pages":0,"count":0,"total_count":0},"success":true,"errors":[],"messages":[]}

Have you added domain.com into cloudflare ? When you create a token also make sure that you add the domain in the Zone Resources list. See https://docs.cloudron.io/domains/#cloudflare-dns

RESOLVED:
It's likely that cloudflare was having some internal issue, but upon checking https://www.cloudflarestatus.com/ I was left more confused is there was any incident on their end in my region. It's buried under scheduled maintanaces and other stuff.

I still not sure if this was the correct resolution, but it started working after executing these steps.

sudo apt-get install -y systemd sudo nano /etc/systemd/resolved.conf

Added the DNS of Cloudflare and google

# This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it under the # terms of the GNU Lesser General Public License as published by the Free # Software Foundation; either version 2.1 of the License, or (at your option) # any later version. # # Entries in this file show the compile time defaults. Local configuration # should be created by either modifying this file, or by creating "drop-ins" in # the resolved.conf.d/ subdirectory. The latter is generally recommended. # Defaults can be restored by simply deleting this file and all drop-ins. # # Use 'systemd-analyze cat-config systemd/resolved.conf' to display the full config. # # See resolved.conf(5) for details. [Resolve] # Some examples of DNS servers which may be used for DNS= and FallbackDNS=: # Cloudflare: 1.1.1.1 #cloudflare-dns.com 1.0.0.1#cloudflare-dns.com 2606:4700:4700::1111 #cloudflare-d># Google: 8.8.8.8 #dns.google 8.8.4.4 #dns.google 2001:4860:4860::8888 #dns.google 2001:4860:4860::8> # Quad9: 9.9.9.9#dns.quad9.net 149.112.112.112 #dns.quad9.net 2620:fe::fe #dns.quad9.net 2620:fe::> DNS=1.1.1.1 8.8.8.8 sudo systemd-resolve --flush-caches # didn't work systemd-resolve --status # wasn't even running. So maybe the config change was irrelevant

Reboot and started working... and I am not sure how this is possible...

Anyway that for the help. This issue was plaguing me for a few days.

@d43m0n1k_sek yes, let us know

@girish yes, I meant this configuration option.

@girish yes it makes total sense, I thought there would be a way like with portainer where it just tells you ip:port but i get this is a bit more complex.
I got it to work with @murgero tip and an nginx reverseproxy.
Thank you both

LDAP uses a custom port and won't be compatible with Cloudflare. Cloudflare only proxies HTTP. OIDC should be compatible with Cloudflare though .

@joseph Thank you and yes, did all those, and was in communication with tech support. The issue is actually mysteriously resolved and I'm just trying to figure out what happened so I can share that in this thread and hopefully avoid repeating this issue in the future.

@TheMoodBoardz YW dude 😉

Right, in the Cloudflare Token UI, you can actually create readonly tokens.

image.png

@taowang note that your IP is actually leaked. If you follow the MX record of your domain, you will find your server IP in the DNS. I think this is what the Cloudflare doc is trying to tell you.

@JOduMonT an email server (without email relays) requires a public IP. There is no way around this. Even if you add a second IP, the second IP will be exposed and one can always access your Cloudron dashboard via that IP address. Just have to put an entry in /etc/hosts on my laptop and point that floating IP to my.domain.com and that's it.

I guess you are looking for a way to "sandbox" mail server to a specific IP somehow. We don't have a way to do this in Cloudron. I can move this to Feature Requests.

But also, it might be easier to just create another VM and run mail on the other VM? Security wise , this is the easiest and cleanest instead of writing a lot of code to make sure mail server and dashboard despite being on the same server don't step on each other (networking wise).

@dreamingofadmin I think first step is to get access to your dashboard.

In Cloudflare, do you have an entry for my.domain.com to your server IP (DNS A record) ? If not, add this manually. Wait a bit. Access https://my.domain.com . If it's asking to accept self signed certs, accept them. Once in dashboard, Domains -> Sync DNS . This will add all the DNS entries. Then, Domains -> Renew all certs.

Please let us know what is failing and where.

I want my users to OIDC via Cloudron to Cloudflares App Launcher where I can put all avialiable softwares some are from cloudron others are just SAAS (cloudflare can do SAML for SAAS) Screenshot 2024-04-11 at 19.57.11.png Cloudron => Cloudflare Launcher => AWS

@micmc yes, already implemented the crash fix -https://git.cloudron.io/cloudron/box/-/commit/d862f1f5b4f10b5852aed958ecc4ce42709103f7 . CF was returning an invalid response that our code was not prepared for.

I didn't uncover the cause, but I believe it was related to the VM running out of disk space. I wound up reinstalling.

I let a large upload job run unattended and wound up completely filling the drive on the VM running Cloudron. I then cleared about 100 GB, rebooted for good measure, resized the partition using parted, expanded the filesystem, rebooted again, and let it run normally for a few days. That's when I noticed I couldn't install any new apps. I suspect that either the partition / filesystem resize or the disk being full broke something internally.

In hindsight I wish I had taken the time to dig into the logs a little more and see what was happening. But this is likely a direct result of my unusual environment fault.

Hi, I just wanted to follow up on this. We found the relating issue in this case which resulted in several different problems. In that case, it was bug in a firmware update on a firewall and not related to Cloudron and can be marked as resolved. Thank you anyway for your help.

This is fixed now.

The original issue is that the zone is added in Cloudflare but the nameservers of the domain are not set to Cloudflare. This makes Cloudflare return name_servers as empty in the response which makes our code crash.