# Upgrade from MAUTIC 4.4.10 --\> 5.0.1 problem

**URL:** <https://forum.mautic.org/t/upgrade-from-mautic-4-4-10-5-0-1-problem/30494>\
**Category:** Mautic 5 Install/Upgrade Support\
**Created:** [January 15, 2024, 10:52am UTC](https://forum.mautic.org/t/upgrade-from-mautic-4-4-10-5-0-1-problem/30494 "2024-01-15T10:52:38Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![omert](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/omert/32/10732_2.png) [@omert](https://forum.mautic.org/u/omert)\
**Post date:** [January 15, 2024, 10:52am UTC](https://forum.mautic.org/t/upgrade-from-mautic-4-4-10-5-0-1-problem/30494/1 "2024-01-15T10:52:38Z")

</div>

**Your software**  
My Mautic version is: 5.0.1  
My PHP version is: 8.0.28  
My Database type and version is: MySQL 8.0.35

**Your problem**  
My problem is:  
After upgrade from 4.4.10 → 5.0.1 I’m getting red offline error message (see screenshot below) in the browser along with the ‘parameter x must be defined’ error(s) when running commands such as (doctrine:migrations:migrate) via CLI.  
I am currently running 4.4.10 again (restored from backup).

\*Had no problem upgrading from 2 → 3 and from 3 → 4 with all the intermediate stable version upgrades.

These errors are showing in the log:  
Browser:

 ![mautic_screenshot](https://us1.discourse-cdn.com/flex020/uploads/mautic/original/2X/a/a0b97757addd2cc57865d557df8e10a2ab14c83d.png)

When running commands from like (e.g. doctrine:migrations:migrate OR mautic:clear:cache) get multiple but same errors:

**In AppKernelProdContainer.php line xxxxx:**

\*\* The parameter “yyyyy” must be defined.\*\*

Steps I have tried to fix the problem:

- Tried moving local.php from app/config to config
- Tried chmoding (755) and chowning directory for www-data as usual  
\*Tried switching NGINX php-fpm from 8.0 to 8.1

Nothing worked.

---

<div class="post-metadata">

**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\
**Post date:** [January 15, 2024, 11:39am UTC](https://forum.mautic.org/t/upgrade-from-mautic-4-4-10-5-0-1-problem/30494/2 "2024-01-15T11:39:42Z")

</div>

Please share the logs from var/logs so we can help you figure out what’s going on. Thanks!

---

<div class="post-metadata">

**Author:** ![peter\_k](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/peter_k/32/511_2.png) [@peter\_k](https://forum.mautic.org/u/peter_k)\
**Post date:** [January 16, 2024, 12:12pm UTC](https://forum.mautic.org/t/upgrade-from-mautic-4-4-10-5-0-1-problem/30494/3 "2024-01-16T12:12:20Z")

</div>

@silavapi He did. Just boiled down to the relevant part. 🙂 (In fact, the log isn’t getting any more useful in this particular case)

> [@omert](#):
>
> \*\* The parameter “yyyyy” must be defined.\*\*

The config migration messed up your config. If you search for parameter `yyyy` you’ll find it in your `local.php` under the `mailer_dsn` key. That’s causing the issue.

To get your backend running again:

1. open `local.php`
2. look for `'mailer_dsn' => 'mautic.transport.`
3. comment that out
4. flush cache

Your backend should work now. **BUT:** Your email transport is **not** configured. You need to do that.

---

<div class="post-metadata">

**Author:** ![omert](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/omert/32/10732_2.png) [@omert](https://forum.mautic.org/u/omert)\
**Post date:** [January 18, 2024, 3:00pm UTC](https://forum.mautic.org/t/upgrade-from-mautic-4-4-10-5-0-1-problem/30494/4 "2024-01-18T15:00:23Z")

</div>

According to this:

> **[Release Mautic Community 5.0.2 · mautic/mautic](https://github.com/mautic/mautic/releases/tag/5.0.2)**
>
> What's Changed
> 🐛 Bugs
> 
> DPMMA-375 fix multiple flash messages by @patrykgruszka in #13187
> Fixing Undefined project root by @escopecz in #13193
> fix: \[DPMMA-2252\] point groups migration fix by @patryk...

This:

> <https://github.com/mautic/mautic/pull/13195>
>
> \<!-- ## Which branch should I use for my PR?
> 
> Assuming that:
> 
> a = current ma…jor release
> b = current minor release
> c = future major release
> 
> \* a.x for any features and enhancements (e.g. 5.x)
> \* a.b for any bug fixes (e.g. 4.4, 5.1)
> \* c.x for any features, enhancements or bug fixes with backward compatibility breaking changes (e.g. 5.x) --\>
> 
> | Q | A
> | -------------------------------------- | ---
> | Bug fix? (use the a.b branch) | \[Y \]
> | New feature/enhancement? (use the a.x branch) | \[N \]
> | Deprecations? | \[N \]
> | BC breaks? (use the c.x branch) | \[\]
> | Automated tests included? | \[\] 
> | Related user documentation PR URL | mautic/mautic-documentation#... 
> | Related developer documentation PR URL | mautic/developer-documentation#... 
> | Issue(s) addressed | Fixes #12993 
> 
> \<!--
> Additionally (see https://contribute.mautic.org/contributing-to-mautic/developer/code/pull-requests#work-on-your-pull-request):
> - Always add tests and ensure they pass.
> - Bug fixes must be submitted against the lowest maintained branch where they apply
> (lowest branches are regularly merged to upper ones so they get the fixes too.)
> - Features and deprecations must be submitted against the "4.x" branch.
> \--\>
> 
> \#### Description:
> This PR fixes the issue with point groups migration
> \<!--
> Please write a short README for your feature/bugfix. This will help people understand your PR and what it aims to do. If you are fixing a bug and if there is no linked issue already, please provide steps to reproduce the issue here.
> \--\>
> 
> \#### Steps to test this PR:
> 
> \<!--
> This part is really important. If you want your PR to be merged, take the time to write very clear, annotated and step by step test instructions. Do not assume any previous knowledge - testers may not be developers.
> \--\>
> 1. Open this PR on Gitpod or pull down for testing locally (see docs on testing PRs \[here\](https://contribute.mautic.org/contributing-to-mautic/tester))
> 2. Run \`ddev exec php bin/console doctrine:migrations:migrate\`
> 
> \<!--
> If you have any deprecations, list them here along with the new alternative.
> If you have any backwards compatibility breaks, list them here.
> \--\>

And this:

> [@Mautic upgrade to 4.4.10 -\> 5.0.1 breaks](https://forum.mautic.org/t/mautic-upgrade-to-4-4-10-5-0-1-breaks/30440):
>
> Your software Mautic 4.4.10 upgrading to Mautic 5.0.1 PHP: tried both 8.0.30 and 8.1 Your Problem Upgrading leads to error message I used the command line upgrade path to upgrade from 4.4.10 → Mautic 5.0.1, but once the upgrade was complete, I receive ubiquitous error messages from any page. So I blew away Mautic entirely and re-installed: Download Mautic 5.0.1 Upload to server Unzip into public\_html directory Ensure file/directory ownership is set appropriately Upload local.php file to …

Would it be a safe bet to assume that this issue has been resolved in the “freshly baked” version 5.0.2 ?

I’m kind of reluctant to try… 🙂

---

<div class="post-metadata">

**Author:** ![chrish](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/chrish/32/522_2.png) [@chrish](https://forum.mautic.org/u/chrish)\
**Post date:** [January 19, 2024, 3:57am UTC](https://forum.mautic.org/t/upgrade-from-mautic-4-4-10-5-0-1-problem/30494/5 "2024-01-19T03:57:34Z")

</div>

Yes! I’m back in business!

To be fully transparent: I attempted to incorporate the proposed fix into my 5.0.1 installation, but it was still broken after I tried it. My day job is NOT in computer science, so I assumed it was a break based on my ignorance of the appropriate procedure. Now that 5.0.2 has been released, I tried again with it, and it worked for me. Specifically, my workflow was:

1. Install Mautic 5.0.2.php bin/console doctrine:migration:status
2. Upload my backed-up SQL into the appropriate database.
3. Copy the 4.x configuration file (local.php) into the correct place for 5.0. Note that the directory location changed!
4. php bin/console doctrine:migration:status ← to identify the need to migrate the db
5. php bin/console doctrine:migration:migrate ← to actually migrate

and now I can log in and do all the things Mautic. Please note there are also cron job changes, and I haven’t fully addressed that just yet.

---

<div class="post-metadata">

**Author:** ![omert](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/omert/32/10732_2.png) [@omert](https://forum.mautic.org/u/omert)\
**Post date:** [January 21, 2024, 7:48am UTC](https://forum.mautic.org/t/upgrade-from-mautic-4-4-10-5-0-1-problem/30494/6 "2024-01-21T07:48:46Z")

</div>

So I noticed a 4.4.11 upgrade recently…  
Performed the upgrade…  
Upgrade from 4.4.10 to 4.4.11 went by smoothly it seems.  
Now 5.0.2 is available again.  
Should I take the risk and upgrade?

---

<div class="post-metadata">

**Author:** ![mzagmajster](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/mzagmajster/32/687_2.png) [@mzagmajster](https://forum.mautic.org/u/mzagmajster)\
**Post date:** [January 22, 2024, 8:26am UTC](https://forum.mautic.org/t/upgrade-from-mautic-4-4-10-5-0-1-problem/30494/7 "2024-01-22T08:26:12Z")

</div>

Just make a full backup of mautic (database + source) before.

---

<div class="post-metadata">

**Author:** ![omert](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/omert/32/10732_2.png) [@omert](https://forum.mautic.org/u/omert)\
**Post date:** [January 22, 2024, 8:57am UTC](https://forum.mautic.org/t/upgrade-from-mautic-4-4-10-5-0-1-problem/30494/8 "2024-01-22T08:57:57Z")

</div>

That still doesn’t seem to work.  
I am now on 5.0.2.  
Still getting the red “offline” message.

---

<div class="post-metadata">

**Author:** ![omert](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/omert/32/10732_2.png) [@omert](https://forum.mautic.org/u/omert)\
**Post date:** [January 22, 2024, 9:11am UTC](https://forum.mautic.org/t/upgrade-from-mautic-4-4-10-5-0-1-problem/30494/9 "2024-01-22T09:11:17Z")

</div>

How would I go about defining my amazon ses api transport in this?

---

<div class="post-metadata">

**Author:** ![abs](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/abs/32/10663_2.png) [@abs](https://forum.mautic.org/u/abs)\
**Post date:** [January 26, 2024, 9:24am UTC](https://forum.mautic.org/t/upgrade-from-mautic-4-4-10-5-0-1-problem/30494/10 "2024-01-26T09:24:17Z")

</div>

I had a nightmare trying to get Amazon SES to work after an upgrade to 5.0.2

1. The upgrade resulted in a broken setup due to the migrated mailer\_dsn containing %…%, had to remove the mailer\_dsn line from local.php
2. I installed symfony/amazon-mailer, but it gave an unrecognised schema error in the config page. You need to install a specific version - “composer require symfony/amazon-mailer=5.3 -W”
3. Pasting in the password to the email config page leaves the cute little lock emoji in the field by default, resulting in the wrong password being saved. Make sure you clear the lock (why is not a placeholder attribute?)

Anyway, I now have Mautic 5.0.2 running with Amazon SES, but it seemed to be much harder than it needed to be

---

<div class="post-metadata">

**Author:** ![mzagmajster](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/mzagmajster/32/687_2.png) [@mzagmajster](https://forum.mautic.org/u/mzagmajster)\
**Post date:** [January 26, 2024, 11:13am UTC](https://forum.mautic.org/t/upgrade-from-mautic-4-4-10-5-0-1-problem/30494/11 "2024-01-26T11:13:59Z")

</div>

But does this symfony amazon mailer properly handle bulk sending. There is a reason why mautic has dedicated transports to integrate with different email providers and its because using default mailer packages makes separate request to an api for each message.

---

<div class="post-metadata">

**Author:** ![abs](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/abs/32/10663_2.png) [@abs](https://forum.mautic.org/u/abs)\
**Post date:** [January 26, 2024, 3:35pm UTC](https://forum.mautic.org/t/upgrade-from-mautic-4-4-10-5-0-1-problem/30494/12 "2024-01-26T15:35:29Z")

</div>

For our usage I expect the standard symfony Amazon SES integration with an API call per message will be performant enough (We can always look to move to a queuing later if needed).

For others moving to the new mailer integration in Mautic 5 may be more of an issue. We just wanted it to be able to work at all 🙂

---

<div class="post-metadata">

**Author:** ![binnykt](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/binnykt/32/11865_2.png) [@binnykt](https://forum.mautic.org/u/binnykt)\
**Post date:** [April 23, 2024, 9:15am UTC](https://forum.mautic.org/t/upgrade-from-mautic-4-4-10-5-0-1-problem/30494/13 "2024-04-23T09:15:48Z")

</div>

Hi There,

Can you please post the steps you followed to upgrade Mautic from 4 to 5.