I’m facing a persistent issue with my self-hosted n8n instance, where the “Test Workflow” functionality isn’t visually highlighting execution steps in real-time. This is making debugging much more challenging. I’ve seen it working correctly in demos and videos (like the one at $$mention video timestamp if known]), and I’d love to get it functioning as expected.
I’m running the latest version of n8n. Here’s a summary of what I’ve already tried, based on suggestions and my own troubleshooting:
Memory Usage: Checked server memory usage during workflow execution; it appears to be within normal limits.
WebSocket Configuration: Verified WebSocket settings, particularly in relation to LiteSpeed Web Server which the server is running on. My hosting provider (Scalahosting) has checked and stated no nginx changes are required
Browser Console: Monitored the browser console during workflow execution. I’m seeing a 500 Internal Server Error when stopping the execution (/rest/executions/*/stop). I initially saw 401 unauthorized errors but am unable to reproduce these.
Hosting Support Interaction: I have engaged my hosting provider (Scalahosting). They’ve confirmed the server isn’t experiencing high resource usage and have checked logs but haven’t identified a root cause. They mentioned that it appears the 500 error on stop happens inside the application.
I’m at a bit of a loss. Has anyone encountered this specific combination of symptoms – particularly the 500 error on stopping execution and the lack of real-time highlighting – and found a solution? Any advice or suggestions would be greatly appreciated!
Can you share a bit more detail here please? You mean the nodes being executed live? Mind recording a small video of the execution running with the canvas open so we see what happens?
Have you tried it on a different browser just to check that?
Thanks. Check if there are any errors on the console/network tab. Are you also on the latest version?
I don’t see any widespread issues at the moment so this is probably something relates to that particular hosted setup.
Does it work in docker on that same provider or the same exact setup on a different provider (e.g. railway, digital ocean)? Could be worth testing this to understand if this is a hosting provider issue or not.
@gualter Cehojac also has the same issue. Do you know what i can do to figure out the issue? The backend seems to work. Its executing in backend, but its not visible in the frontend.
Scalahosting where i am hosting mine does not support docker. What can i even tell my developer if i needed to? How could he fix it?