Cloudron post install questions

[ejarvis]

@girish said in Cloudron post install questions:

@BrutalBirdie said in Cloudron post install questions:

The Cloudron install needs to be run with root / sudo.
Amazingly this is not mentioned anywhere @staff I never noticed that until now.

The setup script errors out that you have to run as sudo.

I vaguely remember elevating with sudo on the installation script, and since it was as extensive as it was, I did other things and let it do its job.

Since I saw somewhere that every night the Cloudron service will handle all updates and such, and with part of the documentation stating that we should 'un-hold' some of the updates that were previously on-hold, I haven't checked yet to see if it helped or hindered yet. Will post more if I see things that I'm not sure how to deal with.

In the meantime, if I reinstalled the OS from a live ISO, will the installation script known to connect with my current account, or do I have to remove everything and start over completely from scratch?

[subven]

@ejarvis said in Cloudron post install questions:

or do I have to remove everything and start over completely from scratch?

The easiest way is to setup a fresh new server, Install Cloudron and during initial setup, restore from a backup. Be sure to install the same Cloudron version your current server is on. I'm not sure if you also need the same OS version (Ubuntu 20.04 in your case) but I would advice to stick with it as you can upgrade later.

@ejarvis said in Cloudron post install questions:

Would it still be an issue if those packages were completely removed from the server?

Not sure what is the best way to fix a half broken Cloudron installation. AFAIK Cloudron expects explicit apt package versions and installing other packages can easy mess with that. While in theory it is possible, I would avoid it and start with a clean OS as it will 100% work.

@ejarvis said in Cloudron post install questions:

I added VNC as a means to access it without really giving it another thought

I think VNC to get basic terminal access should not be the problem. Installing a desktop enviroment however is far more complex in terms of related packages. If you install VNC before Cloudron, I think you should be fine as the setup script will pick the right packages anyway. EDIT: Okay so I digged into the topic and VNC seems to require a DE installed (even for a terminal session) at least if it runs on OS level.

I haven't found anything here in the forums about how others solve that if they don't have VNC from their hoster.

[ejarvis]

@subven said in Cloudron post install questions:

@ejarvis said in Cloudron post install questions:

or do I have to remove everything and start over completely from scratch?

The easiest way is to setup a fresh new server, Install Cloudron and during initial setup, restore from a backup. Be sure to install the same Cloudron version your current server is on. I'm not sure if you also need the same OS version (Ubuntu 20.04 in your case) but I would advice to stick with it as you can upgrade later.

@ejarvis said in Cloudron post install questions:

Would it still be an issue if those packages were completely removed from the server?

Not sure what is the best way to fix a half broken Cloudron installation. AFAIK Cloudron expects explicit apt package versions and installing other packages can easy mess with that. While in theory it is possible, I would avoid it and start with a clean OS as it will 100% work.

@ejarvis said in Cloudron post install questions:

I added VNC as a means to access it without really giving it another thought

I think VNC to get basic terminal access should not be the problem. Installing a desktop enviroment however is far more complex in terms of related packages. If you install VNC before Cloudron, I think you should be fine as the setup script will pick the right packages anyway. EDIT: Okay so I digged into the topic and VNC seems to require a DE installed (even for a terminal session) at least if it runs on OS level.

I haven't found anything here in the forums about how others solve that if they don't have VNC from their hoster.

It absolutely does, which was why I had installed a minimal DE of XFCE4.

I think that I am going to have to start over and see if (now that I know that Cloudron requires an unaltered installation of Ubuntu Server) that lets me install the app that I wanted to deploy.

[girish]

@ejarvis yes, don't install ubuntu desktop and such. Maybe installing some minor tools here and there is OK, but bringing in a whole bunch of other packages is completely untested territory.

[subven]

@girish do you have a solution to install VNC on a Cloudron host?

[ejarvis]

All:

You're not going to believe this ...

I set out to recreate the Ubuntu server today, simply because I have nothing else too pressing that needed my immediate attention.

It's important to know that this was a fresh install, with the only package that was installed prior to installing Cloudron being net-tools.

I connected everything, and as my luck would have it, attempted to install Guacamole again, and it hangs at the same place.

In addition to that, my screen is also showing that it's "Starting services" and that it could take a while.

EDIT: Correction, the app is showing "Installing - Waiting for Cloudron to initialize' as its status.

I'm starting to wonder if there is something else that is preventing this from happening that's not directly related to Ubuntu or Cloudron.

As an aside, I have a recursive DNS setup that also uses Unbound, and I had set that as the primary DNS IP and nothing else as a secondary or tertiary. Could this be an issue? If so, why does everything else work flawlessly but not an app install?

I also use Docker ran from another server, and finally, the Ubuntu server is run on a virtual machine.

While I find troubleshooting Linux things very challenging and fulfilling, this one is starting to have the opposite effect. Any ideas and help, as always, is greatly appreciated.

[ejarvis]

Just checked the Services screen:

Cloudron, docker, mail, mysql, nginx, turn, and unbound are all active and 'green'. Everything else is red.

[ejarvis]

Besides port 80 and 443, are there any other important ports that should be open for communication?

[girish]

@ejarvis said in Cloudron post install questions:

EDIT: Correction, the app is showing "Installing - Waiting for Cloudron to initialize' as its status.

The issue is that the (internal) services are all not starting up on the server for some reason. Can you email the entire /home/yellowtent/platformdata/logs/box.log to support@cloudron.io ? There's got to be some error there or maybe it is stuck somewhere else which we are not handling.

[ejarvis]

@girish It looks like it's choking on MySQL for some reason. I'll send you the log as soon as I am able to.

[ejarvis]

Sorry for the delay, have had internet issues at the office that was preventing me from grabbing the log file and sending it via email.

Now that we're back online I will get that done as soon as possible.

[ejarvis]

@girish said in Cloudron post install questions:

@ejarvis said in Cloudron post install questions:

EDIT: Correction, the app is showing "Installing - Waiting for Cloudron to initialize' as its status.

The issue is that the (internal) services are all not starting up on the server for some reason. Can you email the entire /home/yellowtent/platformdata/logs/box.log to support@cloudron.io ? There's got to be some error there or maybe it is stuck somewhere else which we are not handling.

Sorry for the delay, apparently our outage also almost caused file degradation on our NAS and that had to be resolved before this could.

I just sent a response to that email address that also includes Johannes, if you don't see it that is where you can request to look at it.

Please let me know what else I can do.

[girish]

@ejarvis The issue seems to be that mongodb has crashed/not starting up properly. I sent you some instructions via email.

2022-12-08T14:23:14.794Z box:cloudron Startup task at index 2 failed: Network error waiting for mongodb: connect ECONNREFUSED 172.18.0.5:3000 BoxError: Network error waiting for mongodb: connect ECONNREFUSED 172.18.0.5:3000
at /home/yellowtent/box/src/services.js:588:33
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async promiseRetry (/home/yellowtent/box/src/promise-retry.js:17:20)
at async waitForContainer (/home/yellowtent/box/src/services.js:583:5)
at async startMongodb (/home/yellowtent/box/src/services.js:1508:9)
at async Object.startServices (/home/yellowtent/box/src/services.js:806:9)
at async Object.start (/home/yellowtent/box/src/platform.js:67:13)
at async onActivated (/home/yellowtent/box/src/cloudron.js:79:5)
at async Array.<anonymous> (/home/yellowtent/box/src/cloudron.js:130:9)

[ejarvis]

@ejarvis said in Cloudron post install questions:

@girish said in Cloudron post install questions:

@ejarvis said in Cloudron post install questions:

EDIT: Correction, the app is showing "Installing - Waiting for Cloudron to initialize' as its status.

The issue is that the (internal) services are all not starting up on the server for some reason. Can you email the entire /home/yellowtent/platformdata/logs/box.log to support@cloudron.io ? There's got to be some error there or maybe it is stuck somewhere else which we are not handling.

Sorry for the delay, apparently our outage also almost caused file degradation on our NAS and that had to be resolved before this could.

I just sent a response to that email address that also includes Johannes, if you don't see it that is where you can request to look at it.

Please let me know what else I can do.

I performed those steps, the DB is still not starting up. I am going to respond to that email message and attach the logs so that you can see what's happening.

[namitazop]

can i install cloudron on fedora server

[nebulon]

@namitazop Cloudron only supports Ubuntu (20 or 22).

[namitazop]

okay, i'll try it running on ubuntu using virtual machine.. .