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.
I’m seeing a few lines in the Local log that look like this:
{"thread":"main","class":"Process","process":"nginx","level":"warn","message":"nginx: [emerg] still could not bind()","timestamp":"2021-09-10T14:49:56.506Z"}
{"thread":"main","class":"Process","process":"nginx","level":"warn","message":"nginx: [emerg] bind() to 0.0.0.0:10018 failed (48: Address already in use)","timestamp":"2021-09-10T14:49:57.136Z"}
This part:
bind() to 0.0.0.0:10018 failed (48: Address already in use)
Basically means that when Local is trying to get the site to listen on the 10018 port, something else is already there.
As a test, can you try:
For that plain WordPress site, are you able to create a Live Link and access that site in the browser?
If the plain WordPress site works over Live links, then let’s try freeing up that site. Fully restart the computer. This might free up that port and allow Local to register the site in that location.
If that doesn’t work, try exporting the site, and import it into a new site in Local. Enable the Live Link for that site.
If there are still issues with that specific site, can you take a screenshot so that we can get a better idea of what kinds of styles are missing? Also, can you let us know if there are any page builders enabled on the site?
I just added a new blank site and enabled Live Link - it worked and styles for the default 2021 WP theme showed up. I then added a new blank site and imported my remote mryczek.com site into the blank Local site, enabled Live Link and got the same errors as before. Restarted computer and tried again - same result. Please see attached screenshots.
It’s hard to know why those styles aren’t showing up.
If you open the browser console, do you see any errors?
One possible thing is that the stylesheet is trying to be loaded over regular HTTP, but the site is running on HTTPS. Either way, examining the browser console should give you more info about what’s going on!
