Uh-oh! Error

What issue or error are you experiencing? A pop-up shows when I try to setup a new site , but sites already saved for while are running fine this is the message:

Еггог
Uh-oh! Unable to provision site.
Error: Error: Command failed: /home/yves/.config/Local/lightning-services/mysql-8.4.0/bin/linux/bin/mysql-e CREATE DATABASE local; /home/yves/.config/Local/lightning-services/mysql-8.4.0/bin/linux/bin/mysql: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
at genericNodeError (node:internal/errors:983:15) at wrappedFn (node:internal/errors:537:14) at ChildProcess.exithandler (node:child_process: 417:12) at ChildProcess.emit (node:events:519:28) at maybeClose (node:internal/child_process:1101:16) at Socket. (node:internal/child_process:456:11) at Socket.emit (node: events: 519:28) at Pipe. (node:net:346:12)
Ok

I haven’t found a solution to this problem anywhere. Neither in the Ubuntu Linux community nor on LocalWP. I understand it’s a compatibility issue with the latest versions, but how can I fix it? I need help, thank you!


System Details

  • Local Version: 10.10+6912

  • Operating System (OS) and OS version: Linux Ubuntu 25.10


Local Logs

Attach your Local Logs here (Help Doc - Retrieving Local’s Log)


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.

Hi @sevy!

Instead of using the preferred Local release could you try using the Custom option and changing your MySQL version to 8.0?

Hey !!! Great idea, it works
Thanks for helping me with this…
I’d tried a lot of things, but not that one.

But you have to admit there’s still a small compatibility issue that needs fixing. After all, we need to move towards newer versions, right?

Yes you’re right and I believe our dev team is already looking into this issue as others have raised the same. I’ll check with them and report back. For now however I’m glad you were able to get things working :slight_smile: