If you like you can send us your domain name to support@cloudron.io and we can check if it's something on your side (i.e. some browser caching issue) or if we see it as well.
I had the same issue and I was able to follow the steps given about setting up a redirection in Cloudron. In fact, I decided to write a full article about it to help others understand how to fix this issue step by step.
You will have to make sure you put the right DNS entries and then set up the redirection. Read this guide here and it will help you to fix this issue.
@mastadamus right, the spamlists won't work if those lookups get blocked. Currently, if the lookups fail, the mail server will simply go ahead and try to detect spam via spamassassin. It's just one of the metrics for spam detection. I guess it's fine if it's working OK for you without it .
@girish No I've not patched manually, I have assumed sorry
I assumed the latest update was with the CNAME/A-record fix was live.
The thing was that my home server has been offline for a while and when I started it up it updated to from v7.0.4 to v7.1.3 then v7.1.3 to v7.1.4.
After that the DNS propagation didnt work any longer, as it had done before.
Nope, there's no AAAA record, just an "A+ Dynamic DNS Record"
Incidentally, I'm about to switch this domain to Hetzner, in any event. Namecheap is ok but also quite annoying from time to time...
@meaculpa hehe I was just about to comment here, since I wasn't able to reproduce it on my side.
Glad it worked out now for you. Always good to have such topic for others to find if they hit the same issue in the future.
@atrilahiji said in Installation gets stuck in "checking DNS" step:
@jakobgreenfeld Oh I missed the bit where theres only a txt record. Add an A record pointing my.domain.com to your IP. I've had nothing but trouble with Namecheap's API for configuring everything so I've started doing this:
A record for *.domain.com
A record for @
That did the trick! It's working now. Thanks!
@andreasdueren said in Cloudron can't uninstall apps after access to domain got denied:
Sep 26 10:49:40 box:dns unregisterLocation: Error unregistering location A. retryable: false. message: Invalid access token statusCode: 403 code:9109
The directory message is just a warning can be ignored. The above message is the real error. Are you sure you are not using any other domain in the app which in turn uses some DNS provider? Are all the DNS providers manual ?
@andrewj720 Looks like DNS is not working on your server. You can also try host cloudron.io etc, I guess none of it working?
Can you check if your cloud firewall allows outbound port 53 UDP ? I think there was a post on this forum some time ago that someone had it blocked in AWS security group by mistake, for example.
Hey guys, sorry for the delay
I've updated the fork and the providers function, if I get permission to create a new branch or you open one I can open an MR with the new branch and let you review