Cloudron Forum

At least they can copy/paste from the log file!!

@jdaviescoates A fresh install of Ubuntu does not have docker, nginx or nodejs. We install specific version of these , so we need to make sure it's not already installed.

I would take a step back: where are you creating the server? If it's a VPS provider, I can test out Cloudron installation there. Otherwise, can you tell me more about your server installation?

For these kind of setups, it's easiest if you use one of the automated DNS options (i.e not manual or wildcard).

Setup service1.domain.tld as one of the automated DNS options. Not sure where domain.tld is already hosted but it's not one of the options we support, you can always create a zone called service1.domain.tld and put host the zone is one of the DNS services. In your proxy, forward https://service1.domain.tld AND ``https://*.service1.domain.tld` (hope it supports wildcard) to Cloudron VM.

It should work with valid certs with the above setup.

@luckym said in Ability to go back within the installation setup wizard:

I wanted to restore Cloudron from a backup but in the setup wizard under "Domain Setup" mindlessly filled in the DNS information and clicked next instead of clicking on "Looking to restore".

I've done this before too.

Perhaps @staff could look at making the "Looking to restore" bit that's tiny at the bottom a lot more obvious?

And maybe even add another step afterwards that asks "are you actually looking to restore? go back" or something? 🤷

This is strange if nothing else happens, the code running there is https://git.cloudron.io/cloudron/box/-/blob/master/scripts/installer.sh?ref_type=heads#L126 so its not doing much but downloading nodejs and some extra filesystem things.

Can you curl or curl -sL https://nodejs.org/dist/v18.16.0/node-v18.16.0-linux-x64.tar.gz ?

@dsnradio at this point, no. You can maybe try the previous version of Cloudron. You can run the setup script as cloudron-setup --version 7.5.2. But please be aware that you cannot upgrade.

Can you try pulling that image manually using docker pull registry.docker.com/cloudron/g raphite:3.4.2@sha256:bc30121baecfa887856de56278fca5a532543c8ff439b60dc178132d578 ?

@girish thanks that worked

@girish thanks a lot super fast response. Just installed cloudron this day with the new setup-script. For the people reading this in the future) setting the immutable bit did the trick, no installation like I supposed needed. Works like charme...

Looks like some collectd related failure (if those are the last log lines):

readonly launchpad="https://launchpad.net/ubuntu/+source/collectd/5.12.0-9/+build/23189375/+files" cd /tmp && wget -q "${launchpad}/collectd_5.12.0-9_amd64.deb" "${launchpad}/collectd-utils_5.12.0-9_amd64.deb" "${launchpad}/collectd-core_5.12.0-9_amd64.deb" "${launchpad}/libcollectdclient1_5.12.0-9_amd64.deb" cd /tmp && apt install -y --no-install-recommends ./libcollectdclient1_5.12.0-9_amd64.deb ./collectd-core_5.12.0-9_amd64.deb ./collectd_5.12.0-9_amd64.deb ./collectd-utils_5.12.0-9_amd64.deb && rm -f /tmp/collectd_*.deb echo -e "\nLD_PRELOAD=/usr/lib/python3.10/config-3.10-x86_64-linux-gnu/libpython3.10.so" >> /etc/default/collectd

Can you run the above manually line by line and check if it works ?

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!