How to investigate "Connection Lost" and "502 Bad Gateway"

Questions
1

Hi

We encountered an increasing issue : the UI is not responding. I see “:warning: Connection lost” in the top left on the UI. If I open an new tab to my serveur I see " 502 Bad Gateway — nginx/1.18.0"
After 1 or 2 minutes, the server is back.

The problem appear after a click on Execute Node, or Execute Workflow.

I use only set, code and HTTP request node.

The bug is on the windows version too.

It’s seems that the server stop. Then the OS restart it. But we can’t find logs on the error causing the crash.
How can I investigate on what is causing this behavior ?

Thank you

Information on your n8n setup

  • n8n version: 0.219.1
  • Database you’re using (default: SQLite): Mysql
  • Running n8n with the execution process [own(default), main]: own
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: npm and desktop app
2

Hi @JulienDelRio, I am sorry to hear you’re having trouble.

It’s seems that the server stop. Then the OS restart it.

Yep, that sounds likely.

But we can’t find logs on the error causing the crash.

Logging in n8n can be configured using a number of environment variables. By default, errors would be written to the console and are accessible for example using commands such as docker logs (when using docker) or pm2 logs (when using pm2 to manage your npm deployment).

WIth the desktop app it’s a bit more tricky to view the logs. I think your best bet would be to start the desktop app via the command line as described here, then reproduce the crash.

3

Ok thank you.

I will try with my colleague and make a feedback !

1 Like