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

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

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

I have also added Service events in the event log for the next release. So, this way, we can know if the service was automatically restarted after cert update.

It would be an interesting feature to have the mailserver for a domain be able to recognize that a mailbox it is receiving for is elsewhere and redirects the connection there. This would be at a higher level than where forwarding happens. Just like when one moves IRL and tells the Post Office the new address. Similar to 301/302 HTTP redirects.