updates are always only tested in sqeuence. But for testing I guess you can clone the app and manually update through the next package versions till 4.0.3. Basically update to 4.0.0 then check for updates and update again until 4.0.3

@girish said in Mautic 5 Upgrades Failing: @Dave-Swift The second error is open upstream at https://github.com/mautic/mautic/issues/12993 . The first one probably needs to be reported upstream as well. Do you have a complete log of the first error? Experiencing the same thing, yeah there might be a need for a few adjustment with a major update as such. So here's essentially what shows up in the log and Mautic is actually not responding, and trying to restart it will respond the same as this in the log: Jan 18 10:26:07doctrine:migrations:migrate [--write-sql [WRITE-SQL]] [--dry-run] [--query-time] [--allow-no-migration] [--all-or-nothing [ALL-OR-NOTHING]] [--configuration CONFIGURATION] [--em EM] [--conn CONN] [--] [<version>] Jan 18 10:26:07In Connection.php line 70: Jan 18 10:26:07In Exception.php line 28: Jan 18 10:26:07In ExceptionConverter.php line 45: Jan 18 10:26:07 An exception occurred while executing a query: SQLSTATE[42S01]: Base table Jan 18 10:26:07 SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'point_group Jan 18 10:26:07 SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'point_group Jan 18 10:26:07 or view already exists: 1050 Table 'point_groups' already exists Jan 18 10:26:07 s' already exists Jan 18 10:26:07 s' already exists Jan 18 10:26:07[error] Migration Mautic\Migrations\Version20230621074925 failed during Execution. Error: "An exception occurred while executing a query: SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'point_groups' already exists" Jan 18 10:26:07[2024-01-18 16:26:07] [notice] Column lead_points_change_log.group_id already exists Jan 18 10:26:07[2024-01-18 16:26:07] [notice] Column point_triggers.group_id already exists Jan 18 10:26:07[2024-01-18 16:26:07] [notice] Column points.group_id already exists Jan 18 10:26:07[2024-01-18 16:26:07] [notice] Table plugin_citrix_events already exists Jan 18 10:26:07[2024-01-18 16:26:07] [notice] Table point_group_contact_score already exists Jan 18 10:26:07[2024-01-18 16:26:07] [notice] Table point_groups already exists Jan 18 10:26:07[2024-01-18 16:26:07] [notice] Migrating up to Mautic\Migrations\Versionzz20230929183000 Jan 18 10:26:07[2024-01-18 16:26:07] [notice] Migration Mautic\Migrations\Version20221128145933 skipped during Pre-Checks. Reason: "Schema includes this migration" Jan 18 10:27:10=> Healtheck error: Error: connect ECONNREFUSED 172.18.18.22:8000 Jan 18 10:27:12[2024-01-18 16:27:12] Jan 18 10:27:12[2024-01-18 16:27:12] Jan 18 10:27:12[2024-01-18 16:27:12] [WARNING] You have 183 previously executed migrations in the database that are Jan 18 10:27:12[2024-01-18 16:27:12] not registered migrations. It seems like the installation process attempts to create new tables and columns several times...

@girish said in PHP8.0 is supported for Mautic 4.4.10: I have managed to update the package to Mautic 5 but the LDAP plugin needs to be updated because of upstream changes. Looking into this. Any update on that one pal? Looking forward for that update, with Composer and access to the marketplace etc. Take care. Thanks.

@Dave-Swift in this case, those would be one and the same.

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

Perfect! Thank you - it works as expected.

Yep, Mautic is not yet clean enough in separating data from application code. We learnt it when trying to build containers in the past. Thanks for the fix!

https://www.mautic.org/blog/community/announcing-mautic-developer-days-and-community-sprint-vienna-july-19-21 cu next week in Vienna?

@Aizat Yes, that should work.

@girish Amazing! The new update has fixed the above described problem and we have been able to update and are now running version 4.4.2 of Mautic. Great job! Thanks.

@girish Nan, forget the above I'd made a little more research in the forum and found the solution here, thanks anyway.

@girish Thank you!

@girish Nice!!! thanks

@thibaud I think just to keep things simpler, please check if just simple mautic API works using curl. By OAuth, I guess you mean the Mautic's "OAuth2" i.e the one described in https://www.mautic.org/blog/developer/how-to-use-the-mautic-rest-api ? I have no clue how that works... But for our own mautic automation, we first enable the API like this: [image: 1648787601477-aa2a6977-cc24-4ed9-8b6a-491a1e63955b-image-resized.png] Then, we use http basic auth. We then created a separate user called mauticbot (added straight inside mautic). We then use https://github.com/vdavid/node-mautic to automate. That module just uses the account username and password and no API token.

Same here, problem solved. Thanks!

@rmdes Nice implementation! Unfortunately it also relies on manually adding the html instead of the javascript which would automatically update fields without having to touch the code on the backend of the website.

@nebulon I deleted the theme that was throwing an error (even though it was not in use) and that for some reason fixed it