AI Agent problem

Questions
1

Hey,

I’m trying to use AI agents in my workflows, and till a few days ago, I could easily import templates on my self-hosted n8n. But now I don’t see the AI agent input options. At first, I thought it might be a version issue, so I rolled back versions and tried different backups.
Here’s what’s happening in practice, for example, this template:

image
image351×278 45.6 KB

When pasted into my workflow turns into this:
image
image836×745 22.9 KB

Even a simple AI agent has the same problem, it used to have different options, such as memory, model and tools:
image
image790×372 11.4 KB

What do you suggest I do?

  • n8n version: 1.91.1

  • Database: PostgreSQL (via Docker)

  • n8n EXECUTIONS_PROCESS setting (default: own, main): queue (using EXECUTIONS_MODE=queue)

  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker

  • Operating system: Linux (Ubuntu)

1 Like
2

I have the same problem with my hosted n8n version : ai agent, switch, or text classifier has no branches (if or loop has no problem)
I have tried on different version : 1.91.1, 1.90.0, 1.89.2 , 1.86.0 , with chrome or edge without success

  • n8nVersion: 1.90.2

  • platform: docker (self-hosted)

  • nodeJsVersion: 20.19.0

  • database: postgres

  • executionMode: regular

  • concurrency: -1

  • license: enterprise (production)

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

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

image
image748×583 35.8 KB

3

Same here. I have daily backups, and I reverted to a few days ago, and nothing. I used different versions of n8n and nothing. I tried starting fresh, and still nothing. I disabled caching on Caddy file, different browsers and incognito mode and still nothing.

4

The issue appears to stem from using Nginx to reach n8n.
After exposing port 5678 in the Docker setup and connecting to n8n directly on that port, everything works:

n8n:
  ports:
    - "5678:5678"

Now I need to investigate further to figure out what’s preventing access when Nginx sits in front.

5

Thanks, amazing debugging.
I’m using Caddy, I commented out this line in my Caddy header and that fixed the problem: # Content-Security-Policy “default-src ‘self’; script-src ‘self’ ‘unsafe-inline’; style-src ‘self’ ‘unsafe-inline’; img-src ‘self’ data:; connect-src ‘self’ ws: wss:;”