Cloudron Forum

@nebulon I hit many road blocks indeed, but managed to move quite well forward
now i'm at the part of the npm rebuild and I can't do the db-migrate because I don't see any npm install being done that provides db-migrate within nodes_modules/.bin folder

I have documented the changes I had to do in the different install files to get it working, i can share this to the support email if you're interested

@jdaviescoates Add Hostinger to the list too. I signed up for a basic web hosting plan with them. I created a secondary user account in their admin panel for my developer so he could have access and it didn't work. I contacted support and it took them weeks to get it sorted. Meanwhile, I ended up sharing my main account credentials. I was asked identical questions by different staff (under the same ticket) and I was tossed around like a beach ball in a techno festival. I had better experiences with EIG owned hosts and those guys absolutely s***.

@Olgoonik-IT thanks for reporting, I have fixed this now.

@jodumont If you run the node file for cloudron directly (add it to your PATH) you don't need the set-executionpolicy bit. Node is separate from powershell and as such it can run without that.

@ascua If the new instance is in your house then you need to port-forward (or if your router/modem support - DMZ (AKA 1:1 NAT) ) the server.

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

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

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

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

@saphirata if your IP of your ISP connection (local ip) keeps changing, then you need to keep the DNS records in-sync. So for your use-case it means you have to keep adjusting the settings in Cloudflare.

Maybe for a start you could disable Cloudflare proxying and use it normally as a DNS service, then configuring your domain in Cloudron to use our Cloudflare backend and enable https://docs.cloudron.io/networking/#dynamic-dns

@opensourced said in Unable to install apps:

@girish I moved the appsdata folder to another mounted drive

I think you should have led with that... 🙂

@girish @nebulon
I did not follow the upgrade tutorial for 16.04 → 18.04 → 20.04 entirely because I have some minor adjustments on the server that were blocking the upgrade. Also, there was a minor issue with docker in the past, where I edited the file /etc/apt/sources.list.d/docker.list so this whole problem was my fault 🙂

@drzero You can also check if the demo cloudron https://my.demo.cloudron.io works well for you just to rule out some networking issues (username: cloudron password: cloudron)

This comment was very informative - https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1833013/comments/6 . I didn't realize you have to pass so many options to make it not ask questions.

@vjvanjungg https://www.netcup.eu/ (English)

Is this error still persisting, I cannot reproduce it here, since the tarball from that location loads just fine for me.

Best approach as you already found out is to create multiple VPS on your dedi.

@subven As it was not in the production list, I thought it was not supported. But I will try the generic option. Thanks for the PS, I will look into that 🙂

@girish Thanks!

@relink Cloudron does not work without a domain name. Many features like DNS integration, certificate management, reverse proxy setup etc all require a domain name.

Maybe you can try a setup like this:

Pick an imaginary domain name like relink.home Choose the noop (only for development) DNS provider. In Advanced section, choose Self signed certificates

In your router/DNS, just add entries for *.relink.home and relink.home to the server's IP. Alternately, add those entires to the /etc/hosts of your PC. You should then be able to reach, my.relink.home and install apps.