@eddowding said in Updating Cloudron to a stable version: I was migrating servers when I noticed that I'm on 7.2.5, but the latest is 7.3.2. When moving to the new server, you can install it as ./cloudron-setup --version 7.2.5 . 7.3 was out last week, just ironing out some regressions. We expect to start rolling it out next week.

@necrevistonnezr I wasn't aware of the setting, good to know.

@girish Great. Yes, thanks for asking, it was a painful several hours during the wee hours of the night figuring out how to generate a set of new certs that would bring the UI back enough to regenerate them all. I ended up using one of the 3rd party CLI tools for LE called getssl.

Currently Cloudron is single-server only, however you can of course have multiple Cloudron and thus servers. You can also connect those Cloudrons with regards to the users, by using the external user directory on one Cloudron connecting to the user directory server on the other.

Whoops, apologies. It seems you already wrote to support@cloudron.io and the issue is already resolved.

@subven said in out of space error leading to missing certs: @girish there is no way to trigger certificate renewal over the (SSH) console? I'd like an answer to this question.. as I just ran into the missing cert problem too. Having deleted all the conf/cert files, and gotten nginx started, the UI is still not accessible after box restart. All apps are inaccessible too. box restart seems to recreate the /etc/nginx/applications/my.domain.conf BUT doesn't check if the /home/yellowtent/platformdata/nginx/certs/my.domain.host.cert is there. How are they regenerated from the CLI?

@nebulon Awesome! Muchas Gracias!

That's great! Thank you very much.

@mrchrisjones I don't think the reddit thread is related to this directly, but it seems our latest version has some install regression. We are investigating. Until that you can run cloudron-setup --version 7.2.5 on a fresh Ubuntu which should not have the issue. And to confirm, Cloudron does support running at home as long as you can portforward the relevant ports from your router to the server. Sorry for that hickup on our side.

@nebulon ohh yes that could be it.

@nebulon Thanks, corrected by hosting company, now it worked fine.

Closest upstream issue I found was https://github.com/xtermjs/xterm.js/issues/3380 . But @nebulon tells me the latest 7.3 release moves xterm.js to some OpenGL based rendering, so probably this bug solves itself.

thanks for sharing the root cause!

@robi Thank you!! Nginx Proxy Manager is a UI + LetsEncrypt for Nginx if I have to simplify it. Do you have a sample Nginx proxy conf for this setup? Thanks again!

This should hopefully be fixed in Cloudron v7.3

You could install Cloudron within a subdomain. This way you could do something like my.sub.domain.com for Cloudron itself and *.sub.domain.com for the Wildcard DNS entry.

Sounds good. Yes, we're happy to help with query optimisation in apps and send feedback upstream. This is the quickest way we can do that. With some luck, we'll all end up with faster apps from this R&D too.