The Chat component is not connecting to the

I have a simple chat workflow that I have copied from the template page:

{
“name”: “Chat with local LLMs using n8n and Ollama”,
“nodes”: [
{
“parameters”: {
“options”: {}
},
“id”: “475385fa-28f3-45c4-bd1a-10dde79f74f2”,
“name”: “When chat message received”,
“type”: “@n8n/n8n-nodes-langchain.chatTrigger”,
“position”: [
912,
624
],
“webhookId”: “ebdeba3f-6b4f-49f3-ba0a-8253dd226161”,
“typeVersion”: 1.1
},
{
“parameters”: {
“options”: {}
},
“id”: “61133dc6-dcd9-44ff-85f2-5d8cc2ce813e”,
“name”: “Ollama Chat Model”,
“type”: “@n8n/n8n-nodes-langchain.lmChatOllama”,
“position”: [
1104,
784
],
“typeVersion”: 1,
“credentials”: {
“ollamaApi”: {
“id”: “lCtwNqRXjkJytDLf”,
“name”: “Ollama Test”
}
}
},
{
“parameters”: {
“content”: “## Chat with local LLMs using n8n and Ollama\nThis n8n workflow allows you to seamlessly interact with your self-hosted Large Language Models (LLMs) through a user-friendly chat interface. By connecting to Ollama, a powerful tool for managing local LLMs, you can send prompts and receive AI-generated responses directly within n8n.\n\n### How it works\n1. When chat message received: Captures the user’s input from the chat interface.\n2. Chat LLM Chain: Sends the input to the Ollama server and receives the AI-generated response.\n3. Delivers the LLM’s response back to the chat interface.\n\n### Set up steps\n* Make sure Ollama is installed and running on your machine before executing this workflow.\n* Edit the Ollama address if different from the default.\n”,
“height”: 473,
“width”: 485
},
“id”: “3e89571f-7c87-44c6-8cfd-4903d5e1cdc5”,
“name”: “Sticky Note”,
“type”: “n8n-nodes-base.stickyNote”,
“position”: [
368,
240
],
“typeVersion”: 1
},
{
“parameters”: {
“content”: “## Ollama setup\n* Connect to your local Ollama, usually on http://localhost:11434\n* If running in Docker, make sure that the n8n container has access to the host’s network in order to connect to Ollama. You can do this by passing --net=host option when starting the n8n Docker container”,
“height”: 258,
“width”: 368,
“color”: 6
},
“id”: “9345cadf-a72e-4d3d-b9f0-d670744065fe”,
“name”: “Sticky Note1”,
“type”: “n8n-nodes-base.stickyNote”,
“position”: [
1280,
800
],
“typeVersion”: 1
},
{
“parameters”: {},
“id”: “eeffdd4e-6795-4ebc-84f7-87b5ac4167d9”,
“name”: “Chat LLM Chain”,
“type”: “@n8n/n8n-nodes-langchain.chainLlm”,
“position”: [
1136,
624
],
“typeVersion”: 1.4
}
],
“pinData”: {},
“connections”: {
“Ollama Chat Model”: {
“ai_languageModel”: [
[
{
“node”: “Chat LLM Chain”,
“type”: “ai_languageModel”,
“index”: 0
}
]
]
},
“When chat message received”: {
“main”: [
[
{
“node”: “Chat LLM Chain”,
“type”: “main”,
“index”: 0
}
]
]
}
},
“active”: false,
“settings”: {
“executionOrder”: “v1”,
“binaryMode”: “separate”,
“availableInMCP”: false
},
“versionId”: “4175a286-4d6a-42a5-915e-f8855614221f”,
“meta”: {
“templateId”: “2384”,
“templateCredsSetupCompleted”: true,
“instanceId”: “92d82d8eddeb75c1632295d367de7c0a28a1a65bbe8e484bc9236a3b35962a42”
},
“nodeGroups”: ,
“id”: “rR55c5eeONtyLGm9”,
“tags”:
}
I am using N8N at http://192.168.2.145:11434. The LLM I am using on ollama is llama3.2:latest.
Unfortunately, when I run the workflow, regardless of what I enter into the chat I get
the following error:
Error: Failed to receive response
When I check the Chat component output, I am seeing “no chat output”. And of course, there is no
input data received by the “Chat LLM Chain” component.
There was another post where the person was unable to receive a response using the chat component.
The solution was to set up the editor URL:

I tried that. It didn’t work.
Is there something wrong with the Chat component? Or am I missing something in the configuration
of the components?
Someone please advise.

Hey @factor3, while you wait for a response, here are some things that might help:

Suggested resources

Automatically matched to your question.

Docs:

Forum:

@kjooleng, @DylanS - you’ve helped with similar issues before, can you take a look?

Automatically suggested by n8n’s community bot. It’s a pilot - please share feedback here.

Hello @factor3 ! I hope your doing well! Those webhooks env vars are the wrong thing here, ollama binds to 127.0.0.1 by defualt setup, so it refuses connections from ur lan IP. Set ollama host to 0.0.0.0 and restart ollama. You don’t need the workflow active to test from the editor, so dw about that!

Hi @factor3
n8n builds the chat endpoint URL from those two vars, so localhost only resolves when the browser runs on the same machine as n8n. From any other machine the chat widget posts to a host it can’t reach and the workflow never starts, which is why the Chain gets no input. Set them to the exact address you type to open the editor:

N8N_EDITOR_BASE_URL=http://192.168.2.x:5678
N8N_WEBHOOK_URL=http://192.168.2.x:5678/

N8N_WEBHOOK_URL is the current name for WEBHOOK_URL, which still works but logs a deprecation warning. Restart the container, then send a chat message with DevTools open on the Network tab, the request should go to that address instead of localhost.
See this:

Actually, n8n:

I already have ollama set to use 0.0.0.0.

Those settings I am referring to are for N8N, not ollama.

oh okay, I misunderstood! well anshuls fix should work for you!

Anshul_Namdev:

I have just made the changes you suggested. I am still getting the connection error.

BTW: The link you referred to is where I found the settings for N8N_EDITOR_BASE_URL and WEBHOOK_URL that I originally used.

N8N_HOST is still on its default of localhost. Set it to the exact address you open n8n on, along with the port and protocol:

N8N_HOST=<the IP you open n8n on>
N8N_PORT=5678
N8N_PROTOCOL=http

If you’re on Docker Compose, docker compose restart reuses the old environment, so apply it with docker compose up -d --force-recreate.
See this:

Greetings, Hammad_gaming:

I have attempted a chat, got the connection error, and checked the Overview->Executions.
There are no executions shown.

I am running N8N using docker compose. My compose.yml file is below:

services:
  n8n:
    image: n8nio/n8n:latest
    restart: unless-stopped
	container_name: n8n
    environment:
      - DB_TYPE=postgresdb
      - DB_POSTGRESDB_HOST=postgres
      - DB_POSTGRESDB_PORT=5432
      - DB_POSTGRESDB_DATABASE=n8n
      - DB_POSTGRESDB_USER=n8n
      - DB_POSTGRESDB_PASSWORD=o3RhdvBB3nJDtn
      - N8N_BASIC_AUTH_ACTIVE=true
      - N8N_BASIC_AUTH_USER=admin
      - N8N_BASIC_AUTH_PASSWORD=<Redacted>
      - N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=false
      - N8N_HOST=192.168.2.145
      - N8N_PORT=5678
      - N8N_PROTOCOL=http
      - N8N_EDITOR_BASE_URL=http://192.168.2.145:5678
      - N8N_WEBHOOK_URL=http://192.168.2.145:5678/
    ports:
      - "5678:5678"
    volumes:
      - ./n8n_data:/home/node/.n8n
    networks:
      - n8n-network
    depends_on:
      - postgres

  postgres:
    image: postgres:15
    restart: unless-stopped
    environment:
      - POSTGRES_USER=n8n
      - POSTGRES_PASSWORD=<redacted>
      - POSTGRES_DB=n8n
    ports:
      - "5434:5432"
    volumes:
      - ./postgres_data:/var/lib/postgresql/data
    networks:
      - n8n-network

volumes:
  n8n_data:
  postgres_data:

networks:
  n8n-network:
    external: true   


I am still getting the connection errors when I try to chat.

FYI: N8N is running on a different machine than ollama.

I have done the docker exec command that you suggested, changing the IP to the machine
running ollama. It worked without problems, displaying the tags.

I am running N8N in the following manner:

docker compose up -d --force-recreate && docker compose logs -f

and I am seeing some interesting log entries:

n8n | Initializing n8n process
n8n | n8n ready on ::, port 5678
n8n | Acquiring database migration lock…
n8n | n8n Task Broker ready on 127.0.0.1, port 5679
n8n | Failed to start Python task runner in internal mode. because Python 3 is missing from this system. Launching a Python runner in internal mode is intended o
ly for debugging and is not recommended for production. Users are encouraged to deploy in external mode. See: Set up task runners | Deploy | n8n Docs
ing-up-external-mode
n8n | Deprecation warning: The storage directory “/home/node/.n8n/binaryData” will be renamed to “/home/node/.n8n/storage” in n8n v3. To migrate now, set N8N_MIG
ATE_FS_STORAGE_PATH=true. If you have a volume mounted at the old path, update your mount configuration after migration.
n8n |
n8n | There are deprecations related to your n8n setup. Please take the recommended actions to update your configuration:
n8n | - N8N_UNVERIFIED_PACKAGES_ENABLED → The default for this variable will change to false in a future version. Set it to true explicitly to keep install
ng unverified community packages.
n8n | - N8N_RUNNERS_TASK_TIMEOUT → The default for this variable will be reduced from 300 (5 minutes) to 60 (1 minute) in a future version. Set it explicitly t
keep your current task timeout.
n8n | - N8N_COMPRESSION_NODE_MAX_DECOMPRESSED_SIZE_BYTES → The default for this variable will be reduced from 2 GiB to 256 MiB in a future version. Set it expl
citly to keep your current limit.
n8n | - N8N_COMPRESSION_NODE_MAX_ZIP_ENTRIES → The default for this variable will be reduced from 5000 to 1000 in a future version. Set it explicitly to keep yur current limit.
n8n |
n8n | [license SDK] Skipping renewal on init: license cert is not initialized
n8n | (node:7) DeprecationWarning: Calling client.query() when the client is already executing a query is deprecated and will be removed in pg@9.0. Use async/awa
t or an external async flow control mechanism instead.
n8n | (Use node --trace-deprecation ... to show where the warning was created)
n8n | Registered runner “JS Task Runner” (X2laGdzKHKQXahbLDHLEh)
n8n | Instance registered
n8n | Discovered 4 cluster checks
n8n | Version: 2.33.4
n8n | Building workflow dependency index…
n8n |
n8n | Editor is now accessible via:
n8n | http://192.168.2.145:5678
n8n | Finished building workflow dependency index. Processed 0 draft workflows, 0 published workflows.
^

I do understand the deprecation warnings, and will deal with them shortly. What is particularly
interesting are the license cert not being initialized, and the fact that the workflow dependency index is not initialized and that there are no draft workflows being processed. I don’t know if those
are affecting the chat’s operation, but I am adding them just in case.

@factor3 Can you screenshot your console when n8n sends the request? Its option - command - I or windows key instead of command

@factor3 Thanks, that rules out my theory. No executions means the request never reaches n8n, so forget the SSE idea.

Quick test worth doing: drop a Form trigger or plain Webhook on a scratch workflow and see if that fires. Someone on 2.11 had exactly the same, nothing in the docker logs, form and webhook fine, chat trigger alone doing nothing. He went back to 1.123 to get it working.

Most of that thread is reverse proxy stuff that won’t apply to you, but the start matches your setup. If form and webhook work and chat doesn’t, it’s the node, not your compose file.

Also, “Processed 0 draft workflows, 0 published workflows” in your log stood out. Does your workflow show up in the workflows list after a restart?

achamm:

That was a good question. Below is the console output of an N8N session. Please note how the Chat request is failing (at line 104).

Blocked loading mixed active content “http://192.168.2.145:5678/rest/ph/static/array.js” signin
Loading failed for the <script> with source “http://192.168.2.145:5678/rest/ph/static/array.js”. signin:1:1
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/rudderstack/sourceConfig/?p=cdn&v=1.33.0” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/identify” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/identify” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 17 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” 4 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/identify” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/identify” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 17 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” 2 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/identify” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/identify” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 17 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” 2 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/identify” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/identify” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 17 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” 3 signin
Error: injectNDVStore() was accessed without an active workflow document store. Derive the NDV store from injectWorkflowDocumentStore().value.documentId in contexts that can run without a loaded workflow.
    F_ ndv.store.ts:504
    _t reactivity.esm-bundler.js:391
    get value reactivity.esm-bundler.js:1701
    setup NodeView.vue:1785
    mr runtime-core.esm-bundler.js:199
    hr runtime-core.esm-bundler.js:206
    call runtime-core.esm-bundler.js:880
    d reactivity.esm-bundler.js:1820
    run reactivity.esm-bundler.js:237
    pn reactivity.esm-bundler.js:1921
    Br runtime-core.esm-bundler.js:908
    zr runtime-core.esm-bundler.js:841
    setup NodeView.vue:1784
    mr runtime-core.esm-bundler.js:199
    mo runtime-core.esm-bundler.js:8041
    po runtime-core.esm-bundler.js:8002
    A runtime-core.esm-bundler.js:5939
    k runtime-core.esm-bundler.js:5905
    h runtime-core.esm-bundler.js:5403
    s runtime-core.esm-bundler.js:6131
    run reactivity.esm-bundler.js:237
    runIfDirty reactivity.esm-bundler.js:275
    mr runtime-core.esm-bundler.js:199
    Tr runtime-core.esm-bundler.js:408
vue.runtime.esm-bundler-CK19_EKD.js:2:30623
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” 3 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/identify” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/identify” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 2 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 2 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 2 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 4 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/identify” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/identify” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 2 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 2 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 3 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 5 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 4 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/webhook-test/rR55c5eeONtyLGm9/fbdf6d9b5c9f4ab0977f7c71c0826f1a” signin
Chat API error: TypeError: NetworkError when attempting to fetch resource.
    Wn generic.ts:20
    Kn generic.ts:50
    Yn message.ts:49
    pr chat.ts:198
    s chat.ts:268
    G Input.vue:300
    mr runtime-core.esm-bundler.js:199
    hr runtime-core.esm-bundler.js:206
    n runtime-dom.esm-bundler.js:731
useExecutionDebugging-CJvOivOi.js:2:4816
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/identify” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/identify” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 2 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 3 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 3 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 2 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” 4 signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/track” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin
Blocked loading mixed active content “http://192.168.2.145:5678/rest/telemetry/proxy/v1/page” signin

Hammad_gaming:

That is what is weird: my workflows do show up when I restart N8N. I can access and run them.

I think that I am going to reinstall N8N on my machine from scratch. I will soon see if there is something screwed up about the data and the installation. I will let everyone know if doing so fixes this problem.

No need to do that.

If you don’t strictly need encryption for your local home lab setup:

  1. Go to your browser’s address bar.
  2. Manually change the URL from https://192.168.2.145:5678 to http://192.168.2.145:5678.
  3. The “Mixed Content” errors will disappear, and the Chat will work.

@factor3 Don’t uninstall it! firefox or your browser is blocking every request! If you don’t need https, open the editor over plain http and turn off firefox or the browser you use https only mode,

Everyone:

I did reinstall N8N from scratch (deleting the data and database and deleting the containers). As was predicted by kjooleng and achamm, it did not change anything.

I did, however, change the system so that it has stopped using https. In order to make it work without https, I had to add an environment variable:

N8N_SECURE_COOKIE=false

Once I restarted it, I downloaded the JSON file. It now works.

Thank everyone for your help in getting this working.

I do, however, have one other problem: I would like to offer this over the Internet to my team. This involves setting it up with Nginx Proxy Manager (NPM). I would like to offer it over HTTPS (for security reasons). Unfortunately, I cannot do so. I have created a domain for accessing NPM, but I cannot set it to use HTTPS because, of course, the chat (and perhaps other things) will not work.

Is there a way to get N8N to work with NPM and use HTTPS?

Hi @factor3

Glad you got it going. HTTPS behind NPM does work, you just have to tell n8n it’s behind a proxy and turn websockets on in NPM.

The NPM bit is the one people miss: on the proxy host, Details tab, tick Websockets Support. It’s off by default, and that’s usually what kills the chat and parts of the editor since both need a websocket back to n8n.

Then point everything at the domain instead of the LAN IP, and drop the N8N_SECURE_COOKIE=false you added, since the browser is talking https again:

N8N_HOST=n8n.yourdomain.com
N8N_PROTOCOL=https
N8N_EDITOR_BASE_URL=https://n8n.yourdomain.com
N8N_WEBHOOK_URL=https://n8n.yourdomain.com/
N8N_PROXY_HOPS=1
EXPRESS_TRUST_PROXY=true

NPM still forwards to n8n over plain http on 5678 internally and that’s fine, TLS stops at NPM.

One thing that’ll catch you later: NPM’s default read timeout is 60 seconds, so anything running longer than that comes back as a 504 from openresty rather than a result. If you hit it, add proxy_read_timeout in the Advanced tab of the proxy host.

Hammad_gaming:

Thanks for the info on the environment variables. I can now run N8N over SSL using my domain, and my simple AI test workflow works.

@factor3

Your welcome.