# After update tot 3.2.5 HTTP 500 when creating a new report and when opening an old one

**URL:** <https://forum.mautic.org/t/after-update-tot-3-2-5-http-500-when-creating-a-new-report-and-when-opening-an-old-one/19517>\
**Category:** Product Support\
**Created:** [May 19, 2021, 11:07am UTC](https://forum.mautic.org/t/after-update-tot-3-2-5-http-500-when-creating-a-new-report-and-when-opening-an-old-one/19517 "2021-05-19T11:07:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ascholten](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/ascholten/32/691_2.png) [@ascholten](https://forum.mautic.org/u/ascholten)\
**Post date:** [May 19, 2021, 11:07am UTC](https://forum.mautic.org/t/after-update-tot-3-2-5-http-500-when-creating-a-new-report-and-when-opening-an-old-one/19517/1 "2021-05-19T11:07:20Z")

</div>

**Your software**  
My Mautic version is: 3.2.5  
My PHP version is: 7.4.16  
My Database type and version is:

**Your problem**  
My problem is: After upgrading to 3.2.5 I can’t open reports nor create new reports. Internal server error 500 in Chrome, incognito, Edge. In Firefox a blank page.

These errors are showing in the log: none

Steps I have tried to fix the problem:

> **[Update Failed](https://docs.mautic.org/en/troubleshooting/update-failed?_ga=2.235829697.1110435217.1621421208-1177493923.1621421208)**
>
> . Sometimes when updating Mautic, the process might stall or fail part way through. This can cause a problem, because it can cause Mautic to be inbetween two versions and often this can make the system unusable.The following processes can be followed...

search forum

---

<div class="post-metadata">

**Author:** ![ascholten](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/ascholten/32/691_2.png) [@ascholten](https://forum.mautic.org/u/ascholten)\
**Post date:** [May 19, 2021, 1:33pm UTC](https://forum.mautic.org/t/after-update-tot-3-2-5-http-500-when-creating-a-new-report-and-when-opening-an-old-one/19517/2 "2021-05-19T13:33:56Z")

</div>

Could it be related to?

> [@Landing pages throwing 500 error after upgrade to 3.0.2 from 2.16](https://forum.mautic.org/t/landing-pages-throwing-500-error-after-upgrade-to-3-0-2-from-2-16/15421/6):
>
> Also got the same 500 error on landing pages (upgraded from Mautic 2.16 or newly created in Mautic 3) after upgrading to Mautic 3.0. Editing worked but view/ preview generated errors just like you report. Have rolled back update to v2.16.

> <https://github.com/mautic/mautic/pull/9795>
>
> | Q | A
> | --------------------------------…------ | ---
> | Branch? | "features" for all features, enhancements and bug fixes (until 3.3.0 is released) 
> | Bug fix? | yes
> | New feature? | no
> | Deprecations? | no
> | BC breaks? | no
> | Automated tests included? | no
> | Related user documentation PR URL | mautic/mautic-documentation#... 
> | Related developer documentation PR URL | mautic/developer-documentation#... 
> | Issue(s) addressed | Fixes https://github.com/mautic/mautic/issues/9762 
> 
> \<!--
> Additionally (see https://contribute.mautic.org/contributing-to-mautic/developer/code/pull-requests#step-5-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 "features" branch.
> \--\>
> 
> \<!--
> Please write a short README for your feature/bugfix. This will help people understand your PR and what it aims to do.
> \--\>
> \#### Description:
> Scenario 1: 
> \- Load the PR
> \- Try to create an email (with segment) and edit it.
> \- You should see the errors mentioned in https://github.com/mautic/mautic/issues/9762
> \- This PR fixes it.
> 
> Scenario 2:
> Comment: https://github.com/mautic/mautic/pull/9795#issuecomment-834018754
> 
> Scenario 3:
> Comment: https://github.com/mautic/mautic/pull/9795#issuecomment-810740477
> 
> \<!--
> 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:
> 1. Load up \[this PR\](https://mautibox.com)
> 2. 
> 
> \<!--
> If you have any deprecations, list them here along with the new alternative.
> If you have any backwards compatibility breaks, list them here.
> \--\>

---

<div class="post-metadata">

**Author:** ![alexhammer](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/alexhammer/32/14525_2.png) [@alexhammer](https://forum.mautic.org/u/alexhammer)\
**Post date:** [May 19, 2021, 2:14pm UTC](https://forum.mautic.org/t/after-update-tot-3-2-5-http-500-when-creating-a-new-report-and-when-opening-an-old-one/19517/3 "2021-05-19T14:14:15Z")

</div>

The report functionality got changed since then.  
If you use the group functions with sum, avg etc then it can throw this error.  
But you can open the edit of the report directly.  
Just put [yourmautic.com/s/reports/edit/ID](http://yourmautic.com/s/reports/edit/ID)  
into the browser. (change [yourmautic.com](http://yourmautic.com) to your domain and ID to the Id of the report you want to change

---

<div class="post-metadata">

**Author:** ![ascholten](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/ascholten/32/691_2.png) [@ascholten](https://forum.mautic.org/u/ascholten)\
**Post date:** [May 19, 2021, 2:31pm UTC](https://forum.mautic.org/t/after-update-tot-3-2-5-http-500-when-creating-a-new-report-and-when-opening-an-old-one/19517/4 "2021-05-19T14:31:04Z")

</div>

edit doesn’t work unfortunately. HTTP 500 error

---

<div class="post-metadata">

**Author:** ![ascholten](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/ascholten/32/691_2.png) [@ascholten](https://forum.mautic.org/u/ascholten)\
**Post date:** [May 19, 2021, 8:17pm UTC](https://forum.mautic.org/t/after-update-tot-3-2-5-http-500-when-creating-a-new-report-and-when-opening-an-old-one/19517/5 "2021-05-19T20:17:18Z")

</div>

upgrading to 3.3.3 fixed the problem