@Vladimir Can you send me a mail on support@cloudron.io? Let's try to figure where it's failing.

@girish I did not know the term. I certainly did know the effect ^^ (I might have to invest in an actual rubber duck... maybe they are especially effective)

@girish Hey, did just that, and I'm having trouble resolving names AFTER setting them. Cloudron is able to set dns records on aws just fine, but then the check to see if the records are created never gets done. Checked the logs and it's server timeouts. Tried running an nslookup query, to no avail as well. Kinda weird, seems like the same problem I had on the hosting provider, with unbound, maybe? When I try to sudo, it also says sudo: unable to resolve host ubuntu: Resource temporarily unavailable, but it gets me to root anyway. I'm a bit beyond my skills here, though, if anyone would like to chime in, I'd appreciate it.

Oh, interesting, I hadn't thought of those other use cases for this, but I really like that you brought them up, thanks for the feature request! I'll keep this thread updated with any development on that end if @girish doesn't beat me to it! ️

@robi Ahh, i completely understand now. This is a much complex level of what @girish and I are building right now with the VPN Client being one network you can choose to connect multiple other networks to. We’ve scoped that out pretty well so as we work on that and as it gets more fleshed out, I’ll update this ticket with advancements of how we might be able to have take this “sharing networks” basic concept further. I really like this train of thought though so I won’t forget it! ️

@girish https://www.ipdeny.com/ipblocks/data/countries/all-zones.tar.gz But I did get that from your blog post for 5.6: https://blog.cloudron.io/cloudron-5-6-released/ so maybe you're looking for better ones?

Oh, and it may require like 4 or 5 patches to box code. Forgot about that. It's fully functional tho, a little unpolished, a lot unpolished. But everything works. @girish and I will work together to integrate it properly at some point after 6.0. My patches run at "start" time, so the fact they're inefficient isn't too big of a deal, but just know that somewhere down the line, @girish and I will add it properly into a stable version of Cloudron.

@girish stellar service as usual, of course it was the old node version, login works as expected now!

@girish confirmed - it works now. thanks.

@girish So, it was the TLS. Changed it to 1.2 and the requests went smooth and fast. Thanks for the tips

Hi @abasitali Cloudron will attempt to resolve the DNS records with regards to the public IP address. Since you said you have an internal DNS server and hosting on-premise, can you give a bit more information about the setup? It could also help if you send a quick mail to support@cloudron.io with mentioning the domain, if you don't want to have it publicly known here, that way we can maybe see if things resolve correctly from our side. If this is not a public server, please checkout the docs at https://cloudron.io/documentation/networking/#private-dns