@THI_Staff it's not too uncommon an oversight. I made an internal note for dev. Maybe we can notify Cloudron admins if the Domain API keys are not working anymore. We do this check when adding the domain, but maybe we can do this check periodically. This will also catch API key change etc.
@girish Thanks for the complete and thorough explanation. I guess I was fooled by the apt update I saw in one of your docker image definitions (thinking that others would be following your best practice). If you are comfortable with the risk/reward balance then I am comfortable:)
@luckow good catch. In fact, the sort function usage was entirely wrong.
Fixed in https://git.cloudron.io/cloudron/cloudron-cli/-/commit/87dcb5f8cc8ae29f877a6f5b96c865ec48dd8846
I published a new CLI 5.5.0
Interesting. So, from @necrevistonnezr's like the hosts.allow/hosts.deny may not work in the future. "Note: this might not be an option on modern distributions, as support for tcpwrappers was removed from OpenSSH 6.7"
In the past I have only seen the angular templates, if the browser has javascript disabled or the javascript files are not loaded. Do you see failing requests in your browser console?
@luckow yes. See this comment - https://forum.cloudron.io/post/83868
https://git.cloudron.io/cloudron/box/-/commit/0dfadc59228978f82ae3aa2ba4be2b421e785e02 was the fix . You can always apply it locally in /home/yellowtent/box/src/dns/digitalocean.js . Then, systemctl restart box and renew all certs.
