Can't resolve the Msql error after trying everything

Support
, , ,
1

Hello
Thank you for your help and time in advance if possible. I don’t know witch steps to make now. I am not unfamiliar with the error, but this time i tried all i found and that i can try, without result.

What issue or error are you experiencing?

I recieve the basic Msql error on launching site about the occupied port but i can’t find something that’s working to change that. To be fair, i am not a professional, but as such i tried all i can find from the router page on this website and others things i found on other website, without results.

The situation is :
Today i cannot run my site. A new maj append on my win11 for security, maybe at cause but my site run on it for a whole day before so not sure. Also, i change from a “business” internet network to my private box at home between the two. The site is private, not for work, and not broadcast yet

My attempts
I tried cloning it to use the automatic attribution of host port - not working
I tried to upgrade the ap local - not working
Killing all the process on port 80 - not working
and some process described don’t even exist in my task manager at the indicated PID in cmd
Using the Xdebug to resolve - not working
Changing from “site domain” to “localhost” multiple times, with restart - not working
Restarting the pc, desinstalling the ap local etc - not working
i am not using anything beside local as ap that use the port 80 beside internet explorer
i autorised in windefender firewall the access to local - not working
at the time i also saw something interesting like a double ap name local.

What’s working : creating a new site

Difference that i saw : not the same version of mysql on both site
site not working today : MySQL 8.0.16
site working : MySQL 8.0.35

After flying into the log, i found something about the nginx but i don’t know what to do :

I am sorry, but i am at a lost this time. Please, help me or at list give me direction to seek because i don’t know what to try right now. How can i at least force the new attribution of the host port number ?

What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

the error message :

Capture d'écran 2025-03-05 212622
Capture d'écran 2025-03-05 212622550×306 11.4 KB

System Details

  • Local Version: Version 9.2.2+6771

  • Operating System (OS) and OS version: Win 11 x64

Local Logs

the error (always the same whatever i tried) :
2025/03/05 20:32:41 [warn] 12852#5308: the “listen … http2” directive is deprecated, use the “http2” directive instead in C:/Users/x/AppData/Roaming/Local/run/router/nginx/conf/server-block-ssl.conf:1
2025/03/05 20:32:41 [warn] 12852#5308: the “listen … http2” directive is deprecated, use the “http2” directive instead in C:/Users/x/AppData/Roaming/Local/run/router/nginx/conf/server-block-ssl.conf:2
local-logs (2).zip (585.2 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.

2

Hi @marh

If creating a new site is working, then you could try re-importing the site having problems. The steps would look like this:

  • Locate the site files on your machine, and save a copy of them to your desktop. If you click Go to Site Folder under your site name it should take you right to where they are located.
  • Once you have those copied, completely delete the site from Local
  • Restart Local/your machine
  • Reimport the site back into Local. You can refer here on how to Restore from only Local site files
3

@Nick-B Creating a new site and importing the DB from Workbench higher than 2GB is failing on Windows but works on MacOS. Hence, this step is not a solution and the latest version of Local on Windows is not a stable release as it broke many users’ hearts.

4

Hi @shivapoudel

We can’t replicate this problem on Windows but there could be a few different reasons for the difference between your OS tests. If you haven’t already you might check some of these common issues:

  • On Windows, even if your OS is 64-bit, your Workbench installation could be running under a 32-bit process, depending on how it was installed.

  • On Windows, MySQL Workbench (or MySQL itself) might be writing large imports to a temp folder (usually under %TEMP%). If your temp drive is small (or limited in space), this can silently break the import process.

  • In some cases, file path length or special characters in the file name (or path) can trip up Windows, especially when handling very large files.

  • Windows Workbench could be running into per-process memory caps (even in 64-bit). Windows manages memory quite differently from macOS, and large file handling can suffer if Workbench isn’t allocating memory correctly.

5

Whats the process to import the sql then because I cannot export until the site is running?

But I don’t this proper import also will resolve the SQL erroor and you guys need to give a look.

6

Whats the process to import the sql then because I cannot export until the site is running?

You can always manually locate your site files. The easiest way is to just click on Site Folder in the Local app under your site name. Otherwise you can manually search on your device for your Local Sites directory.

But I don’t this proper import also will resolve the SQL erroor and you guys need to give a look.

We’ve taken some steps to resolve these types of errors in Windows in our latest release but we will continue to investigate. Have you run into the same issue on Windows for other sites or is it only this site with the large database?

8

Only issue within the larger db size on windows.