Merci beaucoup!

For others looking for examples, there's a bunch of custom app templates I made that should help getting started: https://git.cloudron.io/cloudron/tutorial-php-app/ https://git.cloudron.io/cloudron/tutorial-nodejs-app https://git.cloudron.io/cloudron/tutorial-basic https://git.cloudron.io/cloudron/tutorial-redis https://git.cloudron.io/cloudron/tutorial-supervisor-app

@jdaviescoates said in How install wordpress with www?: Quite possible I just didn't wait long enough too I guess... I think that was it. I actually first tried just adding www redirect again to my WordPress at https://uniteddiversity.coop and waited a bit before trying it and it works fine. Sorry, should've been more patient in the first place!

We will fix the pricing page, I agree it's a bit misleading.

@valkalon Cloudron support is still the best

I think there's a genuine case in the future where if we introduce per-app admins, then app admin can access terminal of one app to see traffic (and sniff ldap/db creds) of another app. I think it's an excellent suggestion to remove it!

@girish Ah interesting, yes that definitely seems like an OVH-specific issue then. At least they're heading in the right direction I guess towards the end of this year. Thanks for shedding some light on that one for me.

@necrevistonnezr They are pretty much the same feature. Cloudron's works at the platform level for all apps including nextcloud itself whereas nextcloud's will work only for nextcloud.

@necrevistonnezr indeed, previous versions of Cloudron would allocate more memory for redis based on the app's memory limit. This limit was not settable by the user. In 5.2, we have made the redis limits visible and configurable by the user. Our 5.2 migration script should ideally could have been smarter and allocated more memory to redis.

@Felix Did you manage to install it?

correct in your case this should not be any issue as this is mounted like a regular ext4 which supports hardlinks just fine.

@Mallewax I think this depends on the webmail app, more than on the platform itself. Not totally sure though, I am not particularly familiar with the inner workings of the email protocols

Yeah, had to do a fresh install. It all worked out in the end.

@ruihildt Thanks for reporting. This is fixed in the coming release - https://git.cloudron.io/cloudron/box/-/blob/master/CHANGES#L1930

@girish So, it was the TLS. Changed it to 1.2 and the requests went smooth and fast. Thanks for the tips

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

Correct, those "providers" are two different ones conceptually. One is where the server is hosted. This allows us to apply some VPS provider specific quirks, if required. The DNS/Domains provider is the one where the domain is registered or at least the nameservers for that domain. This may or may not be the same company as the VPS provider, but they have otherwise nothing in common.

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