Why i see this in my selfhosted log

Questions
1

Hello

I usually see this in my self hosted logs many times

TCP Proxy: Was closed, calling abort controller

TCP Proxy: Was closed, calling abort controller

TCP Proxy: Was closed, calling abort controller

also this

(node:7) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.

(Use `node --trace-deprecation ...` to show where the warning was created)

i use https://nginxproxymanager.com/ as proxy manager to provide SSL

and in decker ENV VAR i have below variables added

N8N_PROXY_HOPS = 1
N8N_SECURE_COOKIE = false
WEBHOOK_URL=https://n8n.server.mlotfy.win/
N8N_EDITOR_BASE_URL=https://n8n.mydomain.com/
N8N_HOST=https://n8n.mydomain.com/
N8N_PROTOCOL=https

My server details

Debug info

core

  • n8nVersion: 2.1.4
  • platform: docker (self-hosted)
  • nodeJsVersion: 22.21.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: 41ff6747-4a2a-49b5-9bfa-0aacfe71ca78

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/143.0.0.0 safari/537.36
  • isTouchDevice: false

security

  • secureCookie: false

Generated at: 2026-01-01T13:36:32.485Z

2

Those aren’t critical errors, they are just warnings. The first one is when the real time editor update fails because of a connection, the abort controller is launched to clean up the request so it keeps working.

If you want this to go away, you can ensure that websockets support is enabled in the settings for your host, probally in the docker config.yml file or somewhere similar.

The 2nd one is a warning about an older node.js feature that is old and deprecated. It doesen’t mean anything importaint, it’s also just a warning.

Is your server working though? All of the logs you provided are just warnings, they wont crash your instance.

3

yes when i use to debug a workflow i mostly always getting errors because the the is not reflecting the expected trigger , and then i have to save and force browser refresh and try again.

any suggestion what change can fix/enhance this issue