Uh Oh - Unable to Start Site - Can't connect to mySql server at ::1' failed

Support
1

Uh Oh - Unable to Start Site - Can’t connect to mySql server at ::1’ failed

Local1
Local1965×566 179 KB

Local Version Upgraded to: 10.0.0+6907
Web Server: nginx
PHP Version 8.2.27
MySQL: 8.0.35
Word Press: 6.9.4
Windows 11

After I did the latest update of Local, my site was still running fine. The next day I had to reboot my computer for other reasons. Once it rebooted, Local would no longer connect with my site. It gave the error I attached “Uh Oh - Unable to Start Site - Can’t connect to mySql server at ::1’ failed”. See screenshot!

I Exited local by EXIT Only and checked Task Manager to see if anything was still running. I’ve done this many times and never found anything to get stuck running. I’ve rebooted several times since and still doesn’t work.

I manually started mySql with no issues and confirmed in Task Manager’s Task Manager. I started it by running this command in CMD:

“C:\Users\pc\AppData\Roaming\Local\lightning-services\mysql-8.0.35+4\bin\win64\bin\mysqld.exe” --defaults-file=“C:\Users\pc\AppData\Roaming\Local\run\Kipg7TaOG\conf\mysql\my.cnf” --standalone

I then tried to start Local while mySql was running, but it did the same thing where is just spins and keeps trying to make a connection.

My website is not on my C: drive it’s on my E: drive, but is not an external drive.

What can I do to get this up and running again? I’ll leave it off with providing some log file data. Not sure it this log file of info can help. Also, a few images at the the end of the log file data. So, here’s some data written to my local-lightning.log:

{“class”:“Process”,“level”:“warn”,“message”:“2026-04-22T03:09:17.546390Z 0 [System] [MY-010116] [Server] %%userDataPath%%\\lightning-services\\mysql-8.0.35+4\\bin\\win64\\bin\\mysqld.exe (mysqld 8.0.35) starting as process 22992”,“process”:“mysql”,“thread”:“main”,“timestamp”:“2026-04-22T03:09:17.598Z”}

{“class”:“Process”,“level”:“warn”,“message”:“2026-04-22T03:09:17.590450Z 0 [Warning] [MY-013243] [Server] --character-set-server: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.”,“process”:“mysql”,“thread”:“main”,“timestamp”:“2026-04-22T03:09:17.598Z”}

{“class”:“Process”,“level”:“warn”,“message”:“2026-04-22T03:09:17.634176Z 0 [Warning] [MY-013907] [InnoDB] Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=201326592. Please use innodb_redo_log_capacity instead.”,“process”:“mysql”,“thread”:“main”,“timestamp”:“2026-04-22T03:09:17.634Z”}

{“class”:“Process”,“level”:“warn”,“message”:“2026-04-22T03:09:17.641397Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.”,“process”:“mysql”,“thread”:“main”,“timestamp”:“2026-04-22T03:09:17.642Z”}

{“class”:“Process”,“level”:“warn”,“message”:“2026-04-22T03:09:20.980085Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.”,“process”:“mysql”,“thread”:“main”,“timestamp”:“2026-04-22T03:09:20.980Z”}

{“class”:“Process”,“level”:“warn”,“message”:“2026-04-22T03:09:22.758062Z 0 [System] [MY-010229] [Server] Starting XA crash recovery…”,“process”:“mysql”,“thread”:“main”,“timestamp”:“2026-04-22T03:09:22.760Z”}

{“class”:“Process”,“level”:“warn”,“message”:“2026-04-22T03:09:22.766914Z 0 [System] [MY-010232] [Server] XA crash recovery finished.”,“process”:“mysql”,“thread”:“main”,“timestamp”:“2026-04-22T03:09:22.767Z”}

{“class”:“Process”,“level”:“warn”,“message”:“2026-04-22T03:09:23.082669Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.”,“process”:“mysql”,“thread”:“main”,“timestamp”:“2026-04-22T03:09:23.083Z”}

{“class”:“Process”,“level”:“warn”,“message”:“2026-04-22T03:09:23.082844Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.”,“process”:“mysql”,“thread”:“main”,“timestamp”:“2026-04-22T03:09:23.085Z”}

{“class”:“Process”,“level”:“warn”,“message”:“2026-04-22T03:09:23.213050Z 0 [ERROR] [MY-010262] [Server] Can’t start server: Bind on TCP/IP port: Only one usage of each socket address (protocol/network address/port) is normally permitted.”,“process”:“mysql”,“thread”:“main”,“timestamp”:“2026-04-22T03:09:23.215Z”}

{“class”:“Process”,“level”:“warn”,“message”:" ",“process”:“mysql”,“thread”:“main”,“timestamp”:“2026-04-22T03:09:23.219Z”}

{“class”:“Process”,“level”:“warn”,“message”:“2026-04-22T03:09:23.213115Z 0 [ERROR] [MY-010257] [Server] Do you already have another mysqld server running on port: 10019 ?”,“process”:“mysql”,“thread”:“main”,“timestamp”:“2026-04-22T03:09:23.223Z”}

{“class”:“Process”,“level”:“warn”,“message”:“2026-04-22T03:09:23.213187Z 0 [ERROR] [MY-010119] [Server] Aborting”,“process”:“mysql”,“thread”:“main”,“timestamp”:“2026-04-22T03:09:23.226Z”}

{“class”:“Process”,“level”:“warn”,“message”:“2026-04-22T03:09:24.233859Z 0 [System] [MY-010910] [Server] %%userDataPath%%\\lightning-services\\mysql-8.0.35+4\\bin\\win64\\bin\\mysqld.exe: Shutdown complete (mysqld 8.0.35) MySQL Community Server - GPL.”,“process”:“mysql”,“thread”:“main”,“timestamp”:“2026-04-22T03:09:24.234Z”}

{“class”:“Process”,“level”:“warn”,“message”:“2026-04-22T03:09:25.200318Z 0 [System] [MY-010116] [Server] %%userDataPath%%\\lightning-services\\mysql-8.0.35+4\\bin\\win64\\bin\\mysqld.exe (mysqld 8.0.35) starting as process 12140”,“process”:“mysql”,“thread”:“main”,“timestamp”:“2026-04-22T03:09:25.229Z”}

Local3
Local31221×545 187 KB

Local2
Local21263×840 91.8 KB

2

Summary of More Troubleshooting Steps

  1. Process Hygiene: Consistently verified clean exits from LocalWP; used Task Manager to confirm no “zombie” local.exe or mysqld.exe processes remained active before attempting restarts.

  2. Network Flush: Performed a netsh winsock reset via Administrator Command Prompt followed by a system reboot to clear potential socket/interface errors.

  3. Successful Manual Database Launch: Manually triggered the MySQL instances, which started without issues and were verified as active in Task Manager. This proved the database binaries/data were healthy. Services were fully stopped after testing.

  4. Port Reconfiguration: Attempted to resolve connectivity issues by manually changing the port assignments (shifting from the default 10005 range to 8888).

  5. Phantom Port Conflict: Despite having no other database software installed (no XAMPP, MAMP, or Docker), logs consistently report: [ERROR] [MY-010257] Do you already have another mysqld server running on port: 8888?. Verified via netstat that nothing else was using this port prior to launching LocalWP.

  6. Windows Security Exclusions: Added folder exclusions in Windows Defender for the LocalWP application folder, the Site Data folder, and the Lightning Services folder.

  7. Firewall Configuration: Updated Windows Firewall permissions to “Private” and “Public” for local.exe, nginx.exe, and mailpit.exe.

  8. Hosts File Verification: Confirmed the Windows hosts file was NOT set to “Read-only.”

  9. Router Mode Adjustment: Attempted to bypass the conflict by switching LocalWP Router Mode to “Localhost” in Advanced Preferences.

  10. Outcome: LocalWP remains stuck in a “Starting” loop. It appears to be incorrectly detecting a conflict on Port 8888 that does not exist externally.

3

Thanks for this report, @Azdolfan, and sorry for the experience.

If this site is still failing to start, are you able to DM me a copy of your sites.json file? I’d like to check how ports are currently assigned between your sites. You can find it like this on Windows:

  1. Open the File Explorer.
  2. Choose View → Show → Hidden items.
  3. Browse to This PC → [your harddrive] → Users → [your username] → App Data → Roaming → Local
  4. Look for a file named “sites” or “sites.json”.

As a workaround for now to get this site to start again, you can try this advice: