n8n instance issue (22Apr2026)

11
Viewed 52

I have created an n8n instance and it works fine since last year. I have the below error 'upstream connect error or disconnect/reset before headers. retried and the latest reset reason: remote connection failure, transport failure reason: delayed connect error: 111' when I try to connect this instance. Any recent changes since 21 or 22Apr? Any recommended fix on that? Tks a lot!

2 Answers

same problem here, my n8n pod has been running well for 167 days, and it just show the same error "no healthy upstream" since yesterday, and restart app didn't help.