500 internal server on frontend after migrating with all in one

Support
,
1

What issue or error are you experiencing?

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@localhost to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

after successfully migrating to Local using all in one.
I can access to the backend admin panel but not frontend. it throws the 500 error.
I tried to remove .htaccess (rename it .htaccess-1) under app/public
still the same.

System Details

  • Local Version: latest…(2024 Oct 5) i dunno where to see the version

  • Operating System (OS) and OS version: windows 11

Local Logs

Attach your Local Logs here (Help Doc - Retrieving Local’s Log)

site-error.log (14.6 KB)

Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

2

Hi @futureyoon

If you create a new, blank site in Local can you access that okay?

If the issue is just with this specific site, I’d start by opening Site Shell (there is a button under your site name in the Local app), and then use WP CLI to deactivate plugins or swap out the theme.

3

https://youtu.be/eD8wjVpuSmE?si=WVbOg4T_VZ_shb1i
This is what I followed.

I have deactivated all plugins and changed back to twenty twenty default theme. I dun need to use wpcli tho as I could access to the backend panel.

But I’m getting 500 internal server error for the front-end.

Any idea what others I should be checking ?

Please help.
Thank you.

4

Ah okay I missed that you could still access the backend.

If you create a new, blank site can you access that okay? Just curious if the issue is limited to this specific site or not.

Currently do you have your Router Mode set to LocalHost? If you change to Site Domains does that change the behavior? (Preferences>Advanced>Router Mode)

Is your server type Apache? Seeing some errors in the logs that might indicate a server issue. If you change to NGINX does that resolve the issue?