The site is running in the browser but I’m having trouble troubleshooting a plugin.
The initial symptom was that the error log was not recording any errors. Further investigation revealed that the php-fpm.log is throwing lots of errors. The errors are all like this one:
[23-Mar-2021 16:14:08] WARNING: [pool www] child 2709 said into stderr: "1616469248.288067: There was a problem sending 179 bytes on socket 11: Broken pipe"
Troubleshooting Questions
Does this happen for all sites in Local, or just one in particular?
The problem is limited to one web site.
Are you able to create a new, plain WordPress site in Local and access it in a Browser?
Yes. I can create a new wordpress site in local and access it in the browser
Replication
Describe the steps that others can take to replicate this issue. If you have screenshots that can help clarify what is happening, please include them!
System Details
Which version of Local is being used?
Local v5.10.1
What Operating System (OS) and OS version is being used?
macOS Catalina
Attach the Local Log. See this Community Forum post for instructions on how to do so:
In addition to that error you mention, I’m seeing a few errors in the error.log that seem to point to there being an issue with Local’s router not being able to use Port 80:
2021/03/18 13:11:21 [emerg] 17938#0: bind() to 0.0.0.0:80 failed (48: Address already in use)
2021/03/18 13:11:21 [emerg] 17938#0: bind() to [::]:80 failed (48: Address already in use)
2021/03/18 13:11:21 [emerg] 17938#0: still could not bind()
Often times when Local is having issues binding on Port 80, it’s due to another application taking that port.
However, you mention that you were able to access the site, so I wonder if there’s something crashing that Router processes, but since it’s still listening, Local can’t “re-register” the router? Just a wild guess.
Have any other applications been installed recently which might be listening to that port 80? For some additional troubleshooting steps, you might take a look at the Router Mode help doc:
And as a test, see if switching to localhost Router Mode makes this site work. If it does, then maybe there’s something about what this site is doing that is crashing Local’s Nginx Router.
Yes, I noticed that too. I’m on a Mac, so apache is sitting there. It isn’t/shouldn’t be running but it’s always waiting to be bumped into action, which I do sometimes do I if grab the wrong terminal window and start issuing commands. I think on the 18th I issued “apachectl graceful” to this machine which started apache.
I’ll try the switch to localhost and see what results I get.
thanks for the pointer. I don’t have apache starting on boot because it interferes with my dev environment.
In this case, I can build a new web site easily and the problem is restricted to one website. I’ll simply start moving files manually, testing as I go, until I break something or transfer it all.