@imc67 said in Too many redirects when using Cloudflare DNS proxy: @Grienauer said in Too many redirects when using Cloudflare DNS proxy: I also had this problem. After researching etc, the solution is to set the SSL/TSL to Kustom -> FULL. Wow! Thanks for this very valuable information because now I’m finally able to use Cloudflare’s WAF!! (Cloudron as well as NetCup doesn’t have a WAF to ie. geoblock wp-login.php or other login pages). Certainly no equivalent to WAF but we do have blocklists to geoblock: https://docs.cloudron.io/guides/community/blocklist-updates/

@nebulon Fully agree, it's really odd that Wix doesn't allow AAAA records in this day and age. I'll change that domain to noop for now then as recommended, but my preference is to have the logic of the location DNS propagation check change so that domains in manual status can still be successful even if only one IPv4 or one IPv6 address is set rather than both. The noop is for development after all, isn't it? As long as one of the DNS records exists, that should be seen as successful IMO, since it will work in terms of getting traffic to the site still. There shouldn't be a reason to fail that.

Glad it worked out in the end

@diamantl should not be a problem. we will get to your mail asap.

You may want to replace ssh with autossh, so that the connection is restored in case it stops working. This howto looks quite complete: https://m0agx.eu/yet-another-autossh-tutorial.html

@jdaviescoates said in Bug (?): since latest box version times are in AM/PM: with rsync backups and so backups are virtually instant as not a lot changes. But even with almost 200GB it takes about 2 minutes since the huge backup improvements lately!

Thx, I´ve look into that, it looks like the same!

https://git.cloudron.io/platform/box/-/commit/4992e284fbbe75652f195bfbc657c9a6b911b84d disables the potential squashing and wrapping for next release

Update: cloudron-support --troubleshoot returns: [WARN] netplan configuration is empty. this might be OK depending on your networking setup [FAIL] DNS is not resolving Further, /etc/netplan/ is empty. How do I generate the correct .yaml file to include there? Final Update: I was able to crate a netplan .yaml file by following these instructions.

Things often resolve AFTER posting. Weird.

Since porkbun returns an 400 error, I might guess something is wrong with the API call we do. Sadly https://porkbun.com/api/json/v3/documentation is not very detailed here, nor is the error message itself. Possibly the API requires something else for the naked domain, since the subdomains work apparently fine then. But also I can't find anything mentioned in the docs Can you check if this might be a record conflict error which just reports as 400? Like do A records for that already exist?

That answers my question. Thank you very much

@Algaweb are you proxying via Cloudflare or is there some application firewall or something like that? I have seen cases where Cloudflare throws a captcha screen which trips apps doing OIDC requests.

Thanks, @nebulon—this worked!

Switched to tarball, and it made a huge difference!

You can test on the User agent string. See https://docs.cloudron.io/apps/lamp/#health-check for an example

I was about to write a long time ago that the parameter for resetting SSH has changed: sudo systemctl restart ssh.socket

The multi-part copy was just hanging. If someone hits the same issue, you can just apply this one liner https://git.cloudron.io/platform/box/-/commit/b4d58f0609b1c252fa44799eccbbd9c691c7c2ac . The file is /home/yellowtent/box/src/storage/s3.js

@David-0 said in Use Cloudron Mailserver but have different Webhosting?: Would it be possible to use Cloudron as a mail server for mail@new.com while the domain new.com (or even subdomain.new.com) is hosted somewhere else? yes, the DNS records for a mail server (MX record) and webhosting (A records) are entirely different. It's totally normal and safe to host web and mail of the same domain on totally different systems.

You know better, so anyway the problem is resolved in the end and that didn't take long, so many thanks! have a great week-end ahead