Looks like the DNS resolution is failing. Can you explain your environment and check if you can resolve any host from the system via SSH? Is the unbound service working?

It was indeed a mishap in my provider's area of responsibility. Thanks again for pointing me in the right direction.

thanks, fixed in https://git.cloudron.io/cloudron/box/-/commit/1d1a7af48ebd41fa9a54f73c124a708c226e38e8

@girish Yes Everything is back to normal. Thanks a lot !!!

@matix131997 This was a bug in the UI code (setupdns view code). Fixed in https://git.cloudron.io/cloudron/box/-/commit/003bc457bf95a5b555a83d76b36199f3acec8ece As a workaround: Setup the DNS as manual or wildcard for a start Then, after you setup admin etc, go to Domains View and change it to Bunny. This view does not have this bug.

@subven so what kind of volume is it for paperless? Sorry really would love to know, also having a ads-1700W

Back again now - https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci

You need to remove some log files and also unused kernels apt-get remove `dpkg --list 'linux-image*' |grep ^ii | awk '{print $2}'\ | grep -v \`uname -r\`` source: https://docs.cloudron.io/troubleshooting/ and: Use ncdu to browse every container My results: Gained 1gb of storage by deleting /usr/local/share/.cache/yarn/ on a container volume Gained 500mb of storage by deleting Anaconda distribution package cache within a container volume source: https://forum.cloudron.io/topic/4604/disk-space-should-never-bring-a-whole-server-down/46?_=1708028984619

@nebulon Ok, I'll proceed with this suggestion.

Which plugin are you referring to and can you maybe paste some errors if any?

@saint Excellent, thanks for letting us know. Sequencing matters!

it just went away, i think the router had a DNS cache thats flushed now. It's no longer being set as the DNS server via DHCP, so I think its resolved.

Just to clarify, the account on your server itself, where Cloudron is installed, is NOT the same as the appstore account from cloudron.io

Thank you, it helped

There is no resume logic currently. Have you tried to tweak the part-size, concurrency and memory limit for the backup in the advanced backup settings?

Yes, problem solveld. Thank you!

@aqeelzakir-com said in SPF DNS record (TXT) did not match.: Relay error: Connect to port25check.cloudron.io timed out. Check if port 25 (outbound) is blocked Email Status is checked every 30 minutes. See the troubleshooting docs for more information. See https://docs.cloudron.io/email/#outbound-ports . Basically, your server is unable to send mail because outbound port 25 is blocked. You have to either get it unblocked by talking to your VPS provider or you can set up a relay. Expected: v=spf1 a:my.example.company include:_spf.google.com ~all Actual: v=spf1 include:_spf.google.com ~all If you are going to use a relay, the error above will go away automatically. Otherwise , you have to add a:my.example.company into the SPF record in the DNS.

Hi @girish, hi @nebulon. Many thanks for perfect explanation, hope to have got that. Have now configured as explained above and apex domain does now also produces perfectly valid cert signed by LE. Many thanks also for impressingly quick response during weekend - appreciated.

I wanted to let you know how I got everything to work, it might help other users. The initial issue was about DNS resolution. The quick fix is indeed to use the forward-everything option in unboud but with the previously used dns server. To find that value you just need to do a resolvectl and look at the value of the Current dns servers. In my case it was 10.0.2.3 (the one that was linked to my vpn on the host machine of the server). That is enough to fix the installation script losing internet. For the Configuration error: Domain resolves to ["XXX.XXX.XXX.XXX"] instead of IPv4 XX.XX.XX.XX the quick fix in my case (home server not directly exposed to the internet) was to install an openvpn server on the vps server (https://www.cyberciti.biz/faq/ubuntu-22-04-lts-set-up-openvpn-server-in-5-minutes/) and an openvpn client on my home server so that my home server gets the vps's IP address. In this setup you I also need a reverse proxy to expose the 80 and 443 ports from the home server to the vps.