Cloudron Forum

@girish great thanks!

@girish So I saw in a previous post you said you can setup Cloudron to use a local IP rather than a public one which I decided to go that route everything still works fine but I had one more question. Will Cloudron update DNS records automatically? Like will my system break after updates or something? Will I also receive an alert from my main my.domain.com notifications saying DNS don’t match? I’m hoping with it set to local it won’t update. If it does I can just VPN into my network and access stuff and fix everything again but I was hoping I wouldn’t have to do this often if at all. Can you shed a little light on this? Thanks!

Hello. I was able to get this to work successfully with Cloudflare Tunnels. What I am having a problem with now is that my local Cloudron server is throwing fits when I go and re-sync DNS records. To get Cloudflare Tunnels to work you have to delete the current *.domain.com DNS record in Cloudflare that your Cloudron server automatically creates. Then in the Cloudflare Tunnels settings it creates a CNAME record in place of the old DNS A record that Cloudron automatically created. You do have to check the settings under TLS and disable TLS verify though. At this point it does work. I can access my site and completely disable port 443 on my router. I have zero ports exposed. Essentially Cloudflare Tunnels acts as a Reverse Proxy through the tunnel. I can route all the apps with their sub-domains this way and it works great. My question is, now that you have a little bit of backstory, how can I make Cloudron and the DNS settings Cloudflare Tunnels create work naturally together so that if DNS records re-sync it keeps everything working properly without breaking the site. To my understanding Cloudron does regular DNS checks and makes sure everything can talk to each other. If I do re-sync DNS settings or if the Cloudron server does it automatically itself via it's regular checks the DNS records get overwritten to point back to my public IP address again, instead of the Cloudflare Tunnel, which then breaks the site because the port fordwarding is turned off.

Thanks @girish

@robi I don't think I have that option maybe that's why I can't do it. Here is a screen grab.

Wow. I must be a noob but how in the world do you mark a post as solved???

Sorry for the stupid question lol.

@BrutalBirdie and @robi thanks for your guys help! @robi your suggestion by adding the new line in the /etc/ssh/sshd_config this worked perfectly and gave me my command line gui in Guacamole. I’ll mark this as solved. Thanks for your thorough explanation as not only how to fix it but also as to why it wasn’t working in the first place. Thanks again guys!

Hello,

I’ve been using Cloudron for quite awhile now and I really enjoy the simplicity of it! One of the apps I’ve been using is Guacamole. It’s completely replaced every Remote Desktop service I had. I love it!

But here is my issue. One of the servers I connect to has been running very poorly, so I decided to wipe the server and rebuild it. When I finally got it all setup again I went and removed the old server from Guacamole and re-added this rebuilt server back to Guacamole. VNC works great. But SSH is what’s causing the problem. I can’t for the life of me figure out why it won’t connect. All the other clients I use for SSH connect to the new rebuilt server with the same parameters. I pulled the logs and it says that it successfully connects and establishes itself to the server but then disconnects because a handshake failed. I did set the new rebuilt server to have the same static IP address as it had before it was rebuilt because I have other services that run on this server that have ports already setup and configured in my router and I didn’t want to have to go through and edit all them again.

My guess as to what’s happening is Guacamole has hung onto the previous servers IP address and MAC address as well as the fingerprint associated with those items for SSH. Because the same IP and MAC are identical to the previous settings but the fingerprint has changed since it’s a brand new install it’s failing the handshake. But here’s where it gets weird. I looked everywhere on where this file could possibly be located and was going to edit it to match the correct fingerprint but I cannot for the life of me find the location. It’s no where documented that I am able to locate for this scenario. But because of this hunch I had I decided to completely remove the Guacamole app from my Cloudron server and the do a brand new reinstallation of the app hoping that would clear the problem. But NOPE!!! After pulling the logs I’m still getting the same error. It’s like it saved the settings or something from the previous Guacamole install. I’m at my wits end and can really use some guidance here to make this work. This is my last attempt to get it working before I completely rebuild the Cloudron server itself next. I’m only connecting through username and password no ssh-keys. I haven’t tried that as an option because I want to know why this is even happening in the first place.

Please let me know if you have a way to fix my issue. If you would like me to I can post the logs here if need be.

Thanks!!

@necrevistonnezr Great! Thanks for your guys help. It’s much appreciated.

Okay great. So there really isn’t a con to this or any extra setup I would need to do to change this? When we change the name does that also mean I would go to mail.example.com to access my email?

I noticed that I can change my email server location from my.example.com to *.example.com. Can someone explain to me why I would want to do this and what the benefits are and also what the cons would be? I don’t quite get the point of email server location?

Thanks.