Unable to draw output connections from multiple nodes on self hosted n8n

[Chikwado]

<!-- He## Summary
Unable to draw output connections from multiple nodes. Output 
connection handles (circles on the right edge) are not rendering, 
preventing me from wiring nodes together in my workflow.
## Affected nodes
1. Webhook node — no output handle visible, even after receiving 
   test data successfully
2. AI Agent node — cannot connect to sub-nodes (Anthropic Chat 
   Model as Model input, Window Buffer Memory as Memory input)
## Environment
n8n version: 2.19.5 
Instance URL: workflows.seamfix.com.ng (self-hosted)
Browser tested: Chrome [version], Safari [version]
OS: macOS [version]
## Steps to reproduce
1. Create new workflow
2. Add Webhook node
3. Configure: POST method, path "sales-bot", Respond "Using 
   'Respond to Webhook' Node"
4. Save workflow
5. Click "Listen for test event"
6. Send a test POST request to the test URL
7. Webhook successfully captures data (output panel populates, 
   green checkmark appears)
8. Try to drag a connection from the Webhook node to the next 
   node (Message Parser)
## Expected behavior
A connection handle (small circle) should appear on the right 
edge of the Webhook node when hovered, allowing me to drag a 
connection line to the next node's input.
## Actual behavior
No output handle is visible at any zoom level. The node body 
itself cannot be used as a drag source. Reverse-direction 
dragging (from target node's input back to Webhook) also fails.
## What I've already tried
Zooming in to maximum to verify the handle isn't just tiny
Clicking on empty canvas to deselect, then hovering
Hard browser refresh (Cmd+Shift+R)
Closing and reopening the node panel
Tested in both Chrome and Safari — same result
Sending test data successfully (the node has valid output)
[Add: Whether you've tried deleting and recreating the node]
## Initial issue noticed
When the Webhook node was first created, its Test URL showed 
"/webhook-test/null" instead of "/webhook-test/sales-bot" — the 
webhook ID failed to generate. This may be related to the 
broken handle rendering.
## Screenshots
![Scree

nshot 2026-05-26 at 4.30.29 PM|690x192](upload://8jQ4tVFcyqmFVUhv7LMcy5rWB6R.png)
![Screenshot 2026-05-26 at 4.31.40 PM|690x220](upload://mrpo1SlTR04e5CkY7b6IYcQoqQq.png)
![Screenshot 2026-05-26 at 4.31.57 PM|690x408](upload://1eiw2NochNJzJHNYfyKDqCGCVd5.jpeg)
-->

Describe the problem/error/question

<!-- n8n Cloud users: If you're experiencing issues with your cloud instance (e.g., can't sign in, instance unavailable), please contact support at help@n8n.io -->

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

<!-- If you need help with data transformations, please also share your expected output. -->

Information on your n8n setup

n8n version

Database (default: SQLite):

n8n EXECUTIONS_PROCESS setting (default: own, main):

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

Operating system:

[achamm]

@Chikwado can u share a screenshot (or short screen recording) of what happens when u try to draw the connection — does the line not appear at all, snap back, or fail at a specific node? and which n8n version + browser? canvas/UI issues are usually pretty version + render-context specific.

[Chikwado]

HI

Hi @Achamm, thank you for your response.
it doesnt drag . there is nothing to drag. i have tried it on chrome and safari. the version is 2.19.5

[kjooleng]

@Chikwado , can you try this?

Copy this workflow and modify to your own usage

[Dero.Dev]

Since you are self hosting have you tried properly tunneling traffic most likely through routing it via cloudFlare. That way you could have webhook activated on your self hosted server. Other than that you would experience multiple issues with setting up webhook connections on your self hosted server

[Chikwado]

Hello Kjooleng, i tried this flow as it is and got same issue. here are the screenshots:

[kjooleng]

Seems to be an issue with your n8n installation.

Have you tried n8n re-install?

[Anshul_Namdev]

Hi @Chikwado
See this:

No Output Port on Webhook Trigger

Describe the problem/error/question I want to use a Webhook Trigger and everything is working with the test events, but on my output side I don’t see any port to connect the workflow with the trigger Please share your workflow [{6D9F68F6-F190-43DE-B9A0-2A881A4BED8E}] Information on your n8n setup n8n version: latest stable Running n8n via docker on Linux with nginx config

Some default nodes does not provide connecting points

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 an…

I don’t think so it will solve the problem with switching browsers/proxy, but still give it a try

[Chikwado]

Hi @kjooleng, yes i have. also, when i first encountered the problem, i was working on version 2.18. version. i upgraded to 2.19.5. same issue

[Chikwado]

Hi @Anshul_Namdev, thank you for the advice.
i have switched between chrome and safari, it didnt solve it

[kjooleng]

Are you using any nginx or any reverse proxy, @Chikwado ?

If so, you may need something like this for nginx config

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 support
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_cache_bypass $http_upgrade;

        # Timeouts (important for WebSocket)
        proxy_read_timeout 3600;
        proxy_send_timeout 3600;
        proxy_connect_timeout 3600;
    }
}

[Chikwado]

Hi @kjooleng ,
thank you for help. very grateful. sorry i am just replying. yesterday was a holiday in my country, i relayed your questions to the devop team and i am just getting response:
yes, we are using nginx for porxy

[Chikwado]

Summary

Unable to draw output connections from multiple nodes. Output
connection handles (circles on the right edge) are not rendering,
preventing me from wiring nodes together in my workflow.

Affected nodes

1. Webhook node — no output handle visible, even after receiving
   test data successfully
2. AI Agent node — cannot connect to sub-nodes (Anthropic Chat
   Model as Model input, Window Buffer Memory as Memory input)

Environment

n8n version: 2.19.5 (or whatever the real version is)
Instance URL: workflows.seamfix.com.ng (self-hosted)
Browser tested: Chrome [version], Safari [version]
OS: macOS [version]

Steps to reproduce

1. Create new workflow
2. Add Webhook node
3. Configure: POST method, path “sales-bot”, Respond “Using
   ‘Respond to Webhook’ Node”
4. Save workflow
5. Click “Listen for test event”
6. Send a test POST request to the test URL
7. Webhook successfully captures data (output panel populates,
   green checkmark appears)
8. Try to drag a connection from the Webhook node to the next
   node (Message Parser)

Expected behavior

A connection handle (small circle) should appear on the right
edge of the Webhook node when hovered, allowing me to drag a
connection line to the next node’s input.

Actual behavior

No output handle is visible at any zoom level. The node body
itself cannot be used as a drag source. Reverse-direction
dragging (from target node’s input back to Webhook) also fails.

What I’ve already tried

Zooming in to maximum to verify the handle isn’t just tiny
Clicking on empty canvas to deselect, then hovering
Hard browser refresh (Cmd+Shift+R)
Closing and reopening the node panel
Tested in both Chrome and Safari — same result
Sending test data successfully (the node has valid output)
[Add: Whether you’ve tried deleting and recreating the node]

Initial issue noticed

When the Webhook node was first created, its Test URL showed
“/webhook-test/null” instead of “/webhook-test/sales-bot” — the
webhook ID failed to generate. This may be related to the
broken handle rendering.

Screenshots

[tamy.santos]

@Chikwado welcome to the n8n community.
new release with fixes on 01/06
Release notes | n8n Docs