-
DescriptionAfter I entered the URL provided by lmstudio in DBeaver's AI settings and clicked 'Test Connection', it just keeps sending request. But actually, if I try navigate to 'http://127.0.0.1:1234/v1/models' directly in Edge, Edge can display the model list results. I tried changing the port number and turning off the firewall, but it still doesn't work.
DBeaver Version25.2.4 Operating Systemwin11 Database and driverNo response Steps to reproduceNo response Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 14 comments
-
|
Hello @632575987, Try replacing |
Beta Was this translation helpful? Give feedback.
-
I've already tried using localhost, but it doesn't work either. |
Beta Was this translation helpful? Give feedback.
-
|
There may be something useful in the logs. Can you please provide them? You can find instructions here: https://github.com/dbeaver/dbeaver/wiki/Log-files |
Beta Was this translation helpful? Give feedback.
-
|
I've just encountered same issue, but no logs appear on that part/section:
Basically, the process just stuck there, LM Studio is running fine and callable from the browser, but not from Dbeaver.
|
Beta Was this translation helpful? Give feedback.
-
|
@darrylsepeda don't use the error log view. Instead, collect and send us the log files mentioned in the linked article. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ShadelessFox , Apologize for slow response.
you could ignore the empty API token at the beginning, InterruptedException because its already stuck on loading window for a long time so I ended up canceling the loading window. |
Beta Was this translation helpful? Give feedback.
-
|
Hello All I have the same issue. This is my test, hoping it could be helpful for troubleshooting. here is my logs: I guess it might be that DBeaver’s request method is incompatible with LM Studio. |
Beta Was this translation helpful? Give feedback.
-
|
Can you turn on this option to see if it has any effect? It's available since 25.2.5.
|
Beta Was this translation helpful? Give feedback.
-
|
Is same issue when selected "Use legacy API"
|
Beta Was this translation helpful? Give feedback.
-
|
LM Studio does not handle HTTP/2 requests well. lmstudio-ai/lmstudio-bug-tracker#1079 |
Beta Was this translation helpful? Give feedback.
-
|
Have you tried jan? https://github.com/janhq/jan/ it seems to have the same functionality as LM Studio but with HTTP/2 support |
Beta Was this translation helpful? Give feedback.
-
|
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 published the script here: Just run it locally and point DBeaver's API URL to the proxy's port (e.g., http://127.0.0.1:8080/v1). Hope it helps someone! |
Beta Was this translation helpful? Give feedback.
-
thanks ! so much. |
Beta Was this translation helpful? Give feedback.
-
|
Is it still reproducible in the latest DBeaver version? |
Beta Was this translation helpful? Give feedback.







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…