@cdrm the shared LDAP is available from 7.6.4 in all plans.

Hi @mazarian, in /home/yellowtent/platformdata/logs you will the file box.log, which should give an indication of what went wrong during your restore. I did not check what the documentation says about this, but earlier this week I performed a restore in a similar manner to you and watching the dashboard during the restore there was definitely some parallel activity going on during the restore. I would have said that it was probably something like two or three apps at the same time max.

Nope, there's no AAAA record, just an "A+ Dynamic DNS Record" Incidentally, I'm about to switch this domain to Hetzner, in any event. Namecheap is ok but also quite annoying from time to time...

Attempting to get a password reset yielded no results, however the create account at the homepage is working so there is that. I wonder why it wouldn't let me create the account in the setup? Either way, I think I will be able to move forward. Thank you again!

I run "sync dns" again, now it looks fine, strange.

Hello I wanted to apologize for the lack of response, as right after I posted this had a family emergency and the holidays and it completely vanished from my mind. I want to confirm that Port Forwarding was the kicker, as I was following a Doc for Guacamole install instead of Cloudron's full doc for the base install, there were no instructions in the Guac doc to do port forwarding. Thank you so much!

@nebulon said in Backup Error Message: Maybe the mountpoint went away/got disconnected while the backup was running? yes, I totally forgot, that Cloudron runs not at Home, so I need to adjust my backup time window

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