Some default nodes does not provide connecting points

[Batuhan_ALPEREN]

Describe the problem/error/question

As stated in the title, “On Webhook call“ trigger and “Basic LLM Chain“ seems to be not working as expected. I am using self hosted (Docker) with no extra configs.

For the “On Webhook call” trigger, I cannot connect the node to any other node. Because there is no connection point.

For the “Basic LLM Chain“ node, there is also no connection point and I cannot add any model to it.

I just started using n8n 2-3 days ago. Maybe I am doing something wrong. Did anyone came across this issue before?

Please share your workflow

Information on your n8n setup

• n8n version: 1.108.2
• Database (default: SQLite): SQLite
• n8n EXECUTIONS_PROCESS setting (default: own, main): idk
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker via Ubuntu based VPS and nginx reverse proxy.
• Operating system: Using the project on Windows 11 and hosted at Ubuntu machine.

Workflow Screenshot

[cutecatcode]

Hello @Batuhan_ALPEREN, welcome to community!
I don’t know what happen with your LLM Chain Node, because mine working fine.

Also, you cannot connect the Webhook Trigger to another node, because that’s a Trigger node. Not a regular node that can receive any input, it will Trigger the execution based from which Trigger node that you select.

[Batuhan_ALPEREN]

I suppose you didn’t check my “Workflow Screenshot”. I know that triggers cannot have inputs. Please re-read my issue.

[cutecatcode]

I saw your node, and maybe it’s a bug (?), try to upgrade to next version instead of using latest

[Batuhan_ALPEREN]

I’ve opened a github issue. I think it’s a bug too.

https://github.com/n8n-io/n8n/issues/19020

[cutecatcode]

Uh, I think it is.
Have you been copy my workflow btw?

[Batuhan_ALPEREN]

The issue was my NGINX config and maybe Cloudflare proxy. I managed to solve the issue by switching to Let’s Encrypt SSL and rewriting my whole NGINX config for the n8n domain.

NGINX config file:

server {
    listen 80;
    server_name <your-domain>;

    location / {
        proxy_pass http://127.0.0.1:5678;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        
        # WebSocket için doğru ayarlar
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_cache_bypass $http_upgrade;
        
        # Timeout'lar (WebSocket için önemli)
        proxy_read_timeout 3600;
        proxy_send_timeout 3600;
        proxy_connect_timeout 3600;
    }

    location /webhook/ {
        proxy_pass http://127.0.0.1:5678;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    location /webhook-test/ {
        proxy_pass http://127.0.0.1:5678;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    # Error Pages
    error_page 500 502 503 504 /50x.html;
    location = /50x.html {
        root /usr/share/nginx/html;
    }
}

I was using nginxconfig.io for the basic NGINX config. Most likely that was the problem.