N8n via Portainer and NPM give upstream timed out error

[Zombiehamster]

Hi. Use Nginx proxy manager for Portainer stack running n8n docker. All worked good, but few days ago I have “upstream timed out (110: Connection timed out) while reading response header from upstream” errors in log.

NPM

Portainer stack

Container

/data/compose/1/data/logs/proxy-host-3_error.log

2024/06/05 23:02:53 [error] 200#200: *222 upstream timed out (110: Connection timed out) while connecting to upstream, client: 64.xx.xx.x, server: n8n.xxx.com, request: “GET /favicon.ico HTTP/1.1”, upstream: “http://xx.xx.xx.xx:5678/favicon.ico”, host: “n8n.xxx.com”, referrer: “https://n8n.xxx.com/”

I read few artciles about this situation and turn on websocket support at NPM, but still have errors in log and 500 error. Adding new env to container like

WEBHOOK_URL=https://n8n.example.com 
WEBHOOK_TUNNEL_URL=https://n8n.example.com 
VUE_APP_URL_BASE_API=https://n8n.example.com 

or

N8N_PUSH_BACKEND=sse

dont help.

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

[Jon]

Hey @Zombiehamster,

This doesn’t apear to be an n8n issue and looks like it might be a problem with your nginx proxy manager configutation.

Your forward hostname / IP is normally the local IP or hostname of your n8n install so assuming you are on the same machine it might be something like 172.17.0.1 if nginx proxy manager and n8n are on the same docker network.

Other than that everything else looks to be ok apart from having WEBHOOK_TUNNEL_URL and VUE_APP_URL_BASE_API being set which are not needed.