This has been fixed now with https://git.cloudron.io/cloudron/box/commit/2bde023d4dc783761553a0a7be88650e5885b4ad and should be part of the next release.

@msbt d'oh! That worked, I was able to delete the app successfully after manually (and with sudo) deleting the contents of that directory.
@girish that directory contained an empty data directory and that's it. Hope that helps debugging!

@PRajShar To clarify what this error is trying to say: Let's assume that you have an existing website app (i.e external to Cloudron) on app.domain.com. Now, you go to Cloudron and try to install an app in the domain app.domain.com. Cloudron will detect that the DNS already has an entry for this and fail with the above error. To fix this, go to your DNS provider and remove the app.domain.com entry. Then in Cloudron, click the Repair (wrench icon) and it should work.

Alternately, just use another subdomain app2.domain.com or something.

@subven Have you read https://docs.microsoft.com/en-us/office365/securitycompliance/use-the-delist-portal-to-remove-yourself-from-the-office-365-blocked-senders-lis ?

You should be able to get your specific IP delisted.

Yes, the post @d19dotca linked will have the explanation.

Yes it also shows email storage details

Thanks @girish, that makes sense. I need to migrate TTRSS and Wallabag which should be pretty trivial I believe. The one I'm worried about is Nextcloud because I have some plugins and settings configured just how I want them.

@TheNils If you think it's worth getting those apps published, please join our chat at https://chat.cloudron.io if you have any questions 🙂

@hoangweb the initial installation should work if you have logged into the appstore in your Cloudron dashboard.

For the latter issue about the dev group permission, this is because we currently have to limit access to our app package build service to build custom packages. But since you appear to install the regular WordPress app using the --appstore-id I think the build should not be necessary anyways.

thanks @msbt !

I’m having some similar thoughts about restoring / migrating Cloudron as @d19dotca .

So it is possible to set up Cloudron on different primary domains (or IPs) but still keep the same subscription.

The use-case I’m aiming for is just to serve the code closer to the readers / users. Will the apps on one Cloudron appear on the other Cloudron? @girish

As an update, I found this post solved the issue https://forum.cloudron.io/topic/1819/wordpress-unmanaged-re-directions-unable-to-install/4

I have example.com for the primary domain & my.example.com for Cloudron admin.

For the Ghost app, it is ghostexample.com. At first visit, it showed me the Cloudron login page. This was fixed after a while. The www.ghostexample.com going to admin page was fixed by removing CNAME & adding redirect.

Thanks for the support!

That would work! Thank you for clarifying this for me. Cheers!

@vjvanjungg https://www.netcup.eu/ (English)

I guess this should come in as an nginx update via ubuntu at some point. We don't package nginx ourselves.

@girish I have a project I've been working on, and although it doesn't do exactly that, it can modify files in a single containers filesystem:

https://github.com/mitchellurgero/cloudron-codiad

And the code for the webapp:

https://github.com/mitchellurgero/codiad

This has been resolved with https://git.cloudron.io/cloudron/box/issues/646

Okay then, I understand. Thank you @subven @nebulon for you guys responses!

Okay I think my request is already solved since I did not read the documentation. I will check the "is an external EXT4 Disk" checkbox for the future 😉 Maybe I did not think it through when I made the setting. On the other hand, the description might be clearer. Thanks in any case for the documentation.

PS: Haha thank you @nebulon I solved it myself while you where typing. Yes the Checkbox could be more obvious.

@necrevistonnezr That is true, however the configuration steps are different than what has been described before when trying to work around this issue.