n8n - 💡(How to fix) Fix Openweb-UI no longer working as AI provider [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#30693Fetched 2026-05-20 03:59:17
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×3commented ×1mentioned ×1subscribed ×1

Error Message

2026-05-19 08:24:10.615 | ERROR | open_webui.main:process_chat:2013 - Error processing chat payload: 'NoneType' object has no attribute 'startswith'

  • error: all

Code Example

Bad request - please check your parameters
400 status code (no body)

---

2026-05-19 08:24:10.615 | ERROR    | open_webui.main:process_chat:2013 - Error processing chat payload: 'NoneType' object has no attribute 'startswith'
2026-05-19 08:24:10.615 | INFO     | uvicorn.protocols.http.httptools_impl:send:483 - 10.0.22.70:0 - "POST /api/chat/completions HTTP/1.0" 400
RAW_BUFFERClick to expand / collapse

Bug Description

Openweb-UI is set up as OpenAI compatible AI provider. According to n8n UI I get following

Bad request - please check your parameters
400 status code (no body)

From Openweb-UIs Docker log I get

2026-05-19 08:24:10.615 | ERROR    | open_webui.main:process_chat:2013 - Error processing chat payload: 'NoneType' object has no attribute 'startswith'
2026-05-19 08:24:10.615 | INFO     | uvicorn.protocols.http.httptools_impl:send:483 - 10.0.22.70:0 - "POST /api/chat/completions HTTP/1.0" 400

To Reproduce

  1. Use AI node
  2. Setup OpenAI chat model which uses Openweb-UI instance

Expected behavior

AI should work as in previous versions

Debug Info

Debug info

core

  • n8nVersion: 2.21.3
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: postgres
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: bc0a4d0a-3641-4529-ac0f-b8730f9e7091

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64; rv:150.0) gecko/20100101 firefox/150.0
  • isTouchDevice: false

cluster

  • instanceCount: 1
  • versions: 2.21.3
  • instances:
    • instanceKey: 60c61951-e246-4952-8859-76db647d8c76, hostId: main-77bddcaaae4f, instanceType: main, instanceRole: leader, version: 2.21.3
  • checks:
    • check: hostid-clash, status: succeeded, warnings: -
    • check: lifecycle, status: succeeded, warnings: -
    • check: split-brain, status: succeeded, warnings: -
    • check: version-mismatch, status: succeeded, warnings: -

Generated at: 2026-05-19T08:25:21.637Z

Operating System

Ubuntu 24.04.4 LTS

n8n Version

2.21.3

Node.js Version

24.14.1

Database

PostgreSQL

Execution mode

main (default)

Hosting

self hosted

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

AI should work as in previous versions

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING