Cloudron Forum

@np_cloudron The Cloudron admin credentials and SSH credentials are different. The CLI credentials would have been set when you installed Ubuntu. Not sure where you got the ISO from, but maybe it has some default login? The enable SSH feature is for Cloudron support team to access your server. You should be able to access your server regardless of that.

@shlomi I assume you mean the web server is installed on another server (and not on the same one as Cloudron). If that's the case, then it's fine. Otherwise, we don't support running additional applications on the same server as Cloudron. (why is cloudron not using DNS-level validation for SSL so we will not need to open posts if we do not want/need. ) This is the case already. You have to use one of the programmatic DNS providers (and not manual or wildcard). If you do this, you don't need to open port 80. Please see https://docs.cloudron.io/certificates/#port-80-requirement

Right, Cloudron does not work on ARM. Please see https://docs.cloudron.io/installation/

Unfortunately, we don't support lxc.

Since nobody has any suggestions so far, I am going to just kick off the installer again and see if anything goes differently.

@kdev Indeed as @scooke mentioned it seems that docker is already installed on the server. Can you uninstall it and try again? In general, Cloudron must be installed on a fresh Ubuntu 20.04 without docker etc.

@d19dotca @Lonkle , had the same issues with Cloudron installation on vpsdime. Fixed it using the same workarounds in this thread. Seems to work fine now. Not sure if there will be any issues in the future..

@girish Thanks for that command. It is indeed strange and I haven't seen it on other Cloudrons, so something must have got stuck with this one. Not a big deal, but it's nice to have that message not displaying any more.

Ok, I solved it. I had to delete all my DNS settings that previously existed and then reset them. Once I did this within milliseconds Cloudron started working. Whew, I was sweating bullets there for a minute.

@nebulon You try to make things easy for us but we'll screw it up somehow. ; )

@guyds said in Single domain, multiple cloudrons?: I suppose each Cloudron needs a unique domain name because of the DNS records that are being created when installing a Cloudron: DKIM, SPF, DMARC? Yes, and also because we need a unique location to access the dashboard. what if the domain that's being used for a Cloudron already has e-mail related DNS records, for example when it's already configured for use with G Suite or Office 365? Will Cloudron modify those records, override them or just ignore them? If you have an existing DMARC, it don't touch it. Otherwise, it will put the default strict DMARC policy. DKIM uses a unique selector domain, so it won't affect other DKIM entries. The SPF is modified with "a: my.<domain.com" into the existing SPF.

Ah .. ssdnodes can also be ip6 only. ip4 adds a fair chunk of money these days.

Haha, well glad you managed to resolve it now and thanks for sharing the detailed resolution, might give others in the future some pointers where to look for as well.

@girish it's been solved. I did a docker logout and tried again. Got the error again but this time the error was a bit more detailed. Tried it again and it worked. Thanks!

@atrilahiji said in Installation gets stuck in "checking DNS" step: @jakobgreenfeld Oh I missed the bit where theres only a txt record. Add an A record pointing my.domain.com to your IP. I've had nothing but trouble with Namecheap's API for configuring everything so I've started doing this: A record for *.domain.com A record for @ That did the trick! It's working now. Thanks!

@zjuhasz1 Right, this is also fixed. The packages were installed because we use apt without --no-install-recommends. You can remove those gnome packages by hand for now if it bothers you but it doesn't run any daemons, so it's mostly harmless.

@nebulon Probably not anytime soon. Nexus Bytes' minimum billing period is monthly, and I usually wait to see if they offer discounts before getting one.

I was mistaken, it doesn't install it (not collectd anyway). This is the dep graph of collectd. root@my:~# apt-rdepends collectd Reading package lists... Done Building dependency tree Reading state information... Done collectd Depends: collectd-core (<< 5.9.2.g-1ubuntu5.1~) Depends: libc6 (>= 2.14) Depends: librrd8 (>= 1.3.0) collectd-core Depends: debconf (>= 0.5) Depends: debconf-2.0 Depends: libc6 (>= 2.17) Depends: libcap2 (>= 1:2.10) Depends: lsb-base debconf PreDepends: perl-base (>= 5.20.1-3~) perl-base PreDepends: dpkg (>= 1.17.17) PreDepends: libc6 (>= 2.29) PreDepends: libcrypt1 (>= 1:4.1.0) dpkg Depends: tar (>= 1.28-1) PreDepends: libbz2-1.0 PreDepends: libc6 (>= 2.15) PreDepends: liblzma5 (>= 5.2.2) PreDepends: libselinux1 (>= 2.3) PreDepends: libzstd1 (>= 1.3.2) PreDepends: zlib1g (>= 1:1.1.4) tar PreDepends: libacl1 (>= 2.2.23) PreDepends: libc6 (>= 2.17) PreDepends: libselinux1 (>= 1.32) libacl1 Depends: libc6 (>= 2.14) libc6 Depends: libcrypt1 (>= 1:4.4.10-10ubuntu4) Depends: libgcc-s1 libcrypt1 Depends: libc6 (>= 2.25) libgcc-s1 Depends: gcc-10-base (= 10.2.0-5ubuntu1~20.04) Depends: libc6 (>= 2.14) gcc-10-base libselinux1 Depends: libc6 (>= 2.30) Depends: libpcre2-8-0 (>= 10.22) libpcre2-8-0 Depends: libc6 (>= 2.14) libbz2-1.0 Depends: libc6 (>= 2.4) liblzma5 Depends: libc6 (>= 2.17) libzstd1 Depends: libc6 (>= 2.14) zlib1g Depends: libc6 (>= 2.14) debconf-2.0 libcap2 Depends: libc6 (>= 2.14) lsb-base librrd8 Depends: libc6 (>= 2.29) Depends: libcairo2 (>= 1.2.4) Depends: libdbi1 (>= 0.8.4) Depends: libglib2.0-0 (>= 2.28.0) Depends: libpango-1.0-0 (>= 1.22.0) Depends: libpangocairo-1.0-0 (>= 1.14.0) Depends: libpng16-16 (>= 1.6.2-1) Depends: libxml2 (>= 2.7.4) libcairo2 Depends: libc6 (>= 2.29) Depends: libfontconfig1 (>= 2.12.6) Depends: libfreetype6 (>= 2.9.1) Depends: libpixman-1-0 (>= 0.30.0) Depends: libpng16-16 (>= 1.6.2-1) Depends: libx11-6 Depends: libxcb-render0 Depends: libxcb-shm0 Depends: libxcb1 (>= 1.6) Depends: libxext6 Depends: libxrender1 Depends: zlib1g (>= 1:1.1.4) libfontconfig1 Depends: fontconfig-config (>= 2.13.1-2ubuntu3) Depends: libc6 (>= 2.14) Depends: libexpat1 (>= 2.0.1) Depends: libfreetype6 (>= 2.9.1) Depends: libuuid1 (>= 2.16) fontconfig-config Depends: fonts-dejavu-core Depends: fonts-freefont Depends: fonts-liberation Depends: ttf-bitstream-vera Depends: ucf (>= 0.29) fonts-dejavu-core fonts-freefont fonts-liberation ttf-bitstream-vera ucf Depends: coreutils (>= 5.91) Depends: debconf (>= 1.5.19) Depends: sensible-utils coreutils PreDepends: libacl1 (>= 2.2.23) PreDepends: libattr1 (>= 1:2.4.44) PreDepends: libc6 (>= 2.28) PreDepends: libselinux1 (>= 2.1.13) libattr1 Depends: libc6 (>= 2.4) sensible-utils libexpat1 Depends: libc6 (>= 2.25) libfreetype6 Depends: libc6 (>= 2.14) Depends: libpng16-16 (>= 1.6.2-1) Depends: zlib1g (>= 1:1.1.4) libpng16-16 Depends: libc6 (>= 2.29) Depends: zlib1g (>= 1:1.2.11) libuuid1 Depends: libc6 (>= 2.25) libpixman-1-0 Depends: libc6 (>= 2.29) libx11-6 Depends: libc6 (>= 2.26) Depends: libx11-data Depends: libxcb1 (>= 1.11.1) libx11-data libxcb1 Depends: libc6 (>= 2.14) Depends: libxau6 Depends: libxdmcp6 libxau6 Depends: libc6 (>= 2.4) libxdmcp6 Depends: libbsd0 (>= 0.2.0) Depends: libc6 (>= 2.4) libbsd0 Depends: libc6 (>= 2.25) libxcb-render0 Depends: libc6 (>= 2.14) Depends: libxcb1 (>= 1.8) libxcb-shm0 Depends: libc6 (>= 2.4) Depends: libxcb1 (>= 1.12) libxext6 Depends: libc6 (>= 2.14) Depends: libx11-6 (>= 2:1.6.0) libxrender1 Depends: libc6 (>= 2.14) Depends: libx11-6 (>= 2:1.6.0) libdbi1 Depends: libc6 (>= 2.14) libglib2.0-0 Depends: libc6 (>= 2.28) Depends: libffi7 (>= 3.3~20180313) Depends: libmount1 (>= 2.28) Depends: libpcre3 Depends: libselinux1 (>= 1.32) Depends: zlib1g (>= 1:1.2.2) libffi7 Depends: libc6 (>= 2.14) libmount1 Depends: libblkid1 (>= 2.17.2) Depends: libc6 (>= 2.25) Depends: libselinux1 (>= 2.6-3~) libblkid1 Depends: libc6 (>= 2.25) libpcre3 Depends: libc6 (>= 2.14) libpango-1.0-0 Depends: fontconfig (>= 2.1.91) Depends: libc6 (>= 2.14) Depends: libfribidi0 (>= 1.0.0) Depends: libglib2.0-0 (>= 2.59.2) Depends: libharfbuzz0b (>= 2.1.1) Depends: libthai0 (>= 0.1.25) fontconfig Depends: fontconfig-config Depends: libc6 (>= 2.4) Depends: libfontconfig1 (>= 2.13.0) Depends: libfreetype6 (>= 2.8.1) libfribidi0 Depends: libc6 (>= 2.4) libharfbuzz0b Depends: libc6 (>= 2.14) Depends: libfreetype6 (>= 2.9.1) Depends: libglib2.0-0 (>= 2.31.8) Depends: libgraphite2-3 (>= 1.2.2) libgraphite2-3 Depends: libc6 (>= 2.14) libthai0 Depends: libc6 (>= 2.14) Depends: libdatrie1 (>= 0.2.0) Depends: libthai-data (>= 0.1.10) libdatrie1 Depends: libc6 (>= 2.14) libthai-data libpangocairo-1.0-0 Depends: libc6 (>= 2.4) Depends: libcairo2 (>= 1.12.10) Depends: libfontconfig1 (>= 2.12.6) Depends: libglib2.0-0 (>= 2.59.2) Depends: libpango-1.0-0 (= 1.44.7-2ubuntu4) Depends: libpangoft2-1.0-0 (= 1.44.7-2ubuntu4) libpangoft2-1.0-0 Depends: libc6 (>= 2.4) Depends: libfontconfig1 (>= 2.13.0) Depends: libfreetype6 (>= 2.2.1) Depends: libglib2.0-0 (>= 2.59.2) Depends: libharfbuzz0b (>= 2.6.0) Depends: libpango-1.0-0 (= 1.44.7-2ubuntu4) libxml2 Depends: libc6 (>= 2.29) Depends: libicu66 (>= 66.1-1~) Depends: liblzma5 (>= 5.1.1alpha+20120614) Depends: zlib1g (>= 1:1.2.3.3) libicu66 Depends: libc6 (>= 2.29) Depends: libgcc-s1 (>= 3.0) Depends: libstdc++6 (>= 5.2) Depends: tzdata (>> 2019c-3ubuntu1~) libstdc++6 Depends: gcc-10-base (= 10.2.0-5ubuntu1~20.04) Depends: libc6 (>= 2.18) Depends: libgcc-s1 (>= 4.2) tzdata Depends: debconf (>= 0.5) Depends: debconf-2.0 And gnome desktop is not installed: root@my:~# dpkg -s ubuntu-gnome-desktop dpkg-query: package 'ubuntu-gnome-desktop' is not installed and no information is available Use dpkg --info (= dpkg-deb --info) to examine archive files.

@tx-hermit Ah, here's the explanation - https://serverfault.com/questions/1024770/ubuntu-20-04-time-sync-problems-and-possibly-incorrect-status-information . Uninstalling/disabling ntp service does the trick! I will make a fix for next release.

I think we won't change the minimum requirement tested for in the cloudron-setup script for now. It seem quite the edge case to have that little storage available, however it is good that we know there is a possible workaround for those cases.