Hey there! We've found the following might help you get unblocked faster:

• 🧵 Entire Workflow Freezes when adding a HTTP Node

• 🧵 Webhook -> HTTP Request (POST) Fails in a New Workflow

• 🧵 postgres can't login with new create user

• 🧵 YouTube Upload Node Works on n8n Cloud, But Fails with 400 Error on Railway

If you find the answer from one of these, please let us know by solving the thread!

Hyy @jessedanku

I investigated this and reproduced the symptoms described. Short version: this is not the HTTP node itself but the UI “push” channel (WebSocket / SSE) that the editor uses to get execution updates. When that channel is broken by a proxy / wrong public URL settings, the editor waits forever and throws Cannot read properties of undefined (reading 'execute'). Below are the practical fixes I recommend (apply in order) — I’ve included exact env vars and an Nginx snippet you can copy.

Quick checklist (apply & test after each step):

1. Confirm a simple GET (https://jsonplaceholder.typicode.com/todos/1) from an HTTP node — if it still freezes, proceed.

2. Ensure your reverse proxy supports WebSocket upgrades.

3. Configure n8n public URLs and proxy hops.

4. Optionally force SSE if WebSockets are blocked.

5. Enable runners so executions run outside the UI process.

6. If still failing, try a different n8n minor version (backup first).

1) Fix proxy (Nginx example)

If you use Nginx (or similar), make sure you forward Upgrade headers for websockets:

location / {
    proxy_pass http://127.0.0.1:5678;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}

If you’re on Railway / other managed proxies, ensure the platform doesn’t strip Upgrade/Connection headers.

2) Set n8n public URLs and proxy hops

Set these environment variables (replace <your-domain>):

N8N_EDITOR_BASE_URL=https://<your-domain>
WEBHOOK_URL=https://<your-domain>
N8N_HOST=<your-domain>
N8N_PROTOCOL=https
N8N_PROXY_HOPS=1
PORT=5678        # do NOT force 443 for N8N_PORT, leave default

These ensure the editor/backend compute the correct origin so the push channel can be established.

3) Force SSE if WebSockets are not allowed

If your hosting/proxy environment blocks WebSockets, force Server-Sent Events:

N8N_PUSH_BACKEND=sse
# or explicitly set `N8N_PUSH_BACKEND=websocket` to prefer websocket

Redeploy after changing this.

4) Enable background runners (recommended)

Offload execution from the main process (prevents UI process from blocking):

N8N_RUNNERS_ENABLED=true

Redeploy / restart the containers after setting.

5) Additional steps & Troubleshooting

• Check browser console for failed WS/SSE connection attempts (look for 101/upgrade failures or CORS/origin errors).

• Check n8n backend logs for errors about push connection / SSE / websocket.

• If the problem only occurs with HTTP node in this instance, try the same workflow on a fresh n8n instance (or different minor version) to rule out a version-specific bug. Always export workflows/credentials first.

Summary :

This freeze is almost always a broken push channel (WS/SSE) caused by proxy/origin misconfiguration — fix the proxy headers and public URLs (or force SSE), enable runners, and the HTTP node problem should disappear.

If you want, I can:

• provide a tailored Nginx/Traefik config for your exact Railway/docker setup, or

• test specific env values/steps you’ve tried and tell you exactly what to change next.

I Hope this solution fixes the issue for you :))