Cloudron Forum

Hi there,
migration of bookstack worked pretty quick for me, however this time its not synced with SSO, as we use this for documentation together with clients.

Therefore we add clients with as users to the app directly.

1. creating temporary domain for bookstack in cloudron,
2. checking that versions are in sync in old and cloudron instance,
3. copying bookstack /upload folder to the new instance (contains images in books etc.)
4. exporting database and importing it into cloudron as per: https://docs.cloudron.io/guides/import-mysql/
5. tested it, working fine
6. moving it to the final destination location.

Done.

Hi there,
short description, how I managed the migration of an existing Matomo instance to cloudron. It was a bit more tough, than migrating Yourls (https://forum.cloudron.io/topic/10737/migrating-yourls/10).

I didn't use any app specific migration, as I didn't want to kill any cloudron specific configurations.

These were the steps:

1. Making sure, Old Matomo had the same release level as the one in Cloudron.
2. Setting up Matomo on an intermediate domain in cloudron.
3. Merging Matomo config.ini.php manually - as it consists of data related to the application system setup, but also about our custom settings in Matomo. Also merging the plugin settings.
4. Moving Plugins folder to Cloudron.
5. Exporting old Matomo database, but leave out "user*" tables (we want to use the cloudron SSO login anyway) - but then also leave out "access" table (I forgot about this and had initially some trouble with collations and not working user management in Matomo).
6. Importing Matomo Export as described in https://docs.cloudron.io/guides/import-mysql/ (except we didn't drop any tables in Cloudron Matomo before). We only dropped tables we imported.

This should be the straight way to do it. With less trouble than I experienced

So far everything seems to work.

Ok, finally success. It was a lot more difficult, as our Mautic instance is more than 6 years old, started with Mautic version 2.x.x and had a lot of migrations in between.

Therefore biggest issues were the transfer of the database, which was MariaDB before and is MySQL now in cloudron.

I setup the user management with cloudron.

These were the steps:

1. Making sure, Old Mautic had the same release level as the one in Cloudron.
2. Setting up Mautic on an intermediate domain in cloudron.
3. Make sure, you leave mail settings to the app (see https://forum.cloudron.io/post/80364) if you plan to send via a different mail service provider. Those settings get overwritten with each restart, if you leave default mail settings to be managed by cloudron.
4. Merging Mautic config/local.php manually - as it consists of data related to the application system setup, but also about our custom settings in Mautic. Have a copy at hand from the original cloudron setup. Important - certain paths, like for cache, are links in cloudron, which will be added automatically at start of Mautic App. You can remove tmp and cache entries for the Mautic config.
5. Copying media, themes and custom plugins folders from old to new instance.
6. Try to do some maintenance with your database, e.g. run mautic:maintenance:cleanup, for my old database, I also removed page_hits, which were not linked to leads. Tried to get the database as small as possible. I also had some old collations for tables, like utf8 instead of utf8mb4, which is needed for some major tables, like leads, companies etc.
7. Exporting old Mautic database, if its MariaDB, make sure you export it with phpMyAdmin with compatibility settings activated (I used MySQL4 for the export).
8. Import mautic database into as described in https://docs.cloudron.io/guides/import-mysql/ - you can also drop tables from the existing cloudron Mautic database before, the relevant settings for user management are in the merged config file.
9. Clear cache for Mautic.
10. If you want to use single sign on, you probably need to delete those imported users from Mautic and let cloudron do its magic, when users logon the first time after migration with their cloudron user name.
11. Check all your settings - open leads, companies etc., have a look if everything is there.
12. Move the app to its new (old) location.
13. Test your mail settings (I needed to set them again, they got lost in the process, although added in the config file).
14. Increase your PHP Memory limit, if you have enough resources. Edit the php.ini in your cloudron folder and add this line (adjust as you like):

memory_limit = "2G";

That should be it. Also look into the discussion about cronjobs (https://forum.cloudron.io/topic/10255/adjust-cron-jobs-for-mautic-is-it-possible/11) to stay updated.

So far everything seems to work fine. Except I miss Alias Domains for now.

Node RED is not just about home automation. We use it regularly to integrate several Cloud Services.

Hi there,
I have certain usernames in my catchall domain that are 100% spam. I'm trying to filter them out using a custom SpamAssassin rule:

DELETE MISSLEADING CODE

However, those emails are still getting through. Also, it seems the score isn't being adjusted when I check the headers. Any ideas?

UPDATE:
Wrong approach. No custom rule needed. Just a regular one rule is needed. Adding to addresses into the "Custom Spamassassin rule" will do it.

Nothing more - Spamassassin will add 10 points to the score.

The initial code was an over engineered approach bei KI

For Hetzner... it looks like the PTR setting for an IPv6 is not checking if its correctly set. You will need to add the last piece - in my case "::1" - to the PTR record - even if Hetzner also accepts "::" only. I guessed this will cover the whole range - but I was wrong.

@micmc never ever upgrade from within the app
Especially not when you are using the managed version here in Cloudron.

Hi there @girish ...
Version 5.0.2 with bug fixes is supposed to be released today.

Those are helpful documents:

• https://github.com/mautic/mautic/blob/5.x/UPGRADE-5.0.md
• https://www.mautic.org/blog/community/mautic-5-beyond-expectations-beyond-limits

As I'm still pretty new to cloudron, how will you handle upgrades? I'm happy to jump in and to beta testing with migration of an existing Mautic Instance to version 5, if that helps.

@girish no that won't work, as the installation needs the central composer.json and also update it. It also loads more directories into the vendor directory, which is read-only in Cloudron. Did you come to some conclusion with your experiments?

Looks to me like the Mautic plugin concept doesn't work well with the Cloudron way of things.

Potential Scenarios:

1. Plugins should be installed with composer, a lot of directories and the central composer.json would need to be writable... not good.
2. Cloudron Mautic image would have some basic required plugins preinstalled, how to decide which? For me it would be (AWS)Mail, Custom Objects, Multi Domain plugins. Probably it would need to be different mailers. But this would increase maintenance, as plugins may have urgent updates outside of release cycles of Mautic.
3. Cloudron set up like WordPress (Dev) - like a preinstall but without continuous updates of core (because that would kill customizations). A little improvement, as the initial installation is fine and working (at least causing 50% of Mautic beginners trouble otherwise).
4. Cloudron self maintained on LAMP stack. Almost all the benefits of Cloudron lost.

Which other options did I miss?

Found the problem... Logo was in my OneDrive local folder, but not loaded locally. While OneDrive didn't run, it didn't download. Letting it appear that InvoiceNinja wouldn't finish.

Now it works!

Is the "not writeable" .styleci.yml causing other problems?

Hi,
is there a way we can easily setup a cloudron instance for a client, run it for a while and then hand it over to a clients own license? Like an agency model?

I have a subdomain, which - by mistake - linked to an old ip. Later it indexed a lot of wrong pages, not related to our domain.

I now want to remove it from google index and issue an error 410 for each calls to this subdomain. What would be the easiest way? Setting up a LAMP stack?

Or can this be done simpler?

Hi there,
as we are using some apps with partners and some only internally - can I force access control to not automatically default to "all users of this cloudron instance"?

I found the culprit - Simple LDAP Auth Plugin was deactivated. Not sure how (I?) caused it in the process.

Now I can confirm this way its working - moving yours from old server to cloudron, keeping existing URL. For all migrations, I started to move DNS management with the existing DNS records to be managed by cloudron.

1. setup yourls with directory user credentials in a temporary (sub)domain,
2. install your custom plugins (if you had any),
3. make sure, your plugins are activated, especially "Simple LDAP Auth Plugin",
4. make sure custom yourls settings in /app/code/user/config.php are the same like before (especially: YOURLS_URL_CONVERT and YOURLS_UNIQUE_URLS),
5. dump existing database from other installation and uploaded to /tmp,
6. drop existing tables from existing cloudron yourls db as per https://docs.cloudron.io/guides/import-mysql/,
7. import database dump, as described in the guide,
8. confirm your redirects are still working,
9. move yourls to the final location.

Done - without interruption, as DNS will switch from old server to cloudron, if you set DNS to be managed by cloudron.

Just fyi - Mautic 4.4.10 would also run with PHP8.0. With upcoming Mautic 5 also PHP8.1 will be supported.

Given that PHP7.4 (currently in use for Mautic Package) is longer EOL than 8.0 - would it make sense to upgrade the PHP version for the package?

Alright, after Contabo support confirmed, that they don't directly peer with Deutsche Telekom ... things didn't get better.

We now finally moved to Hetzner, which confirmed they do all the peering. I moved today with help of Cloudron. Was such a pleasure:

1. started backup on old server...
2. created virtual dedicated server (CCX33), which took <1 min in our existing client account
3. installed Cloudron on a fresh Ubuntu 24.04 LTS
4. waited for the backup to finish
5. copied the backup config file for restore into the new Cloudron instance, added password and passphrase
6. done in total effort of about 2h with 48 migrated apps...

Only some domains still pointed to the old server (with no running apps on them), which was fixed quickly and one custom app still needs some love.

Happy so far.
Network performance is a huge difference!

Pretty unexpected - while I was editing a page for a while, I was asked to reauthorize. Is there a timeout related to the session and is this not refreshed with each action?

Lost my editing and needed to restart.
Was it just a random error?

Perfect! Thank you - it works as expected.

We have years long experience with mautic

Its important to help with a default cronjob setup. The one from the docs work, but its not optimal. I will help setting it up in a better way together with you, if you like.

For now it would be good, if the out of the box setup for cronjobs in cloudron could also be disabled. I did it by commenting out every line in the crontab.system - but will this be replaced again by an update or not? Its in the /app/data directory. So I think it will not?

I already changed my cronjob setup with a shell file. I trigger this every minute, in case its still running, it will be ignored. I will need to extend it by other optional cronjob tasks - maybe having even two or more scripts. One to run every minute (if server can handle it). And then some maintenance task that don't need to run that often.

Update - the current version can now be found at:
https://github.com/twentyZen/mautic-cronjobs

Myself I'm not a script or Linux Professional. Probably that approach can be improved.

... good catch! Found out meanwhile there was a restart and my settings where also overwritten again. I thin I experienced this when configuring this instance already. But thought I probably just missed the save button. I will update my post with your input.