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.
Am I expected to install MySQL and PHP separately?
No that shouldn’t be necessary. Is this your first time using Local?
Can you share your full Local Log here? There are some different ways to access and share Local Logs. For us to be able to troubleshoot thoroughly, please click the Download Local Logs button from the Support tab in Local. This will generate a zip archive that contains the Local log along with some other diagnostic information to help quickly zero in on any issues that Local is encountering.
I have just added the local-logs.zip to the original post.
I used this application on a prior version of Linux Mint. I recently did a fresh installation of the Mint OS on the same hardware. I did a fresh installation of localwp via the official DEB file. No errors on installation.
I have also tried switching the router settings without any success.
Yep I see that in your original error now. I was looking through your log and noticed these which seemed like a port conflict, but so far we haven’t been able to root it out with any of the usual checks:
This morning there were some updates via APT. I looked them over and found nothing related. I ran the updates, rebooted, and tried the local app again. Same results of an error as before.
So, changing the MySQL version does allow LocalWP to provision a site. That site does not work. I get a 502 error at this point using the Site Domains option.
If I try it with localhost I get “Unable to connect”
If you look to revisit this in the future, after some digging what we noticed is that there seems to be a port conflict between MySQL and Nginx.
To troubleshoot this you could first try restarting their computer and then check your sites.json to see what it shows for Ports. Then if you edit or kill either the MySQL or Nginx does the issue go away? That might help narrow things down.