Cloudron Forum

@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...

Fixed in support as outlined in https://forum.cloudron.io/topic/12300/how-to-change-dns-settings-of-my-server/18

@joseph Thanks, that was it! It's all working now.

Thanks, it's working !

The only message was only related to PTR. And there was no other message. Maybe it was a special case or a problem with the request and the question was whether from my server or on the provider's side. After I clicked sync DNS, I left it for another 24 hours just to be sure, because the proprogation could have been prolonged. After 24 hours there was still a problem , then I did a record analysis and noticed as I wrote above one record A was not updated. In general, the situation embraced. You can close the topic only waiting for the improvement of the results from PTR. Generally I have changed but FCrDNS has not been updated.

Looks like that was the fix, now it doesn't change the A and AAAA records of the email server, and Cloudron can still use my External SMTP connection while having the Mail Server Location set to "cloudron.blockbluemedia.com".

i think the unbound DNS worked; seems ok now. thanks!!

I just waited 24 hours and now everything is working

https://my.hussainwh.info works for me. Note that for https://hussainwh.info to work, you have to install an app on that domain. When there is no subdomain , it's called the bare/naked/apex/root domain .

@victorlinares94 GoDaddy has put some new limitations on API access. Please contact their support. https://www.reddit.com/r/godaddy/comments/1bl0f5r/am_i_the_only_one_who_cant_use_the_api/ " We wanted to inform you that we have recently updated our Domain API requirements. As part of this update, customers are now required to have 50 or more domains in their account to utilize the API. Unfortunately, as you currently only have 1 domain in your account, access to the API is blocked for you. " See also: https://www.reddit.com/r/godaddy/comments/1chs1j8/godaddy_access_denied_via_apicall/

That fixed it, the home IP wasn't whitelisted. Thanks for your help