Cloudron Forum

@joseph ah, there you go. I have indeed updated to 24.04, and presumably it was before this instruction was added.

Thank you all for the help, guys, all is well now

Thanks for sharing that and glad it worked out in the end.

Porkbun issue is fixed in 8.1

never mind, I fixed the issue with the IP. I went into GoDaddy and noticed the IP was different, so I changed it back, restarted unbound service and now my dashboard is loading with my domain. Now to restoring all of the apps with my backups.

And I would appreciate if this fix get published soon. I need to update it, because I accidently did not renew but delete the API key and there is no way back. (Really not "no bullshit" like years ago @gandi) @girish

Thanks for the explanation, I've likely overlooked that when upgrading to V8 😬 and likely also overestimated the quality of my "default" DNS 🙂 , thanks !

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.

If Hairpin NAT is not working, please refer to https://docs.cloudron.io/troubleshooting/#hairpin-nat

I think @nebulon means host -t NS vysvr.org . This should resolve to your nameservers.

Switching to hetzner feels good enough for now 😂. Full backup takes 30min for 21 apps. I've cancelled contabo storage service.
Hope this stays so snappy for the long run

@b2breporter you can contact us on support@cloudron.io and we can fix it up

Ok weird, this worked, I backed up apps and updated to Cloudron 8 but it's not working again. that file didn't change. I set it to google's public DNS and it was fine - I reinstalled tailscale and set override DNS to true which I think should fix it and let me keep using TS

Thanks, then I know it's going to return to normal. No, not using name.com. Some domains are with a Swedish provider (Loopia) and some with Cloudflare.

For anyone else, the wonderful team at Cloudron assisted further and identified the issue is that my internet service (and router) did not have ipv6 but the server was trying to use ipv6 to connect for appstore auth. Adding ipv6 with my isp and enabling in router "resolved" the issue. It is not currently known why my server was insisting on using ipv6 or how to stop that if I was unable to add it.

From error message it looks like Cloudflare ... @asatyr maybe the Cloudflare keys expired or don't work anymore ? If you go to Domains -> Edit and click save, does it work? Most likely it gives the same error. Either fix the keys or if you don't want that domain anymore, change the dns provider to manual and then delete the app and the domain.

@girish yes, I meant this configuration option.

@nebulon something is slipping out here...

If it works from host abra-ka-da-bra.mydomain.com command, but does not from Cloudron - isn't it something specific to Cloudron implementation?

@lucifer1004 thanks for the correction , will fix the original post!

@girish moreover, the package.json on my WS indicates the version installed as being "version": "5.9.0"so then I still tried from the git directory and I still get:

No image found, please run `cloudron build` first or use --image

Now, when I try without the git to the repo then I get:
App repair error: No CloudronManifest.json found
Ho my...