Just Upgraded to Latest Version of Local and Now Get 500 Internal Server Error

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.

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:

Once you’ve done that, you can downgrade by following the steps here:


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.


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:

1 Like

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.