@scooke yes, you can mix between Cloudron's automation and manual DNS changes. In fact, that's the normal and only mode of operation. The automation is only adding and removing things that you would have to do normally outside Cloudron. For example, when you install an app, you have to setup A records. When you uninstall an app, you remove the A records. This is all the automation does. If you try to install an app in a location and there is already a DNS entry in your DNS provider, Cloudron will inform you of the same and let you 'overwrite' it or cancel the app installation. Same goes for email stuff. It sets up things like DKIM/SPF records automatically. These are updated carefully to not collide with existing entries. The MX record is only touch if you enable incoming Cloudron Email. Even in that case, there is a checkbox to not update DNS.

@eddowding If you like you can patch the file in /home/yellowtent/box/src/mail.js and systemctl restart box.

@fbartels Thanks, it working and solved my issue. @girish The issue was that I have not set the provider to No-op, while without this step it was unable to change the location of any apps. Thank you both for the support.

@ntnsndr You talking about Github Pages official, or the Cloudron app?

@molinaire did you get this sorted out? If not, I think maybe it's best sorted out by writing to us at support@cloudron.io

@marcusquinn Actually, SIM Swapping is pretty common. I would not suggest having a phone number as a single-point-of-failure for anything remotely critical.

@aziz So, certificate for *.devz.cloud is already there, so if you install apps on subdomain it will work. Cert for devz.cloud (it is not a subdomain, so we have to get a separate cert from the wildcard cert) is getting rate limited. You can just wait for 2-3 days to install an app on the bare domain and that should work. You should be able to install apps in subdomains in the meantime.

@girish thank you very much, I will do that

@nebulon said in Unable to install 2nd app: @khadanja from your forum account, I was able to trace it down and for some reason our state showed 2 installed apps. This sometimes happens, since we don't closely track our users. I have reset the state now, so can you try again? That worked. Thanks @nebulon

@ohault hi and welcome here. Other external auth providers are currently not supported and I don't think we have any plan to integrate this, at least this wasn't asked for in the past for the whole Cloudron as such. We have external LDAP syncing for larger organizations to avoid having to manually create user accounts on Cloudron though.

@roru2k20 great that you found this out and thanks for sharing here

@girish Oh sorry about that, I don't seem to have looked that closely for the topic so that I would have noticed it. I already thought that it has to do with the Let's Encrypt exchange. Thanks for that. My nextcloud has no error, only my banking app, but I would say it is the same reason and I must wait for an update.

@scooke Thank you very much! Bookmarked

@luckow Thanks! didn't know SoGo can too, updated my post!

Hi and welcome here @briankb What you say is correct, you can have multiple Cloudrons bound to the same cloudron.io account and those Cloudrons may have different subscription states.

@girish That'd be awesome, thanks Girish. I'll hope it's ready for this week though for everyone and that should fix it.

@manngobaum yes, this was a display bug. It's fixed in the upcoming release. Thanks for reporting.

@smokeyfro I replied from support@ earlier today but I am able to reach your dashboard just fine. Can you confirm? Not sure what changed but looks like you managed to fix this yourself. What did you have to do ?

@girish that's what I meant, the cmd ran always before, but now only in the rare case the directory isn't there