[GH-ISSUE #8984] Deepseek r1 : answer loading infinitively #15346

New Issue

GiteaMirror · 2026-04-19T21:35:08-05:00

GiteaMirror commented

2026-04-19 21:35:08 -05:00

Originally created by @BenDes21 on GitHub (Jan 27, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8984

Hi there, deepseek r1 is loading infinitively even after a restart of open web ui, I don't see any errors on the logs, what can be the solution ?

Originally created by @BenDes21 on GitHub (Jan 27, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/8984 <img width="934" alt="Image" src="https://github.com/user-attachments/assets/b8ae676b-88b0-40ce-8385-f55d66febcd0" /> <img width="934" alt="Image" src="https://github.com/user-attachments/assets/279545b0-7227-40f2-9846-8f4a0a277edb" /> Hi there, deepseek r1 is loading infinitively even after a restart of open web ui, I don't see any errors on the logs, what can be the solution ?

GiteaMirror closed this issue

2026-04-19 21:35:08 -05:00

GiteaMirror commented

2026-04-19 21:35:09 -05:00

@emimix commented on GitHub (Jan 27, 2025):

I'm getting the same issue (v0.5.7). It happens every time I try Deepseek R1...
@BenDes21 I see you closed the issue ...what is the fix?

@emimix commented on GitHub (Jan 27, 2025): I'm getting the same issue (v0.5.7). It happens every time I try Deepseek R1... @BenDes21 I see you closed the issue ...what is the fix?

GiteaMirror commented

2026-04-19 21:35:10 -05:00

@alexfisher commented on GitHub (Jan 27, 2025):

Same issue for me.

@alexfisher commented on GitHub (Jan 27, 2025): Same issue for me.

GiteaMirror commented

2026-04-19 21:35:10 -05:00

@kbranvh commented on GitHub (Jan 27, 2025):

same here latest 0.5.7

@kbranvh commented on GitHub (Jan 27, 2025): same here latest 0.5.7

GiteaMirror commented

2026-04-19 21:35:11 -05:00

@kbranvh commented on GitHub (Jan 27, 2025):

check this, seems to make sense....

https://github.com/open-webui/open-webui/discussions/9004

@kbranvh commented on GitHub (Jan 27, 2025): check this, seems to make sense.... https://github.com/open-webui/open-webui/discussions/9004

GiteaMirror commented

2026-04-19 21:35:11 -05:00

@emimix commented on GitHub (Jan 27, 2025):

check this, seems to make sense....

#9004

I checked that, and it’s not related to my issue.

@emimix commented on GitHub (Jan 27, 2025): > check this, seems to make sense.... > > [#9004](https://github.com/open-webui/open-webui/discussions/9004) I checked that, and it’s not related to my issue.

GiteaMirror commented

2026-04-19 21:35:12 -05:00

@Detrol commented on GitHub (Jan 28, 2025):

I think the reason might be the DDOS attack on them, or that they are also currently getting an enormous amount of attention/requests.

https://status.deepseek.com/

@Detrol commented on GitHub (Jan 28, 2025): I think the reason might be the DDOS attack on them, or that they are also currently getting an enormous amount of attention/requests. https://status.deepseek.com/

GiteaMirror commented

2026-04-19 21:35:13 -05:00

@rikhuijzer commented on GitHub (Feb 1, 2025):

@tjbck could you re-open this issue? I consistently have the same issue with WebUI 0.5.7 and DeepInfra's API. Occasionally DeepSeek R1 will complete, but 4 out of 5 times it will just hang. In the browser console, the error is "WebUI could not connect to Ollama". I have set max_tokens in the user interface to 80k, so that is not the problem. Answering hangs even while being well below that token limit. This is my configuration:

services:
  open-webui:
    container_name: 'open-webui'
    image: 'ghcr.io/open-webui/open-webui:main'
    volumes:
      - './open-webui:/app/backend/data:rw'
    ports:
      - '3003:8080'
    environment:
      ENABLE_SIGNUP: 'False'
      OPENAI_API_BASE_URLS: 'https://api.deepinfra.com/v1/openai'
    env_file:
      - 'OPENAI_API_KEYS.env'
      - 'WEBUI_SECRET_KEY.env'
    logging:
      driver: 'json-file'
      options:
        max-size: '10m'
        max-file: '10'
    extra_hosts:
      - 'host.docker.internal:host-gateway'
    restart: 'unless-stopped'

@rikhuijzer commented on GitHub (Feb 1, 2025): @tjbck could you re-open this issue? I consistently have the same issue with WebUI 0.5.7 and DeepInfra's API. Occasionally DeepSeek R1 will complete, but 4 out of 5 times it will just hang. In the browser console, the error is "WebUI could not connect to Ollama". I have set `max_tokens` in the user interface to 80k, so that is not the problem. Answering hangs even while being well below that token limit. This is my configuration: ```yml services: open-webui: container_name: 'open-webui' image: 'ghcr.io/open-webui/open-webui:main' volumes: - './open-webui:/app/backend/data:rw' ports: - '3003:8080' environment: ENABLE_SIGNUP: 'False' OPENAI_API_BASE_URLS: 'https://api.deepinfra.com/v1/openai' env_file: - 'OPENAI_API_KEYS.env' - 'WEBUI_SECRET_KEY.env' logging: driver: 'json-file' options: max-size: '10m' max-file: '10' extra_hosts: - 'host.docker.internal:host-gateway' restart: 'unless-stopped' ```

GiteaMirror referenced this issue

2026-04-19 23:19:07 -05:00

[GH-ISSUE #15346] issue: Error parsing tool call arguments #17538

GiteaMirror referenced this issue

2026-04-20 06:33:46 -05:00

[PR #22189] [CLOSED] fix: initialize streaming tool call arguments to '{}' instead of empty string #26541

GiteaMirror referenced this issue

2026-04-25 06:55:44 -05:00

[GH-ISSUE #15346] issue: Error parsing tool call arguments #33067

GiteaMirror referenced this issue

2026-04-25 14:08:52 -05:00

[PR #22189] [CLOSED] fix: initialize streaming tool call arguments to '{}' instead of empty string #42171