So, I have a client that has a website built on basic Wordpress. I am creating a new website for him. I have never used Local before, but I was trying to set it up and clicked trust for the SSL certificate. It broke the current website and I cannot log into Wordpress anymore. I have no idea what happened…Anyone have any ideas?
Troubleshooting Questions
Does this happen for all sites in Local, or just one in particular?
This is for one website. I never linked it to the internet. Now it shows me the local site and I have to install Wordpress on it. Is there a way to go back to normal and remove Local?
System Details
Which version of Local is being used?
Version 6.1.0 +5452
What Operating System (OS) and OS version is being used?
Windows 10
It’s hard to know exactly what went wrong without seeing a Local log – Can you please provide one? See this Community Forum post for instructions on how to do so:
You mention not being able to log into the live site, one thing you might check is if the site-domain within Local is different than the live site’s domain.
You’ll want to use a different domain for the local site so that you’re able to access both of them at the same time. We usually recommend using a “dot local” suffix, like example.local
So, for starters…the client has hosting elsewhere, does that matter? I assumed that Local by Flywheel was just a local hosting that was separate from the current website. I am receiving the 500 Error when I try to view the website as well as the wp-admin.
I’m hoping sending the log file and the home page will help. Please let me know, thank you!
Taking a look at that Local log, it looks like Nginx is having issues with the special characters in the folder name:
{"thread":"main","class":"Process","process":"nginx","level":"warn","message":"nginx: [emerg] CreateFile() \"C:\\Users\\danny.myers\\OneDrive - Valmark Securities\\�T� TeamComm\\06. WEBSITES\\McNair_&_Company\\logs","timestamp":"2021-07-23T13:57:56.763Z"}
{"thread":"main","class":"Process","process":"nginx","level":"warn","message":"ginx\\error.log\" failed (123: The filename, directory name, or volume label syntax is incorrect)","timestamp":"2021-07-23T13:57:56.764Z"}
This part is what stands out to me: ...ies\\�T� Tea... – I think that’s the escape sequence for a musical note.
This type of special character isn’t something that Nginx can handle and you’ll need to create a new site in a location that doesn’t have special characters in it.
I switched from Mac to PC a few years ago. When I was using Mac, I used a dash to keep folders pinned to the top, now I use the music symbol. So, if I change the path for the local site, that wouldn’t fix the online website though, would it?
Yeah, sorry. I guess the timing was very weird on this one. I thought that creating the local site messed up the live site, when in all reality…it was the fact that I activated Elementor on his live site. So, just to be clear, if I wanted to create a local site I would just have to change that path and remove the ♫ symbol. Then I could set up a fresh install of WordPress and download Elementor, etc.
Essentially when you create the local site, it starts you from scratch with installing WordPress.
