@leefree IAs a first step, are you able to access https://<internal-ip-of-your-vm> ? If that works, it means the VM itself is fine and ports are open. Next step is then to figure why BT home hub is not forwarnding ports correctly.

OK, I have fixed the unbound issue with IPv6. It's an upstream bug but I have made a workaround for the moment. Fix will be part of 7.3.5 (released next week).

okay, i'll try it running on ubuntu using virtual machine.. .

@interface as long as your Cloudron dashboard is reachable you can perform all this from the UI. If your IP has changed by now for the dashboard as well, then initially set your current IP manually for your my.example.com dashboard domain to reach that again.

@madmaneighteen can you share a bit more about your environment? Also when the routing and possible portforwarding are correctly setup, you should hit nginx on your Cloudron there, so for a start check if nginx is running in your Cloudron server systemctl status nginx and also maybe try to curl localhost within the server to ensure nginx is also responding correctly there at least.

This happens every time I rebake posts too

sudo -E -u cloudron bundle exec rake posts:rebake

i Had the same issue... but still works at ubuntu 20.04

I have edited https://docs.cloudron.io/guides/upgrade-ubuntu-22/#post-upgrade further that should fix the collectd issue. If you run /home/yellowtent/box/scripts/init-ubuntu.sh, I think collectd should get installed properly.

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

@amg It seems there are multiple issues here:

Restore via CLI not working. Can you tell me more what the error is? Where are you seeing 'Already Setup'? Is this when installing Cloudron? (But the post starts with 'after update' to 3.4)

Please give us more information to help you out.

@CarbonBee Did I understand correctly that the DNS of cloudron A and Cloudron B are different above?

If so, the behavior is expected (not saying it is correct or even good). Currently, there is no easy way to easily 'migrate' domains - it is only easy to migrate a Cloudron from one server to another provided that all the DNS remains the same.

Can you explain your use case a bit more so we can try to come up with a solution together? I guess you are trying to test your backups? How can we make this work when Cloudron has multiple domains? Once you restore to another server, Cloudron will do the DNS setup of apps automatically and it will end up re-configuring the DNS of the apps to point to this new server.

@robw Sorry for the delayed response, we are just coming back from vacation and catching up on support tickets.

If I understand correctly, the Cloudron server has a different outbound IP than the one it detects. We have a custom endpoint (https://api.cloudron.io/api/v1/helper/public_ip) which helps us detect the IP of a server but I guess this detection goes wrong because of your setup.

To fix/workaround this: In the domain setup wizard, you can simply choose "no-op" as the DNS provider. With this provider, all DNS checks are disabled and as long as the domain somehow is able to resolve and reach your cloudron, it should all work. Another thing is that port 80 needs to be reachable as well for Let's Encrypt to work. If this is not possible, you can select 'Self Signed Certs' in the Advanced section of the domain UI.