@nebulon yeah, I also find having a clean extension-less vanilla install of Chrome at hand is useful for testing things too

@timconsidine said in Test installation refuse to install apps: @stoccafisso said in Test installation refuse to install apps: Fresh Ubuntu 18.04 server 18 ?? very old version On 31 May 2023, Ubuntu 18.04 LTS will reach the end of standard support. I thought that I read Cloudron no longer supports Ubuntu 18. Yeah, I was about to say the same. I'm pretty sure the latest version of Cloudron do not support Ubuntu 18.04 any more. @stoccafisso I'd recommend starting with a fresh 22.04! (or at least 20.04, but I see no reason not to start with 22.04)

Maybe search for "Hetzner" and "EACCES" - and thou shalt find....

it's just a SSD so around 500 MB/s

@makemrproper sorry, I marked the thread as solved I guess because there is nothing we can do here other than package the app at some point. For that, we have the App Requests thread - https://forum.cloudron.io/topic/1256/odoo-distributed-business-apps . Also, see https://forum.cloudron.io/topic/3343/sponsoring-odoo in the past. So, the solved here is simply that 'support' ticket is solved since there is nothing we can really do more.

Setting up under the wildcard option worked. Hopefully the wider issue with DigitalOcean will get resolved.

Are you able to login without 2fa yep - by setting up temporary password with cloudron cli tool Note that the ldap connector does not sync with a cron job, you have to press the sync button manually. Not valid - as otherwise I wouldn't be able to login with temporary password - user wouldn't exist. Manual sync - yes, sure. My logins worked up till I setup 2FA on admin on master server.

Ah .. ssdnodes can also be ip6 only. ip4 adds a fair chunk of money these days.

I had tried that before posting, but it failed. Turns out Vultr wants you to boot from a recovery disk to resize. Much faster (and no downtime) to just create new block storage and copy data over.

This is now fixed with https://git.cloudron.io/cloudron/box/-/commit/c8cd67258ad0329214e46b841de62e26e36842de

Well I'm kind of ashamed to say it but I gave up, I spent far too many hours on this one (felt like ~25 between the last three days) just on this one single issue in order to avoid an IP block for my clients as Microsoft was blocking the IP of the host machine, and I still couldn't get it to work. I eventually opted instead to create a new Public Cloud instance at OVH instead, migrated all the data to it, using the floating IP, and things seem to be working fine now (only accessible with one public IP address so Docker had no other choice, lol). Sorry there's no confirmed solution to this one.

Well then looks like OVH is not setting the DMI/SMBIOS values then properly. I guess there is not much to be done to remedy this from our side, unless some other metadata standard is used by them instead.

Fixed now for next release.

This is fixed now. The original issue is that the zone is added in Cloudflare but the nameservers of the domain are not set to Cloudflare. This makes Cloudflare return name_servers as empty in the response which makes our code crash.

@VictorMC26 There are two totally separate accounts. One is to access your server's dashboard to install and manage apps. This is via my.domain.com . The account you have here is local to your server. The other is cloudron.io account. This lets you manage billing/subscription. The screenshot you posted appears in the 'App Store' view in your server's dashboard on first time use. It is asking for this account's password. If you don't have one, you have to sign up. Once signed up, you can use the My Account link on the top right at https://www.cloudron.io/ to manage billing/invoices.

@nebulon I’m not sure I understand… if my server had 128 GB to set, why does Cloudron allow me to set nearly 256 GB? That doesn’t make sense to me.

There are some hard coded rate limits - https://docs.cloudron.io/security/#rate-limits

@nebulon It took a while to look into it - on my external facing URL it was my proxy & firewall that was blocking it. I switch to using the local IP & changed the Base DN as you mentioned & it is now pulling in users. Thanks for your help!

@ChicagoGregg said in Removing a domain produces an SQL error: Low of the totem pole. Low of the totem pole. Just use "least significant/important/crucial".