Encountering Internal Server Error When Installing Theme via LocalWP

What issue or error are you experiencing?

I’m unfamiliar with LocalWP. I tried to install the WordPress theme (UNCODE), but encountered only an error message stating: “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

System Details

  • Local Version:
    Version 8.3.2+6660
  • Operating System (OS) and OS version:
    |Edition|Windows 11 Pro|
    |Installed on|‎2/‎5/‎2023|
    |OS build|22631.3296|
    |Experience|Windows Feature Experience Pack 1000.22687.1000.0|

Local Logs

Attach your Local Logs here (Help Doc - Retrieving Local’s Log)
local-logs1.zip (8.1 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.

Hi @amaaljuffry

It looks like there might be some permissions issues on your machine. Are you running this application under an admin user account or this is a work machine where you don’t have that access?

Having the same issue while trying to step through code debugging. Site works fine without breakpoints in PHPStorm, but when I hit a breakpoint and start to step through the code this happens. Seems like a timeout issue, but max_execution_time = 1200 so I am not sure what the issue could be.

I am still having this error. It makes it almost impossible to step through large sections of code because the server just dies.

I added

KeepAliveTimeout 5

KeepAliveTimeout 1200

I added this

Timeout 1200

to my apache2.conf.hbs file to no avail.

Any ideas?

How large are the sections of code?

Do you have other sites running in Local while you’re working on this? Other applications running on your machine?

It might be that it’s just too much for Local to process at once but as always trying to cut down on any other conflicts might help give it an edge.

When I say large sections of code I really mean confusing sections of code that take me some time to figure out what they are doing. I have to step through some code that is 200 or 300 lines long and it seems there is a timeout that I am not aware of that causes this message.

Does it make a difference if you have other sites stopped, or other applications on your machine closed out? Just trying to eliminate any competition here.

Have you ever tested this on another machine to see if the same thing happens?

I don’t have another machine to test.

I opened another ticket to be able to give more info on this issue and I included a link to a video so that what is happening will be clear - Breakpoints go away after 40 seconds

I found the solution here - Internal server on Xdebug breakpoint

It is solved. It was an Apache problem. Apache times out by default after 40 seconds on a breakpoint. I added FcgidIOTimeout 600 to site.conf.hbs withing the <ifModule…> section to increase this to 10 minute


Thank you @jim_hubbard :green_heart:


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