Cloudron Forum

As @scooke and @mehdi already mentioned, the sole reason to support only one distribution is the reduced complexity by having to deal with only a single well known system. Even different ubuntu versions require quite a lot of testing and different code. Sometimes package names change for example. We essentially just settled on Ubuntu 16.04 initially since that was available on basically every VPS provider. Really that is the main concern for us. Naturally for security updates we then progressed to 18.04 and will soon hopefully support 20.04. Other distros with even other package managers are simply just overhead and cause trouble to users. In the end from what Cloudron requires, there will hardly be any noticeable difference in speed or resources use between any of the distros, so we lean towards stability here.

@mehdi Not sure I know enough yet about handling updates, patches & security so just running in good faith on all that at the mo.

Happy? Yes.

Confident? Sure - until something goes wrong 🙂

Just always thinking about prevention being better than cure.

Thanks, Girish,
That patch worked. I've successfully setup things.
cheers
Mark

@grimm1369 Let's continue this further at https://forum.cloudron.io/post/44414

@Felix Did you manage to install it?

@girish Thanks for the assistance.

Apparently this was caused by a misconfigured IPv6 / Ubuntu installation script which my host helped me diagnose and correct. Thank you for your help, I'm glad I stumbled upon Cloudron.

The netcup image for VPS, Root and Dedicated servers is still there and working. "Latest" would be Ubuntu 20.04 but the image is still based on Ubuntu 18.04 with is fine. The Cloudron version will always be latest because of the auto update on installation. I'm using Netcup and the image on various cloudrons and never had an issue so you should be fine.

I think you're right, it took a while to propogate fully.

@cyanogenic Did you install/enable any nextcloud plugins? This usually happens when one of the nextcloud plugins is not too happy. Try this https://cloudron.io/documentation/apps/nextcloud/#fixing-a-broken-install . Or if you have nothing important in it, I would just re-install nextcloud.

@leahcim37 are there any errors in /var/log/cloudron-setup.log ? When you say it installed but it failed, what do you mean?

Thanks all!

I just installed it on 1 of my Cloudron servers (at DO) to see and experience if and how it works.

Hi @derek sorry for the delayed answer, did you manage to solve this after the TTLs have expired from your attempts?

@randyisscott I'm not entirely sure if the article I saw on https://www.proxies.com/ipv6 is attending to my question. I don't think I need all the additional trusted domains and trusted proxies stated there. Trusted domains are meant to tell nextcloud to allow access when you access it at cloudxxx or by IP address. They also have a duplicate in there, probably need to remove that. Trusted proxies I believe should only list the IP address of the proxy server, nothing else. I'm not sure if that affects the redirect loop but I would start there.

Hi @abasitali Cloudron will attempt to resolve the DNS records with regards to the public IP address. Since you said you have an internal DNS server and hosting on-premise, can you give a bit more information about the setup? It could also help if you send a quick mail to support@cloudron.io with mentioning the domain, if you don't want to have it publicly known here, that way we can maybe see if things resolve correctly from our side.

If this is not a public server, please checkout the docs at https://cloudron.io/documentation/networking/#private-dns

@homo for the easiest experience, i would sign up at https://www.digitalocean.com/ . Cloudron is available as a 1-click image in the marketplace. So, you don't have to install it at all.

https://forum.cloudron.io/topic/7193/unable-to-install-cloudron/3?_=1654970145198. Please help me with this topic. A bit similar to this topic.