Test webhook works fine but production do nothing/ What is wrong?

Questions
1

Describe the problem/error/question

Postman window screenshot : Awesome Screenshot
Easy workflow: webhook GET node connected to Set node. Test URL works fine in Postman but production do nothing.

What is the error message (if any)?

Here is my DB

/home/node # sqlite3 /home/node/.n8n/database.sqlite
SQLite version 3.48.0 2025-01-14 11:05:00
Enter “.help” for usage hints.
sqlite> .tables
annotation_tag_entity migrations
auth_identity processed_data
auth_provider_sync_history project
credentials_entity project_relation
event_destinations settings
execution_annotation_tags shared_credentials
execution_annotations shared_workflow
execution_data tag_entity
execution_entity test_case_execution
execution_metadata test_run
folder user
folder_tag user_api_keys
insights_by_period variables
insights_metadata webhook_entity
insights_raw workflow_entity
installed_nodes workflow_history
installed_packages workflow_statistics
invalid_auth_token workflows_tags
sqlite> SELECT * FROM webhook_entity; ### ← Workflow was active
4r360oJti7AVMr9k|ea299d62-164f-482d-ad88-c30f3c535e0c|GET|Webhook|| ## There is hook
sqlite> SELECT * FROM webhook_entity; ### ← Set Workflow isnactive via UI, made SELECT, table is empty
sqlite> SELECT * FROM webhook_entity; ### set workflow active again
4r360oJti7AVMr9k|ea299d62-164f-482d-ad88-c30f3c535e0c|GET|Webhook|| ## There is hook
sqlite>

So webhook entity appears and disappears as in should

Traefik log

2025-06-04T10:32:48Z DBG traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:173 > Service selected by WRR: http://172.18.0.2:5678
2025-06-04T10:40:36Z DBG traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:173 > Service selected by WRR: http://172.18.0.2:5678
2025-06-04T10:40:44Z DBG traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:173 > Service selected by WRR: http://172.18.0.2:5678

It recieves request from Postman and pass it to n8n - OK
But n8n DO NOTHING! )))

n8N log

2025-06-04T10:30:30.354Z [Rudder] debug: no existing flush timer, creating new one
2025-06-04T10:30:40.355Z [Rudder] debug: in flush
2025-06-04T10:30:40.355Z [Rudder] debug: cancelling existing flushTimer…
2025-06-04T10:30:45.504Z [Rudder] debug: no existing flush timer, creating new one
2025-06-04T10:30:45.510Z | debug | Added webhooks for workflow “Easy webhook” (ID 4r360oJti7AVMr9k) {“scopes”:[“workflow-activation”],“workflowId”:“4r360oJti7AVMr9k”,“file”:“active-workflow-manager.js”,“function”:“addWebhooks”}
2025-06-04T10:30:47.456Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:30:47.456Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:30:55.507Z [Rudder] debug: in flush
2025-06-04T10:30:55.507Z [Rudder] debug: cancelling existing flushTimer…
2025-06-04T10:31:15.813Z | debug | Querying database for waiting executions {“scopes”:[“waiting-executions”],“file”:“wait-tracker.js”,“function”:“getWaitingExecutions”}
2025-06-04T10:31:17.460Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:31:17.460Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:31:47.462Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:31:47.462Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:32:15.817Z | debug | Querying database for waiting executions {“scopes”:[“waiting-executions”],“file”:“wait-tracker.js”,“function”:“getWaitingExecutions”}
2025-06-04T10:32:17.468Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:32:17.469Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:32:47.472Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:32:47.473Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:33:15.822Z | debug | Querying database for waiting executions {“scopes”:[“waiting-executions”],“file”:“wait-tracker.js”,“function”:“getWaitingExecutions”}
2025-06-04T10:33:17.475Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:33:17.476Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:33:17.491Z | debug | Found no executions to hard-delete {“scopes”:[“pruning”],“file”:“executions-pruning.service.js”,“function”:“hardDelete”}
2025-06-04T10:33:17.491Z | debug | Hard-deletion in next 15 minutes {“scopes”:[“pruning”],“file”:“executions-pruning.service.js”,“function”:“scheduleNextHardDeletion”}
2025-06-04T10:33:47.478Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:33:47.479Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:34:15.824Z | debug | Querying database for waiting executions {“scopes”:[“waiting-executions”],“file”:“wait-tracker.js”,“function”:“getWaitingExecutions”}
2025-06-04T10:34:17.481Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:34:17.481Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:34:47.483Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:34:47.484Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:35:15.824Z | debug | Querying database for waiting executions {“scopes”:[“waiting-executions”],“file”:“wait-tracker.js”,“function”:“getWaitingExecutions”}
2025-06-04T10:35:17.485Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:35:17.486Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:35:47.488Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:35:47.489Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:36:15.826Z | debug | Querying database for waiting executions {“scopes”:[“waiting-executions”],“file”:“wait-tracker.js”,“function”:“getWaitingExecutions”}
2025-06-04T10:36:17.490Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:36:17.491Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:36:47.492Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:36:47.493Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:37:15.827Z | debug | Querying database for waiting executions {“scopes”:[“waiting-executions”],“file”:“wait-tracker.js”,“function”:“getWaitingExecutions”}
2025-06-04T10:37:17.495Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:37:17.495Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:37:47.497Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:37:47.497Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:38:15.827Z | debug | Querying database for waiting executions {“scopes”:[“waiting-executions”],“file”:“wait-tracker.js”,“function”:“getWaitingExecutions”}
2025-06-04T10:38:17.498Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:38:17.499Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:38:47.500Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:38:47.501Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:39:15.832Z | debug | Querying database for waiting executions {“scopes”:[“waiting-executions”],“file”:“wait-tracker.js”,“function”:“getWaitingExecutions”}
2025-06-04T10:39:17.502Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:39:17.502Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:39:47.503Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:39:47.504Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:40:15.833Z | debug | Querying database for waiting executions {“scopes”:[“waiting-executions”],“file”:“wait-tracker.js”,“function”:“getWaitingExecutions”}
2025-06-04T10:40:17.505Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:40:17.505Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:40:47.506Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:40:47.506Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:41:15.841Z | debug | Querying database for waiting executions {“scopes”:[“waiting-executions”],“file”:“wait-tracker.js”,“function”:“getWaitingExecutions”}
2025-06-04T10:41:17.507Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:41:17.507Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:41:47.509Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:41:47.509Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:42:15.841Z | debug | Querying database for waiting executions {“scopes”:[“waiting-executions”],“file”:“wait-tracker.js”,“function”:“getWaitingExecutions”}
2025-06-04T10:42:17.509Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:42:17.509Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:42:47.509Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:42:47.510Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:43:15.841Z | debug | Querying database for waiting executions {“scopes”:[“waiting-executions”],“file”:“wait-tracker.js”,“function”:“getWaitingExecutions”}
2025-06-04T10:43:17.511Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:43:17.511Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:43:47.512Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:43:47.517Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:44:15.841Z | debug | Querying database for waiting executions {“scopes”:[“waiting-executions”],“file”:“wait-tracker.js”,“function”:“getWaitingExecutions”}
2025-06-04T10:44:17.513Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:44:17.514Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:44:47.516Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:44:47.516Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:45:15.842Z | debug | Querying database for waiting executions {“scopes”:[“waiting-executions”],“file”:“wait-tracker.js”,“function”:“getWaitingExecutions”}
2025-06-04T10:45:17.518Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:45:17.518Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:45:47.519Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:45:47.520Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}
2025-06-04T10:46:15.843Z | debug | Querying database for waiting executions {“scopes”:[“waiting-executions”],“file”:“wait-tracker.js”,“function”:“getWaitingExecutions”}
2025-06-04T10:46:17.522Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”}
2025-06-04T10:46:17.522Z | debug | Started flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“startFlushingTimer”}

Please share your workflow

{
“nodes”: [
{
“parameters”: {
“path”: “ea299d62-164f-482d-ad88-c30f3c535e0c”,
“options”: {}
},
“type”: “n8n-nodes-base.webhook”,
“typeVersion”: 2,
“position”: [
-120,
0
],
“id”: “e3633ee9-c564-488d-b581-2f118e88edab”,
“name”: “Webhook”,
“webhookId”: “ea299d62-164f-482d-ad88-c30f3c535e0c”
},
{
“parameters”: {
“assignments”: {
“assignments”: [
{
“id”: “58fca696-dc60-4895-b16c-f1081b7347fb”,
“name”: “body”,
“value”: “={{ $json.body }}”,
“type”: “string”
}
]
},
“options”: {}
},
“type”: “n8n-nodes-base.set”,
“typeVersion”: 3.4,
“position”: [
220,
0
],
“id”: “bf4ede03-e742-4b2f-8e3a-b378f1d6478d”,
“name”: “Edit Fields”
}
],
“connections”: {
“Webhook”: {
“main”: [
[
{
“node”: “Edit Fields”,
“type”: “main”,
“index”: 0
}
]
]
}
},
“pinData”: {},
“meta”: {
“instanceId”: “742c899cd25fa91792ae2856cef673804f2bbd17a8c907d22153cda8d1a7cae5”
}
}
(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:** 1.95.3
- **Database (default: SQLite):**
- **n8n EXECUTIONS_PROCESS setting (default: own, main):** not set in docker-compose.yml
- **Running n8n via (Docker, npm, n8n cloud, desktop app):** Docker
- **Operating system:**  Ubuntu 22.04.5 LTS

![image|527x500](upload://bc8zeUMZDC0NwOlMAXi0wYo7PPj.png)
----------------- docker-compose.YML ---------------------------
services:
  traefik:
    image: "traefik"
    restart: always
    command:
      - "--api=true"
      - "--api.insecure=true"
      - "--providers.docker=true"
      - "--providers.docker.exposedbydefault=false"
      - "--entrypoints.web.address=:80"
      - "--entrypoints.web.http.redirections.entryPoint.to=websecure"
      - "--entrypoints.web.http.redirections.entrypoint.scheme=https"
      - "--entrypoints.websecure.address=:443"
      - "--certificatesresolvers.mytlschallenge.acme.tlschallenge=true"
      - "--certificatesresolvers.mytlschallenge.acme.email=${SSL_EMAIL}"
      - "--certificatesresolvers.mytlschallenge.acme.storage=/letsencrypt/acme.json"
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - traefik_data:/letsencrypt
      - /var/run/docker.sock:/var/run/docker.sock:ro

  n8n:
    image: docker.n8n.io/n8nio/n8n
    restart: always
    ports:
      - "127.0.0.1:5678:5678"
    labels:
      - traefik.enable=true
      - traefik.http.routers.n8n.rule=Host(`${SUBDOMAIN}.${DOMAIN_NAME}`)
      - traefik.http.routers.n8n.tls=true
      - traefik.http.routers.n8n.entrypoints=web,websecure
      - traefik.http.routers.n8n.tls.certresolver=mytlschallenge
      - traefik.http.middlewares.n8n.headers.SSLRedirect=true
      - traefik.http.middlewares.n8n.headers.STSSeconds=315360000
      - traefik.http.middlewares.n8n.headers.browserXSSFilter=true
      - traefik.http.middlewares.n8n.headers.contentTypeNosniff=true
      - traefik.http.middlewares.n8n.headers.forceSTSHeader=true
      - traefik.http.middlewares.n8n.headers.SSLHost=${DOMAIN_NAME}
      - traefik.http.middlewares.n8n.headers.STSIncludeSubdomains=true
      - traefik.http.middlewares.n8n.headers.STSPreload=true
      - traefik.http.routers.n8n.middlewares=n8n@docker
    environment:
      - N8N_HOST=${SUBDOMAIN}.${DOMAIN_NAME}
      - N8N_PORT=5678
      - N8N_PROTOCOL=https
      - NODE_ENV=production
      - WEBHOOK_URL=https://${SUBDOMAIN}.${DOMAIN_NAME}/
      - WEBHOOK_TUNNEL_URL=https://${SUBDOMAIN}.${DOMAIN_NAME}/
      - GENERIC_TIMEZONE=${GENERIC_TIMEZONE}
      - N8N_DISABLE_PRODUCTION_MAIN_PROCESS=true
      - EXTERNAL_MODULES_ALLOW_LIST=*
#new
      - NODE_FUNCTION_ALLOW_BUILTIN=*
      - NODE_FUNCTION_ALLOW_EXTERNAL=*
# end new
#      - NODE_PATH=/usr/local/lib/node_modules
      - NODE_PATH=/data/node_modules

    volumes:
      - n8n_data:/home/node/.n8n
      - ./local-files:/files
#      - /n8n-packages/node_modules:/data/node_modules

volumes:
  n8n_data:
  traefik_data:
2

Just a quick check.

Screenshot_20250604_202826_2fOx10aK@2x
Screenshot_20250604_202826_2fOx10aK@2x266×124 1.82 KB

Did you active first and test the production url?

production url only working when workflow turn to activate.

The html code you show in Postman seems mean 404 not found in html code.

3

Yep workflow is active. I played around with activate/inactivate workflow and checked database for changes

sqlite> SELECT * FROM webhook_entity; ### ← Workflow was active
4r360oJti7AVMr9k|ea299d62-164f-482d-ad88-c30f3c535e0c|GET|Webhook|| ## There is hook
sqlite> SELECT * FROM webhook_entity; ### ← Set Workflow inactive via UI, made SELECT, table is empty
sqlite> SELECT * FROM webhook_entity; ### set workflow active again
4r360oJti7AVMr9k|ea299d62-164f-482d-ad88-c30f3c535e0c|GET|Webhook|| ## There is hook

With regard to Postman screenshot, you are right. Response is 200, text: ‘404 Ooops’ usual response from n8n.

4

I believe 127.0.0.1:5678:5678 will make n8n only listen to local host confined to the container.

ports:
- “127.0.0.1:5678:5678”

Try:

ports:
- “5678:5678”

5

Tnx, Falds. I tried this. No luck

6

DRILL, BABY, DRILL!

 Workflow is active, Webhook is GET
 OK. Iam inside n8n container
 
 docker exec -u root -it n8n-compose-n8n-1 /bin/sh
 
 Here is table

/home/node # sqlite3 /home/node/.n8n/database.sqlite
SQLite version 3.48.0 2025-01-14 11:05:00
Enter “.help” for usage hints.
sqlite> SELECT * FROM active_workflow_entity;
Parse error: no such table: active_workflow_entity
sqlite> .tables
annotation_tag_entity migrations
auth_identity processed_data
auth_provider_sync_history project
credentials_entity project_relation
event_destinations settings
execution_annotation_tags shared_credentials
execution_annotations shared_workflow
execution_data tag_entity
execution_entity test_case_execution
execution_metadata test_run
folder user
folder_tag user_api_keys
insights_by_period variables
insights_metadata webhook_entity
insights_raw workflow_entity
installed_nodes workflow_history
installed_packages workflow_statistics
invalid_auth_token workflows_tags
sqlite> SELECT * FROM webhook_entity;
4r360oJti7AVMr9k|ea299d62-164f-482d-ad88-c30f3c535e0c|GET|Webhook||
sqlite>

4r360oJti7AVMr9k|ea299d62-164f-482d-ad88-c30f3c535e0c|GET|Webhook||

BOOM!

/home/node # curl -X GET “http://localhost:5678/webhook/ea299d62-164f-482d-ad88-c30f3c535e0c/” \

 -H "Content-Type: application/json" \
 -d '{"message":"Hello from inside the container!"}'

            <meta charset="utf-8" />
            <meta http-equiv="X-UA-Compatible" content="IE=edge" />
            <meta name="viewport" content="width=device-width,initial-scale=1.0" />
            <link rel="icon" href="/favicon.ico" />
            <style>@media (prefers-color-scheme: dark) { body { background-color: rgb(45, 46, 46) } }</style>
            <script type="text/javascript">
                    window.BASE_PATH = '/';
                    window.REST_ENDPOINT = 'rest';
            </script>
            <script src="/rest/sentry.js"></script>
            <script>!function(t,e){var o,n,p,r;e.__SV||(window.posthog=e,e._i=[],e.init=function(i,s,a){function g(t,e){var o=e.split(".");2==o.length&&(t=t[o[0]],e=o[1]),t[e]=function(){t.push([e].concat(Array.prototype.slice.call(arguments,0)))}}(p=t.createElement("script")).type="text/javascript",p.async=!0,p.src=s.api_host+"/static/array.js",(r=t.getElementsByTagName("script")[0]).parentNode.insertBefore(p,r);var u=e;for(void 0!==a?u=e[a]=[]:a="posthog",u.people=u.people||[],u.toString=function(t){var e="posthog";return"posthog"!==a&&(e+="."+a),t||(e+=" (stub)"),e},u.people.toString=function(){return u.toString(1)+".people (stub)"},o="capture identify alias people.set people.set_once set_config register register_once unregister opt_out_capturing has_opted_out_capturing opt_in_capturing reset isFeatureEnabled getFeatureFlag onFeatureFlags reloadFeatureFlags".split(" "),n=0;n<o.length;n++)g(u,o[n]);e._i.push([i,s,a])},e.__SV=1)}(document,window.posthog||[])</script>

            <title>n8n.io - Workflow Automation</title>
            <script type="module" crossorigin src="/assets/index-yHq_9MHK.js"></script>
            <link rel="stylesheet" crossorigin href="/assets/index-DH8MNLw5.css">
    </head>
    <body>
            <noscript>
                    <strong
                            >We're sorry but the n8n Editor-UI doesn't work properly without JavaScript enabled. Please
                            enable it to continue.</strong
                    >
            </noscript>
            <div id="app"></div>
    </body>

It makes me insane!!! )))

7

Rolled back to 1.92.0, 1.8.0 No luck. In vain. Think to go from scratch with npm maybe.
Waiting for community opinion 4 this choice. Tnx in adv guys

8

I removed from docker-compose.yml:

  • N8N_DISABLE_PRODUCTION_MAIN_PROCESS=true
  • N8N_RUNNERS_ENABLED=true

Now n8n works like a charm!

1 Like
9

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.