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.

To add to this, the upper limit here is also not allocation of memory and in the end the system memory is also a limiting factor. So the setting protects you from a buggy or otherwise misbehaving app, in the way that this app cannot occupy the whole system memory, bringing down other apps.

Also for apps using language runtimes like ruby or nodejs, we have found that those usually cleanup memory on their own depending on the available memory. I think this is correct bahavior, since available memory should be used for caching as long as there is some available, but in the Cloudron case this behavior was often not favorable.

@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>

@brutalbirdie Yup, all sorted and working as intended for now.
I have upvoted your comment above. Thank you.

I updated the email relay page with newer screenshots of the SES console - https://docs.cloudron.io/email/#amazon-ses

@metalcated https://support.cloudflare.com/hc/en-us/articles/115002833612-Understanding-Cloudflare-Audit-Logs . In our cloudflare account, I can see there are records for every DNS change as "Rec del" and "Rec add".

I put some docs on how to fix the mysql addon here - https://docs.cloudron.io/troubleshooting/#mysql-addon . It's not "complete" but it's very hard to write those docs since there's a lot of things that can go wrong with mysql....

@nebulon Thanks. If I keep having this issue I'll start troubleshooting as you suggest, and will probably try to get the Vultr support people involved as well.

@zylstra thanks, I have made a fix in our next release in any case - https://git.cloudron.io/cloudron/box/-/commit/73315a42fef03bc144fdfd707b8a6d5905733109

@girish perfect answer! Worked like a charm, thanks 🙂

@murgero re-read, my response remains the same, sorry.

You know the way security scanners (or script-kiddies) works, it's to scan the network (Internet), get hosts and they software; if there is zero-day on CloudRon or other not disclosed vulnerability, apply it across the hosts.
Having DNS records showing that there is CloudRon here means you don't even need to scan for the ports, which just simplify things.

Hope that helps to understand my response here.

@klfc556 let's follow up at https://forum.cloudron.io/topic/5715/domain-setup-shows-queryns-eservfail

@klfc556 does that domain contain any special characters? Also can you query the nameservers from your server if you are logged in via SSH?

This can be done for example with host -t NS example.com

@avatar1024 /me shrugs

Hopefully someone else more knowledgable will chime in 🙂