Wappler Version : 7.1.2
Operating System : Windows
Server Model: NodeJS
Database Type: External
Hosting Type: Docker
Every few hours the Local Web Server keeps crashing without showing any errors in the output.
When running Wappler with logging enabled, this line appears in the logs each time it happens:
[2025-07-31 14:37:58.634] done code=null
This issue has been occurring since Wappler 7 Beta.
Yep. Can confirm this has been happening for ages, on any project, on both Windows and Mac, using the local server option.
I resorted to just running the server via terminal instead
Interestingly we do not experience this on Ubuntu. Have you got any scheduling or anything similar that is running server side?
In see it a lot also on Win 11. Assumedc it was linked to the port issue i reported a while back.
I can also confirm that Wappler crashes several times a day since version 7. I'm on MacOS, NodeJS, server type "own server", db none (extern Supabase).
Could you post the exact node crash log that you see in the Web Server tab?
Sure, you'll find the web server tab log and the wappler.log find attached.
(downloaded and removed to protect privacy)
What do you see as crash Dennis? Because I see just regular web server output only, with enabled debug logging, so all server connect state and actions are outputted, and all seems fine.
I have checked this multiple times and there is never actually a crash log for me in the web server tab, it just stops.
There's no indication whatsoever, and it's seemingly completely randomly, even if you are just idle.
What Digo states also happens for me. Randomly it crashes the local server and then I have to restart the server.
Not sure if mine crashes as I don't see anything in the log that would point to that, but my server does stop a dozen times a day or more and I have to keep restarting the server. Only since 7.x.
Is there any update on this?
The server keeps stopping almost every hour or so.
You're lucky, how does every 10 minutes sound to you?
My brain has now been programmed to first restart the server before checking in the browser. 
Edit: Wappler 7.2.2 and prior, Windows 11
Yes, same here. Just start getting 404 errors or more commonly cached versions of old code which has since been updated.
Seems to affect api actions mainly where old versions are served instead of updated versions.
No indications of the crash. Status bar shows running but it isn't
for the people having this problem please specify exactly what are you using as server for you development target
wappler local server, own server or docker
Further more exactly define, what do you experience as "crashing" - is that a 404 errors on all files, or browser does nothing or other errors?
on which OS are you?
And lastly a wappler debug log file will be greatly appreciated that is recorded during the server crash.
Iâm using âOwn serverâ with NodeJS on Windows 11
My experience of crashing is that I canât access the server via the browser in any way. Both pages and api-calls are refused. The console throws errors for socker.io - net::ERR_CONNECTION_REFUSED
The only visible reponse I see is the yellow excamation next to the Target: Development.
I have to press the âStart Local Serverâ button to restart the server and then I am able to continue in the browser.
The âcrashingâ can happen at any time. While working in the Wappler app, in the browser or even when iâm away from the computer.
You can see all the Wappler logs towards the crash.
wappler.zip (8.6 KB)
Wappler own server
Win 11
Sometimes no indication it has stalled in status bar.
Own Server, NodeJS, Windows 11, Wappler 7.2.2
wappler.zip (6.9 KB)
I had a glance at Mark Jonkers' zip file and in both (his and mine) cases, there is a time lag between the second last and last activity. No further error messages have been shown.
