N8n workflow not moving through nodes

Describe the problem/error/question

When I run an n8n workflow manually, it is not progressing to the next node even though the execution log shows the previous node completes without any errors and outputs the data for the next node to pickup as input.

It is very odd - no errors, it just never moves to the next node.

What is the error message (if any)?

No error

Please share your workflow

Share the output returned by the last node

Output is showing all the files that it should show (167 in total)

Information on your n8n setup

  • n8n version: 1.61.0
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm
  • Operating system: MacOS

Hey @ThatPrivacyGuy , could you share a screenshot showing where the workflow execution stalls?

I suspect it might be at LLM Chain due to large text to process or general service availability provided by Ollama. If so, do you self-host Ollama or use the external solution?

No need to screenshot it stays on the node that was executed and just keeps the state of “Executing” - but when you go to execution log it shows as complete.

So if I use the Manual trigger it never moves from the Manual trigger, if I run the second node (the read file node) by clicking the play button, it does the same. If I stop that execution and then manually play the next node, same thing.

Each time I try to manually progress (only after the execution view shows the node has completed and I can see the output data is there) it is the same.

I left it running for 45 minutes, it never progressed.

Worked last week, workflow hasn’t changed only difference is I was physically sat at the machine running n8n and hosting the files when I ran it last week from localhost- this week I am in a hotel a thousand miles away - accessing n8n through nginx reverse proxy.

Hey @ThatPrivacyGuy

Did you remember to configure nginx to allow websockets? It sounds like it hasn’t been done which means the front end is waiting for the message from the backend but it is never arriving.

I have a configuration as per the forums but it is not working it seems.

My n8n is not installed via docker (as I don’t use docker) it is installed via npm, I am running my own Ollama as well.

Also my nginx reverse proxy is not running on localhost, it runs on my network gateway as I have several machines serving sites.

I will dig into the nginx config shortly.

OK I managed to fix the Nginx websockets issue and everything is now working correctly.

Thanks for the headsup, I had commented out a line in the conf for testing and forgot to re-enable it.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.