Skip to content
Discussion options

You must be logged in to vote

Hi everyone,

I was running into this exact same issue and wrote a lightweight Python reverse proxy to act as a bridge between DBeaver and LM Studio.

The root of the problem seems to be how DBeaver's strict HTTP client handles the streaming responses and headers from LM Studio. The proxy fixes this by intercepting the traffic, forcing "stream": false in the JSON body, stripping problematic chunked/encoding headers, and explicitly injecting the exact Content-Length so DBeaver knows exactly when the response ends (which prevents the infinite connection hang). It also prevents the ECONNRESET spam on LM Studio's side.

If anyone needs a quick workaround while this isn't officially fixed, I publ…

Replies: 14 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by E1izabeth
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
9 participants
Converted from issue

This discussion was converted from issue #39606 on June 04, 2026 15:00.