@scooke Thank you very much! Bookmarked

@luckow Thanks! didn't know SoGo can too, updated my post!

Hi and welcome here @briankb What you say is correct, you can have multiple Cloudrons bound to the same cloudron.io account and those Cloudrons may have different subscription states.

@girish That'd be awesome, thanks Girish. I'll hope it's ready for this week though for everyone and that should fix it.

@manngobaum yes, this was a display bug. It's fixed in the upcoming release. Thanks for reporting.

@smokeyfro I replied from support@ earlier today but I am able to reach your dashboard just fine. Can you confirm? Not sure what changed but looks like you managed to fix this yourself. What did you have to do ?

@girish that's what I meant, the cmd ran always before, but now only in the rare case the directory isn't there

For reference, the other thread is https://forum.cloudron.io/topic/5819/jellyfin-install

@nebulon Yes, it took a while to figure that out. The UI is the confusing part, since if you see that screen the first time and it is populated, you have no indication to clear it, or button to turn it off. The logical part is to change what it says, for ex Disallow to Allow, but that doesn't work either So a UX improvement would be to have a toggle, which only displays the robots.txt proxy content if it's enabled and while off gives a hint as to what turning it on will actually do. That way the breadcrumbs lead to the loaf of understanding and satisfaction

@murgero I suspect the exception is coming from https://git.cloudron.io/cloudron/cloudron-cli/-/blob/master/src/actions.js#L255 . That function is called from https://git.cloudron.io/cloudron/cloudron-cli/-/blob/master/src/actions.js#L309 (you can see the error message in the line after). If you know some nodejs, maybe you can debug that to see why it thinks options is undefined.

Solved. It was a small misconfiguration on the registrar side. Thanks!

@girish thanks a lot, that sounds just right

@nebulon Thank you, yes!!! i am now able to access it. great help.

@nebulon Thanks

@brutalbirdie Thank you so much! Ill give it a go. Really appreciate your help. Hopefully the internal IP wont ake me to my router web console & onto the cloudron doman registration page.

@korishan said in Cannot Install Cloudron: Package 'mysql-server-5.7' has no installation candidate: on a new install of Ubuntu Server 21.04. Cloudron only supports running on the LTS releases of Ubuntu, which would mean Ubuntu 20.04 at the time of writing this. https://docs.cloudron.io/installation/

@shodanime is this a clean install of Ubuntu? Or do you already have stuff installed on this server? Because Cloudron should be installed on a fresh Ubuntu install.

it's solved, it was a problem with resolv.conf. The DNS servers of my scaleway instance are not responding anymore ...

@inference the issue is docker itself is not running (for some reason). app memory is not an issue because apps are run as containers using docker. What I can suggest is: spin up another new VPS using the VM image you have. check if docker runs then for backups, do you remember how you configured backups in Cloudron ? By default, the backups are in /var/backups of the server. Do you see many timestamped directories in that folder?

@imc67 currently only via SSH, so umount the device and then run systemctl restart <mountpointunit.mount>