Cloudron Forum

Glad it all worked out

@W1LMS See it as two levels of security. Firewall at DC level and at server level is also best practice.

@nebulon That seemed to fix it. Thanks!

@marcusquinn said in Installing Cloudron after other software has been setup: @LoudLemur I think you'll find it surprisingly easy and empowering. HAha! That is exactly what I wanted to hear! haha. There is no time like the present... You are great, and cheers!

@linuxpowerhouse Did you check the upgrading instructions at https://docs.cloudron.io/guides/upgrade-ubuntu-20/ ?

@jdaviescoates said in Setting Up Cloudron on SSDnodes: It's really easy to install Cloudron anywhere. yep I installed Cloudron on SSDNODES without any issues ... before moving it to Hetzner. Never had any stability issues at SSDNODES but definitely you can't load them with heavy usage. And bear in mind that SSDNODES 'bargain' is only really on 3 year terms. 1 year pricing is good but not not overly attractive.

@DeBossNow it would really help if you could give more context on what you refer to when pasting plain text from presumably the Cloudron dashboard. If this is somewhere from the app configure UI, is the app in error state or which state is it in? Is the repair button enabled for that app and if so, have you tried to click that?

@mrkovash cloudron never sends 521. Can you tell us a bit more about your setup? Screenshots? Errors? Where did you have to use the loopback address (this is even more strange) ?

@girish The resolv.conf has nameserver set to 8.8.8.8 and 8.8.4.4. I did notice that when I ran the script it would overwrite dns and set to 127.0.0.1. I edited the /etc/resolvconf/resolv.conf.d/head file and permanently added nameserver 8.8.8.8 and 8.8.4.4 Ran the install and successfully installed. Thank you for your assistance!

@necrevistonnezr Thank you for your answere. I am just tryin to learn things step for step and take my time added you in discord Okay i never was been here before in this forum. this is sad what trolls are tryin i just here to improve my skills at the points where there are. clearly i am a little bit late with 29 to focus an such beginner things other learn with 15-19 but its never to late i guess

@BrutalBirdie Thanks, it worked for me.

Can just pass --redo to the setup script.

@Nostudentsomg Can you give us more information and what you have tried with step/screenshots and such?

Hey y'all. Used another domain I had that was correctly propagated. It's perfect. Now I gotta wait for my DNS records to update before I do the switch!

@cjblank This is how i fixed that exact issue: Run these commands sudo sysctl -w net.ipv6.conf.all.disable_ipv6=0 sudo sysctl -w net.ipv6.conf.default.disable_ipv6=0 sudo sysctl -w net.ipv6.conf.lo.disable_ipv6=0 double check IPv6 is off by running "ip a" This is tempoary work around just to install it and get it up and running. to restart your installation without rebuilding a new VM Add this flag --redo

Update: I installed Ubuntu 20.04 and then upgraded to Ubuntu 22.04. The Cloudron install then worked!

Cool. Thanks for the definitive answers all. Cheers.

This is fixed in 7.3.5 (will be released next week).

Not sure I completely understood your questions... but just add the DNS for my.cloud.host.name to point to the server and you should be able to access the dashboard from there. Is this a VPS or some home server? The deceptive warning is probably not related to all this.

Closed due to inactivity