Cloudron Forum

@kk_cloudron that is correct, Cloudron requires IPv4 and does not work on IPv6 only servers (yet).

@chiragnahata The cloudron for installed and setuped. After that I installed the Guacamole and OpenVPN. After they got installed. I just opened them. Then I got that error message. I don't what is the promblem. I uninstalled and reinstalled the apps but same issue. Please help.

@adhithiyan I thought I fixed this in 7.2.2 . collectd has an option to disable FQDNLookup. Can you tell me which version of Cloudron you installed ? If you don't remember, you can check the file /home/yellowtent/box/VERSION. It's also in the Settings page of the dashboard (this appears only after you have setup cloudron).

@JOduMonT Both issues are fixed in the latest package.

Indeed, OpenVZ is not supported. I recently discovered systemd-detect-virt , will try to add a warning in our install script based on what it detects.

@humptydumpty thanks for the hint. I have update the blog post accordingly.

Regarding the Ubuntu installation, you can already set the server name to the intended dashboard domain and for the username, just use ubuntu or anything besides cloudron-* or yellowtent, to avoid conflict and confusion later.

@girish I'm not. I'm self hosting. It's running on a Ubuntu 20.04 Server install on a Synology 1517+ with Intel Processor. It's got 4 Cores and 6GB of memory for now.

@JavaCraft Can you post the output of free -m ?

To move ahead, you can just edit the line readonly MINIMUM_MEMORY="974" to be something lower in the cloudron-setup script. It's at the top of the file around line 14 and run the setup script again.

I have put a fix in https://git.cloudron.io/cloudron/box/-/commits/bfb233eca19df07a82e3b524812d8270371ed738 which should hopefully fix this.

I have put a fix in https://git.cloudron.io/cloudron/box/-/commits/bfb233eca19df07a82e3b524812d8270371ed738 which should hopefully fix this.

@PlaceToGame hi there, you would have to start fresh with a pristine Ubuntu image/installation. This is to avoid any side-effects from half-installed services.

@scooke the solution was in advanced settings creating let's encrypt manually at least this is what I understood from my friend.

See https://forum.cloudron.io/topic/6632/help-me-please-got-error-while-installing-the-cloudron-on-a-fresh-ubuntu-20-04-x64-server

Thank you all, I only thought the port forwarding of 80 was enough,

Thank you for all the help for explanations ❤

@blackshot7 are you able to run those commands manually and check if they succeed ? maybe some DNS resolution is not working?

@girish said in Docker Container - Unable To Install Cloudron:

@brutalbirdie said in Docker Container - Unable To Install Cloudron:

Maybe adding Docker in there as well to prevent confusion.

Done!

The fast guy! 😄

@kirakodo what is the output of this command that tests IO on your system?

dd if=/dev/zero of=/tmp/test1.img bs=1G count=1 oflag=dsync ; rm /tmp/test1.img

@brutalbirdie
sorry about that, by 'it was' i meant that it was on my secondary machine. I am new to these things and I apologise for anything annoying.

FWIW, a great DNS tool for checking on DNS propagation progress is here: https://dnschecker.org