Cloudron Forum

@joseph Okay, it's solved. It works a bit differently than with Infomaniak, since Infomaniak doesn't allow you to modify outbound firewall rules yourself — for example, you have to open a support ticket to request outbound access to port 25. With Hetzner, I just had to get used to their setup: I needed to manually open the outbound port on the Hetzner Cloud firewall side. : https://docs.cloudron.io/security/#cloud-firewall Outbound ports¶ We recommend leaving all outbound ports open. Some providers like AWS EC2, Google Cloud, Digital Ocean forcefully block outbound port 25 for reducing email spam. The only way around this is to either request your server provider to unblock this port or better to setup an Email relay. It was a dumb issue hahaha omg I need some sleep.

@potemkin_ai said in can't install cloudron due to unbound issues: It seems like unbound is only used for SpamHause and during setup. If the setup issue will resorted, only SpamHause issue will remain. It's also used for DNS propagation checks (during app install, change location etc) and also verify validity of DNS records for Let's Encrypt. We cannot rely on caching resolvers because they would cache not found (NXDOMAIN) entries for very long periods of time. The recommendation is to keep all the outbound ports open - https://docs.cloudron.io/security/#outbound-ports .

@visamp said in New Hetzner Server Installation Best Practices: Do you recommend installing CrowdSec or not? Maybe it's overkill? I had it installed once, looked at pretty graphs for maybe 4–5 days. Then I forgot it, re-setup the server and did not install it again. So, I can not even tell you if it was helpful or not. But what I can say is, no one here really uses crowdsec, nor maintains support for it with cloudron. Good thing is, backup or snapshot, try it, decide for yourself, rollback if it is not to your liking.

Not sure what you mean with "redirect" here, but the code checks if the DNS A (and AAAA if you use ipv6 also) are in sync at all configured nameservers for this domain. So basically you just have to make sure that you have setup A records for my.heavendigital.com.br pointing to your server IP. Then after some time, depending on your DNS provider, this should succeed.

Thank you for your answer. So I have to figure out how to redirect port 443. As it stands, I can't, but I'll try to find a way, thank you and good luck!

@titi49600 thanks for the update. Did you have to run any command to adjust the mtu? If you post it here, it will help future readers.

I use uBlock Origin and have never had a problem.

@firmansi said in Issue with New Installation with Cloudron 8.0.0: @girish I don't activate IPV 6, i have bad experience with this Just to say, it seems going forward you'll likely hit email deliverability issues without IPv6 stuff being configured (especially to M$/ Gmail accounts). See e.g. https://forum.cloudron.io/topic/13145/problems-with-sending-mail

Not sure what we can do here I mean wget is pretty very basic and part of standard ubuntu. I am not sure who they are trying to reach stripping basic tooling on a server. I will mark this as solved but if you have idea on what we can do, I am open for suggestions. Apart from putting a note saying, "make sure you have wget installed"

Don't think this is a problem. It's quite normal to use Hyper-V and Proxmox to host Cloudron

I would be surprised if the default configs do not regulate the fan already. As you mention mostly the Paperless issue with CPU simply heats up the CPU continuously, so we have to first get down to that issue.

@awestenb it means that IPv6 record is not set up. try host -t AAAA my.domain.name . This should be the ipv6 address of you server. If your server does not have IPv6, then in the cloudron setup page -> advanced -> disable ipv6.

@potemkin_ai & @kk_cloudron On my side I was also having the issue "queryNs ETIMEOUT" , and it was because my outbound UDP port 53 was not open. I just had to add it like that on my Hetzner Cloud Firewall : [image: 1744283926608-7bf48621-4935-4413-af8d-775b9a05abe2-image-resized.png]

Yes, this was a bug. I have fixed this for the next release (8.0.1).

Fixed! Thank You!

This worked thanks

To add to what @necrevistonnezr said, add the hard drive as a Cloudron volume and use https://docs.cloudron.io/apps/#data-directory to move the app's data into that volume.

@linuxpowerhouse no worries, welcome to cloudron

There are two categories of servers for me. A) my home server, I can ping B) the server at Cloudron, which is not accessible with the two specified addresses

@alwi said in Ubuntu-server 24.04: pardon. https://gnulinux.ch/windows-11-produktschluessel Um, that's irrelevant, the correct link was https://gnulinux.ch/cloudron-1-einfuehrung