Port 3000 in use so server can not start

[Ulrich]

OS info

• Operating System : Mac OSX 25.5.0
• Wappler Version : 7.9.6

Problem description

After Wappler crashed, I had to reinstall it. Now I receive the error: Failed to listen on 0.0.0.0:3000. Bevor the crash everything works perfect.

report1783063287892.zip (277.7 KB)

Steps to reproduce

1. After Rebooting und starting my Project:

2. [Fri Jul 3 09:36:49 2026] PHP 8.5.6 Development Server (http://0.0.0.0:3000) started
   [Fri Jul 3 09:36:50 2026] 127.0.0.1:49591 Accepted
   [Fri Jul 3 09:36:50 2026] 127.0.0.1:49592 Accepted
   [Fri Jul 3 09:36:50 2026] No .htaccess file found in document root /Users/ulrichantz/Documents/DurchDieLinse
   No .htaccess file found in document root /Users/ulrichantz/Documents/DurchDieLinse
   [Fri Jul 3 09:36:50 2026] 127.0.0.1:49591 [200]: GET /dmxConnect/api/Countries/Pictures/read.php?filter_pic=
   [Fri Jul 3 09:36:50 2026] 127.0.0.1:49591 Closing
   [Fri Jul 3 09:36:50 2026] No .htaccess file found in document root /Users/ulrichantz/Documents/DurchDieLinse
   No .htaccess file found in document root /Users/ulrichantz/Documents/DurchDieLinse
   [Fri Jul 3 09:36:50 2026] 127.0.0.1:49592 [500]: GET /dmxConnect/api/Countries/countries/read.php
   [Fri Jul 3 09:36:50 2026] 127.0.0.1:49592 Closing
   [Fri Jul 3 09:36:50 2026] 127.0.0.1:49608 Accepted
   [Fri Jul 3 09:36:50 2026] 127.0.0.1:49608 Closed without sending a request; it was probably just an unused speculative preconnection
   [Fri Jul 3 09:36:50 2026] 127.0.0.1:49608 Closing
   [Fri Jul 3 09:36:50 2026] 127.0.0.1:49613 Accepted
   [Fri Jul 3 09:36:50 2026] 127.0.0.1:49614 Accepted
   [Fri Jul 3 09:36:50 2026] No .htaccess file found in document root /Users/ulrichantz/Documents/DurchDieLinse
   No .htaccess file found in document root /Users/ulrichantz/Documents/DurchDieLinse
   [Fri Jul 3 09:36:50 2026] 127.0.0.1:49613 [200]: GET /dmxConnect/api/Countries/Pictures/read.php?filter_pic=
   [Fri Jul 3 09:36:50 2026] 127.0.0.1:49613 Closing
   [Fri Jul 3 09:36:50 2026] No .htaccess file found in document root /Users/ulrichantz/Documents/DurchDieLinse
   No .htaccess file found in document root /Users/ulrichantz/Documents/DurchDieLinse
   [Fri Jul 3 09:36:50 2026] 127.0.0.1:49614 [500]: GET /dmxConnect/api/Countries/countries/read.php
   [Fri Jul 3 09:36:50 2026] 127.0.0.1:49614 Closing

[George]

Seems you still have a previous php server running on port 3000.

Just search for it from the Activity Monitor and kill it.

Then you can start Wappler normally.

[bpj]

Wappler usually handles the closure gracefully but on the odd occasion, especially after a crash, it can hang on to the open port. The quickest method I have found to handle it is to open Terminal (you can do this at the bottom of the Wappler UI) and use the following command:

kill $(lsof -t -i:3000)

You can then use the button to restart the local server

e.g.

[Ulrich]

Now another Problem comes up:

there is no server starting

[bpj]

Did you click the restart Local Server button (bottom right of Wappler UI)?

[Ulrich]

There is nothing like that

This is the setting

[bpj]

XX - Can you post a screenshot of the settings page for your Development target? -- XX
You could also try:

1. Clicking Publish and choosing the Development target
2. Restarting Wappler (from the system tray choose Restart Wappler)

[Ulrich]

I just realize that the server side ist own server. Before it was Wappler local server. But switch to Wappler local server and the page is shown in the browser, But the connection to the db seems to be not working

[bpj]

When you say the db connection doesn't work. Is this just on the page or also in Database Manager/Queries in the Wappler UI?

[Ulrich]

The connection to the database works correct. When I start the query with debug the following error names up:A server error occured, to see the error enable the DEBUG flag.

Problem solved. It was a missing column in a table. This happened by the first crash of Wappler when I created a new column

[bpj]

In the interest of helping anyone else trying to solve what the thread title was (solving the port 3000 issue) can you make the answer with the kill command the solution?