# Just Upgraded to Latest Version of Local and Now Get 500 Internal Server Error **URL:** \ **Category:** Support\ **Tags:** mac\ **Created:** [October 22, 2023, 5:17pm UTC](https://community.localwp.com/t/just-upgraded-to-latest-version-of-local-and-now-get-500-internal-server-error/39660 "2023-10-22T17:17:42Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![PLD](https://avatars.discourse-cdn.com/v4/letter/p/8baadc/32.png) [@PLD](https://community.localwp.com/u/PLD)\ **Post date:** [October 22, 2023, 5:17pm UTC](https://community.localwp.com/t/just-upgraded-to-latest-version-of-local-and-now-get-500-internal-server-error/39660/1 "2023-10-22T17:17:42Z")
### What issue or error are you experiencing? ## I’ve been using Local now for several months and just upgraded to Version 8.0.1+6490. Now, when I make changes to my website and try to publish, I get a 500 Internal Server Error. I’ve made no other changes and have not installed any new plugins. This happened immediately after I upgraded. ### What steps can be taken to replicate the issue? My only plugins are Elementor, Elementor Pro, WPForms Lite, and WP Mail SMTP. I tried deactivating these sequentially, except for Elementor, but nothing worked. I also resaved my Permalinks without making any changes, as directed by a YouTube video I watched on this. I’m on a MacBook Pro using Ventura 13.6 I’m stumped (and also new at this). Is there a way to revert back to the version of Local that worked for me? Any other suggestions, please? Thank you. ---
**Author:** ![nickc](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nickc/32/21209_2.png) [@nickc](https://community.localwp.com/u/nickc)\ **Post date:** [October 23, 2023, 12:05pm UTC](https://community.localwp.com/t/just-upgraded-to-latest-version-of-local-and-now-get-500-internal-server-error/39660/2 "2023-10-23T12:05:27Z")
Sorry that you encountered this, @PLD! Have you tried restarting Local or your device after the upgrade? (I’m on Ventura too and cannot reproduce the 500 error with Local 8.0.1 so far.) If that doesn’t help, before you downgrade, please could you share your Local Logs with us so that we can investigate? You can get a zip of your logs by clicking “Download Local Log” from the “Support” tab in Local. See this help doc for more information: > **[Retrieve Local’s Log File](https://localwp.com/help-docs/troubleshooting/retrieving-locals-log-file/)** > > A big part of troubleshooting errors, on any website or application, is the log file. This file contains a record of actions or errors that have occurred when a process is done. When reaching out for… Once you’ve done that, you can downgrade by following the steps here: > **[Downgrade Local Version](https://localwp.com/help-docs/troubleshooting/downgrade-local-version/)** > > Downgrading Local may be used to troubleshoot issues presented with a newer version or other various reasons. We recommend running Local on the latest version available when possible. ---
**Author:** ![PLD](https://avatars.discourse-cdn.com/v4/letter/p/8baadc/32.png) [@PLD](https://community.localwp.com/u/PLD)\ **Post date:** [December 26, 2023, 10:05am UTC](https://community.localwp.com/t/just-upgraded-to-latest-version-of-local-and-now-get-500-internal-server-error/39660/3 "2023-12-26T10:05:58Z")
Thank you, @nickc I have no idea how this occurred or what happened, but I got this message: Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /Users/-----/Local Sites/-----/app/public/wp-includes/meta.php on line 1194 Thank you, @nickc Lots of info on the web about increasing memory in the wp-config.php and/or the .htaccess file but none of this worked for me. In the middle of this, I bought a new MacBook Air M2 with 16 GB of memory and Sonoma 14.1.2. The problem persisted. Finally, I changed the php.ini.hbs file. All it took was to change memory\_limit = 256M to memory\_limit = 512M in this file and the error went away. I am back in business and I hope this helps someone else. Thank you for your help and advice. ---
**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\ **Post date:** [December 27, 2023, 2:32pm UTC](https://community.localwp.com/t/just-upgraded-to-latest-version-of-local-and-now-get-500-internal-server-error/39660/4 "2023-12-27T14:32:42Z")
Hi @PLD - Thank you for sharing! We also mention adjusting the memory this way at the bottom of our performance help guide below just for anyone else’s reference: > **[Troubleshoot: Performance Issues](https://localwp.com/help-docs/troubleshooting/troubleshooting-performance-issues-in-local/)** > > Performance issues can be hard to fix! The best thing to do is zero in on where the slowness is occurring. Here are some suggestions to help set you up for success and ensure things are running as… ---
**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/system/32/1_2.png) [@system](https://community.localwp.com/u/system)\ **Post date:** [December 29, 2023, 2:32am UTC](https://community.localwp.com/t/just-upgraded-to-latest-version-of-local-and-now-get-500-internal-server-error/39660/5 "2023-12-29T02:32:48Z")
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.