Webhook-test dont update frontend data to build workflows

In the N8n dashboard when i test a webhook, the data will not be updated but the test webhook triggered. So i cant see the flow in the dashboard and cant build new workflows with the data wich is provided in the tests.

Information on your n8n setup

  • n8n version: latest 0.160
  • Database you’re using (default: MySQL, Redis):
  • Running n8n with the execution process : Main
  • Running n8n via [Docker]:

With plesk im using nginx as proxy to get serve n8n over ssl:
n8n webinterface: n8n.domain.com
n8n webhook url: webhook.n8n.domain.com

nginx config for: n8n.domain.com
//This goes to the main process // This is working!
location ~ / {
proxy_redirect off;
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-Host $server_name;
proxy_pass http://localhost:5678;
}
//This goes to the worker process (For old webhooks installed on some services) this is working!
location ~ /webhook/ {
proxy_redirect off;
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-Host $server_name;
proxy_pass http://localhost:5680;
}

nginx config for: webhook.n8n.domain.com
//Pointing to the main process // Webook gets triggered and serves data but frontend doesnt show any changes!
location ~ /webhook-test/ {
proxy_redirect off;
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-Host $server_name;
proxy_pass http://localhost:5678;
}
//This is working too!
location ~ / {
proxy_redirect off;
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-Host $server_name;
proxy_pass http://localhost:5678;
}

Hey @Benedikt_Bohm,

I would say it might be worth updating if you are on 0.160.0 just to rule out anything that has been fixed. If you still see an issue press F12 to open the browser dev console then check to see if there are any errors.

I take it as you are using different URLs and ports you are running in queue mode as well?

Browser Console log (Browser: Brave):

DevTools failed to load source map: Could not load content for https://webhook.n8n.domain.com/js/chunk-vendors.07686313.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

DevTools failed to load source map: Could not load content for https://webhook.n8n.domain.com/js/app.fd95894c.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

app.fd95894c.js:1

Love n8n? Help us build the future of automation! n8n - Current Openings

DevTools failed to load source map: Could not load content for webpack://Quill/node_modules/quill-delta/dist/Delta.js.map: Fetch through target failed: Unsupported URL scheme; Fallback: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

DevTools failed to load source map: Could not load content for webpack://Quill/node_modules/quill-delta/dist/AttributeMap.js.map: Fetch through target failed: Unsupported URL scheme; Fallback: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

DevTools failed to load source map: Could not load content for webpack://Quill/node_modules/quill-delta/dist/Op.js.map: Fetch through target failed: Unsupported URL scheme; Fallback: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

DevTools failed to load source map: Could not load content for webpack://Quill/node_modules/quill-delta/dist/Iterator.js.map: Fetch through target failed: Unsupported URL scheme; Fallback: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

Yes im using the queue mode as well

Found more: Firefox kann keine Verbindung zu dem Server unter https://webhook.n8n.domain.com/rest/push?sessionId=99mdy3kce1d aufbauen.

Worker 1

docker run -d \

–name n8n-queue \

-p 5679:5678 \

-e DB_TYPE=“mysqldb” \

-e DB_MYSQLDB_DATABASE=“n8n” \

-e DB_MYSQLDB_HOST=“domain.com” \

-e DB_MYSQLDB_PORT=“3306” \

-e DB_MYSQLDB_USER=“n8n” \

-e DB_MYSQLDB_PASSWORD=“SECRET” \

-e N8N_BASIC_AUTH_ACTIVE=“true” \

-e N8N_BASIC_AUTH_USER=“admin” \

-e N8N_BASIC_AUTH_PASSWORD=“SECRET” \

-e N8N_HOST=“domain.com” \

-e N8N_PROTOCOL=“https” \

-e N8N_PORT=“5678” \

-e VUE_APP_URL_BASE_API=“https://domain.com/” \

-e WEBHOOK_TUNNEL_URL=“https://webhook.n8n.domain.com/” \

-e N8N_ENCRYPTION_KEY=“SECRET” \

-e EXECUTIONS_MODE=“queue” \

-e QUEUE_BULL_REDIS_HOST=“SERVERS-EXTERN-IP” \

-e QUEUE_BULL_REDIS_PORT=“6379” \

-e QUEUE_BULL_REDIS_PASSWORD=“SECRET” \

-e WEBHOOK_URL=“https://webhook.n8n.domain.com” \

n8nio/n8n n8n worker

Webhook

docker run -d \

–name n8n-webhook \

-p 5680:5678 \

-e DB_TYPE=“mysqldb” \

-e DB_MYSQLDB_DATABASE=“n8n” \

-e DB_MYSQLDB_HOST=“domain.com” \

-e DB_MYSQLDB_PORT=“3306” \

-e DB_MYSQLDB_USER=“n8n” \

-e DB_MYSQLDB_PASSWORD=“SECRET” \

-e N8N_BASIC_AUTH_ACTIVE=“true” \

-e N8N_BASIC_AUTH_USER=“admin” \

-e N8N_BASIC_AUTH_PASSWORD=“SECRET” \

-e N8N_HOST=“domain.com” \

-e N8N_PROTOCOL=“https” \

-e N8N_PORT=“5678” \

-e VUE_APP_URL_BASE_API=“https://domain.com/” \

-e WEBHOOK_TUNNEL_URL=“https://webhook.n8n.domain.com/” \

-e N8N_ENCRYPTION_KEY=“SECRET” \

-e EXECUTIONS_MODE=“queue” \

-e QUEUE_BULL_REDIS_HOST=“SERVERS-EXTERN-IP” \

-e QUEUE_BULL_REDIS_PORT=“6379” \

-e QUEUE_BULL_REDIS_PASSWORD=“SECRET” \

-e WEBHOOK_URL=“https://webhook.n8n.domain.com” \

n8nio/n8n n8n webhook

Main process

docker run \

–name n8n-main \

-p 5678:5678 \

-e DB_TYPE=“mysqldb” \

-e DB_MYSQLDB_DATABASE=“n8n” \

-e DB_MYSQLDB_HOST=“domain.com” \

-e DB_MYSQLDB_PORT=“3306” \

-e DB_MYSQLDB_USER=“n8n” \

-e DB_MYSQLDB_PASSWORD=“SECRET” \

-e N8N_BASIC_AUTH_ACTIVE=“true” \

-e N8N_BASIC_AUTH_USER=“admin” \

-e N8N_BASIC_AUTH_PASSWORD=“SECRET” \

-e N8N_HOST=“domain.com” \

-e N8N_PROTOCOL=“http” \

-e N8N_PORT=“5678” \

-e VUE_APP_URL_BASE_API=“https://domain.com/” \

-e WEBHOOK_TUNNEL_URL=“https://webhook.n8n.domain.com/” \

-e N8N_ENCRYPTION_KEY=“SECRET” \

-e EXECUTIONS_MODE=“queue” \

-e QUEUE_BULL_REDIS_HOST=“SERVERS-EXTERN-IP” \

-e QUEUE_BULL_REDIS_PORT=“6379” \

-e QUEUE_BULL_REDIS_PASSWORD=“SECRET” \

-e WEBHOOK_URL=“https://webhook.n8n.domain.com” \

n8nio/n8n n8n start

Anything in the network tab? I suspect this is going to be proxy related but I am not sure what it is yet.

Firefox Console Log:
Firefox kann keine Verbindung zu dem Server unter https://webhook.n8n.domain.com/rest/push?sessionId=hmzn3hcng1 aufbauen. app.fd95894c.js:1:281913
onmozfullscreenchange sollte nicht mehr verwendet werden. chunk-vendors.07686313.js line 563 > eval:52:37
onmozfullscreenerror sollte nicht mehr verwendet werden. chunk-vendors.07686313.js line 563 > eval:52:37

                                                                //////
                                                             ///////////
                                                           /////      ////
                                           ///////////////////         ////
                                         //////////////////////       ////
 ///////               ///////          ////                /////////////

//////////// //////////// //// ///////
//// //// //// //// ////
///// ///////////// //////////
///// //// //// //// ////
//////////// //////////// //// ////////
/////// ////// //// /////////////
///////////// ////
////////// ////
//// ////
///////////
//////

Love n8n? Help us build the future of automation! n8n - Current Openings
app.fd95894c.js:1:273278
Einige Cookies verwenden das empfohlene “SameSite”-Attribut inkorrekt. 2
Source-Map-Fehler: Error: request failed with status 401
Ressourcen-Adresse: https://webhook.n8n.domain.com/js/app.fd95894c.js
Source-Map-Adresse: app.fd95894c.js.map

Brave console log:
DevTools failed to load source map: Could not load content for https://webhook.n8n.xape.eu/js/chunk-vendors.07686313.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for https://webhook.n8n.xape.eu/js/app.fd95894c.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
app.fd95894c.js:1

Love n8n? Help us build the future of automation! n8n - Current Openings

DevTools failed to load source map: Could not load content for webpack://Quill/node_modules/quill-delta/dist/Delta.js.map: Fetch through target failed: Unsupported URL scheme; Fallback: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
DevTools failed to load source map: Could not load content for webpack://Quill/node_modules/quill-delta/dist/AttributeMap.js.map: Fetch through target failed: Unsupported URL scheme; Fallback: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
DevTools failed to load source map: Could not load content for webpack://Quill/node_modules/quill-delta/dist/Op.js.map: Fetch through target failed: Unsupported URL scheme; Fallback: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
DevTools failed to load source map: Could not load content for webpack://Quill/node_modules/quill-delta/dist/Iterator.js.map: Fetch through target failed: Unsupported URL scheme; Fallback: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

Firefox network tab everything status 200 except:
https://webhook.n8n.domain.com/rest/push?sessionId=z0b2voh6db

Brave network tab everything status 200 except:
https://webhook.n8n.domain.com/rest/push?sessionId=0i5s8ubnxw8s

When i hit this page in the browser its loading forever

If i call n8n without proxy its working

So i saw if i hit the URL /rest/push?sessionId=tfwsmghwrmm with the direct port to the n8n docker container that the page is loading always, every few seconds there will be a line with a “:” added. Maybe nginx is waiting till the request is complete and then sends over the proxy the complete message?

I think the way to setup n8n with plesk and use docker proxy rules is a common way to use docker containers on a server. Because backups etc is managed by plesk.

Maybe someone can tell me how the always loading pages are called so i can hopefully find a solution for it.

@jon i saw in the code the npm package “sse-channel” is used.
That nginx knows to send the data packages direct without buffering n8n needs to set a new header in the package “sse-channel”
(“X-Accel-Buffering”, “no”);

Hey @Benedikt_Bohm,

I will need to check my nginx config in the morning to see if I can spot the difference but it is good to know that it works direct.

Solution for nginx is:

proxy_http_version 1.1;
proxy_set_header Connection ‘’;
proxy_buffering off;
proxy_pass http://localhost:5678;
2 Likes