"NotebookLM by Dify" Podcast Generator giving error "Expecting value: line 1 column 1 (char 0)" #152

New Issue

Closed

opened 2026-02-16 10:18:15 -05:00 by yindo · 9 comments

yindo commented 2026-02-16 10:18:15 -05:00

Owner

Copy Link

Copy Source

Originally created by @tylerdurden4285 on GitHub (Mar 30, 2025).

Self Checks

• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1. Installed dify with docker and setup the .env urls to point to the local IP
2. Setup and tested models (all working fine using gemini, anthropic, openai)
3. Created "NotebookLM for Dify" workflow from provided template
4. Workflow failed with error "

✔️ Expected Behavior

The "NotebookLM for Dify" workflow's Podcast Generator plugin should take input text and provide output audio podcast file that is audio to listen to the podcast.

❌ Actual Behavior

it seems to process the input text for a while, then fails with no output audio file at all. It just shows in output " { } " and the error code received for this Podcast Generator is:

"Expecting value: line 1 column 1 (char 0)"

For added insight I also see this in docker-compose debug logs:

api-1 |
api-1 | [on_tool_execution]
api-1 | Tool: podcast_audio_generator
api-1 | Outputs: {"type":"text","message":{"text":"Audio generated successfully"},"meta":null}
api-1 |
api-1 | 2025-03-30 14:21:37.517 ERROR [Thread-141 (_generate_worker)] [graph_engine.py:842] - Node Podcast audio generator run failed
api-1 | Traceback (most recent call last):
api-1 | File "/app/api/core/workflow/graph_engine/graph_engine.py", line 645, in _run_node
api-1 | for item in generator:
api-1 | ^^^^^^^^^
api-1 | File "/app/api/core/workflow/nodes/base/node.py", line 84, in run
api-1 | yield from result
api-1 | File "/app/api/core/workflow/nodes/tool/tool_node.py", line 122, in _run
api-1 | yield from self._transform_message(message_stream, tool_info, parameters_for_log)
api-1 | File "/app/api/core/workflow/nodes/tool/tool_node.py", line 208, in _transform_message
api-1 | for message in message_stream:
api-1 | ^^^^^^^^^^^^^^
api-1 | File "/app/api/core/tools/utils/message_transformer.py", line 25, in transform_tool_invoke_messages
api-1 | for message in messages:
api-1 | ^^^^^^^^
api-1 | File "/app/api/core/callback_handler/workflow_tool_callback_handler.py", line 21, in on_tool_execution
api-1 | for tool_output in tool_outputs:
api-1 | ^^^^^^^^^^^^
api-1 | File "/app/api/core/tools/plugin_tool/tool.py", line 41, in _invoke
api-1 | yield from manager.invoke(
api-1 | File "/app/api/core/plugin/manager/base.py", line 189, in _request_with_plugin_daemon_response_stream
api-1 | self._handle_plugin_daemon_error(error.error_type, error.message)
api-1 | File "/app/api/core/plugin/manager/base.py", line 204, in _handle_plugin_daemon_error
api-1 | error_object = json.loads(message)
api-1 | ^^^^^^^^^^^^^^^^^^^
api-1 | File "/usr/local/lib/python3.12/json/__init__.py", line 346, in loads
api-1 | return _default_decoder.decode(s)
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/usr/local/lib/python3.12/json/decoder.py", line 338, in decode
api-1 | obj, end = self.raw_decode(s, idx=_w(s, 0).end())
api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1 | File "/usr/local/lib/python3.12/json/decoder.py", line 356, in raw_decode
api-1 | raise JSONDecodeError("Expecting value", s, err.value) from None
api-1 | json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
api-1 | 2025-03-30 14:21:37.557 DEBUG [Dummy-142] [based_generate_task_pipeline.py:45] - error: Run failed: Expecting value: line 1 column 1 (char 0)

Originally created by @tylerdurden4285 on GitHub (Mar 30, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.1.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. Installed dify with docker and setup the .env urls to point to the local IP 2. Setup and tested models (all working fine using gemini, anthropic, openai) 3. Created "NotebookLM for Dify" workflow from provided template 4. Workflow failed with error " ### ✔️ Expected Behavior The "NotebookLM for Dify" workflow's Podcast Generator plugin should take input text and provide output audio podcast file that is audio to listen to the podcast. ### ❌ Actual Behavior it seems to process the input text for a while, then fails with no output audio file at all. It just shows in output " { } " and the error code received for this Podcast Generator is: > "Expecting value: line 1 column 1 (char 0)" For added insight I also see this in docker-compose debug logs: > api-1 | > api-1 | [on_tool_execution] > api-1 | Tool: podcast_audio_generator > api-1 | Outputs: {"type":"text","message":{"text":"Audio generated successfully"},"meta":null} > api-1 | > api-1 | 2025-03-30 14:21:37.517 ERROR [Thread-141 (_generate_worker)] [graph_engine.py:842] - Node Podcast audio generator run failed > api-1 | Traceback (most recent call last): > api-1 | File "/app/api/core/workflow/graph_engine/graph_engine.py", line 645, in _run_node > api-1 | for item in generator: > api-1 | ^^^^^^^^^ > api-1 | File "/app/api/core/workflow/nodes/base/node.py", line 84, in run > api-1 | yield from result > api-1 | File "/app/api/core/workflow/nodes/tool/tool_node.py", line 122, in _run > api-1 | yield from self._transform_message(message_stream, tool_info, parameters_for_log) > api-1 | File "/app/api/core/workflow/nodes/tool/tool_node.py", line 208, in _transform_message > api-1 | for message in message_stream: > api-1 | ^^^^^^^^^^^^^^ > api-1 | File "/app/api/core/tools/utils/message_transformer.py", line 25, in transform_tool_invoke_messages > api-1 | for message in messages: > api-1 | ^^^^^^^^ > api-1 | File "/app/api/core/callback_handler/workflow_tool_callback_handler.py", line 21, in on_tool_execution > api-1 | for tool_output in tool_outputs: > api-1 | ^^^^^^^^^^^^ > api-1 | File "/app/api/core/tools/plugin_tool/tool.py", line 41, in _invoke > api-1 | yield from manager.invoke( > api-1 | File "/app/api/core/plugin/manager/base.py", line 189, in _request_with_plugin_daemon_response_stream > api-1 | self._handle_plugin_daemon_error(error.error_type, error.message) > api-1 | File "/app/api/core/plugin/manager/base.py", line 204, in _handle_plugin_daemon_error > api-1 | error_object = json.loads(message) > api-1 | ^^^^^^^^^^^^^^^^^^^ > api-1 | File "/usr/local/lib/python3.12/json/__init__.py", line 346, in loads > api-1 | return _default_decoder.decode(s) > api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^ > api-1 | File "/usr/local/lib/python3.12/json/decoder.py", line 338, in decode > api-1 | obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > api-1 | File "/usr/local/lib/python3.12/json/decoder.py", line 356, in raw_decode > api-1 | raise JSONDecodeError("Expecting value", s, err.value) from None > api-1 | json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) > api-1 | 2025-03-30 14:21:37.557 DEBUG [Dummy-142] [based_generate_task_pipeline.py:45] - error: Run failed: Expecting value: line 1 column 1 (char 0)

yindo closed this issue 2026-02-16 10:18:15 -05:00

yindo commented 2026-02-16 10:18:15 -05:00

Author

Owner

Copy Link

Copy Source

@dosubot[bot] commented on GitHub (Mar 30, 2025):

To resolve the "Expecting value: line 1 column 1 (char 0)" error in the "NotebookLM by Dify" Podcast Generator, you should set the NO_PROXY environment variable with the following values: weaviate,qdrand,db,redis,web,worker,plugin_daemon. Additionally, ensure that the HTTPS_PROXY and ALL_PROXY settings are correctly configured, especially if you have Docker global proxy configurations. This setup is necessary when HTTP_PROXY is configured in your Docker environment to ensure proper communication between Dify's internal services ^[1][2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

@dosubot[bot] commented on GitHub (Mar 30, 2025): <!-- Answer --> To resolve the "Expecting value: line 1 column 1 (char 0)" error in the "NotebookLM by Dify" Podcast Generator, you should set the `NO_PROXY` environment variable with the following values: `weaviate,qdrand,db,redis,web,worker,plugin_daemon`. Additionally, ensure that the `HTTPS_PROXY` and `ALL_PROXY` settings are correctly configured, especially if you have Docker global proxy configurations. This setup is necessary when `HTTP_PROXY` is configured in your Docker environment to ensure proper communication between Dify's internal services ^{[[1]](https://github.com/langgenius/dify/issues/14822)}^{[[2]](https://github.com/langgenius/dify/issues/14608)}. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- ^{Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/66ad2668-b06b-4a7c-b7ef-1071196f7389?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/66ad2668-b06b-4a7c-b7ef-1071196f7389?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/66ad2668-b06b-4a7c-b7ef-1071196f7389?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/66ad2668-b06b-4a7c-b7ef-1071196f7389?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/66ad2668-b06b-4a7c-b7ef-1071196f7389?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/66ad2668-b06b-4a7c-b7ef-1071196f7389?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/66ad2668-b06b-4a7c-b7ef-1071196f7389?feedback_type=other)}

yindo commented 2026-02-16 10:18:15 -05:00

Author

Owner

Copy Link

Copy Source

@tylerdurden4285 commented on GitHub (Mar 30, 2025):

It seems this user had a similar issue with firecrawl but no solution was provided: https://github.com/langgenius/dify/discussions/8604

@tylerdurden4285 commented on GitHub (Mar 30, 2025): It seems this user had a similar issue with firecrawl but no solution was provided: https://github.com/langgenius/dify/discussions/8604

yindo commented 2026-02-16 10:18:15 -05:00

Author

Owner

Copy Link

Copy Source

@tylerdurden4285 commented on GitHub (Mar 30, 2025):

@dosu this didn't help. Problem persists.

@tylerdurden4285 commented on GitHub (Mar 30, 2025): @dosu this didn't help. Problem persists.

yindo commented 2026-02-16 10:18:15 -05:00

Author

Owner

Copy Link

Copy Source

@dosubot[bot] commented on GitHub (Mar 30, 2025):

To address the "Expecting value: line 1 column 1 (char 0)" error in the Podcast Generator, please ensure the following:

1. TTS Service Configuration: Verify that you have selected a valid TTS service, such as OpenAI TTS, and that the API key is correctly entered and valid. Also, ensure the OpenAI base URL is correctly configured if applicable ^[1].

2. Network Settings: Check your network settings to ensure there are no connectivity issues with the TTS service. This includes verifying that the NO_PROXY, HTTPS_PROXY, and ALL_PROXY settings are correctly configured, especially if you have Docker global proxy configurations.

3. Logs Review: Review the logs for any additional error messages that might provide more insight into the issue.

Unfortunately, I couldn't find any similar threads that might offer additional solutions. If the problem persists, consider reaching out to the community for further assistance or checking for updates in the project's repository.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

@dosubot[bot] commented on GitHub (Mar 30, 2025): <!-- Answer --> To address the "Expecting value: line 1 column 1 (char 0)" error in the Podcast Generator, please ensure the following: 1. **TTS Service Configuration**: Verify that you have selected a valid TTS service, such as OpenAI TTS, and that the API key is correctly entered and valid. Also, ensure the OpenAI base URL is correctly configured if applicable ^{[[1]](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/builtin/podcast_generator/podcast_generator.yaml)}. 2. **Network Settings**: Check your network settings to ensure there are no connectivity issues with the TTS service. This includes verifying that the `NO_PROXY`, `HTTPS_PROXY`, and `ALL_PROXY` settings are correctly configured, especially if you have Docker global proxy configurations. 3. **Logs Review**: Review the logs for any additional error messages that might provide more insight into the issue. Unfortunately, I couldn't find any similar threads that might offer additional solutions. If the problem persists, consider reaching out to the community for further assistance or checking for updates in the project's repository. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- ^{Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/f24410c4-49e8-4b4b-9860-ded1158c984f?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/f24410c4-49e8-4b4b-9860-ded1158c984f?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/f24410c4-49e8-4b4b-9860-ded1158c984f?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/f24410c4-49e8-4b4b-9860-ded1158c984f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f24410c4-49e8-4b4b-9860-ded1158c984f?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/f24410c4-49e8-4b4b-9860-ded1158c984f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f24410c4-49e8-4b4b-9860-ded1158c984f?feedback_type=other)}

yindo commented 2026-02-16 10:18:15 -05:00

Author

Owner

Copy Link

Copy Source

@tylerdurden4285 commented on GitHub (Mar 30, 2025):

I experimented and signed up to the cloud version of Dify (not self hosted at all) and the issue also happens to cloud version so it seems like a deeper issue with the Podcast Generator. Here's a screenshot from the cloud dify doing same thing so it seems to happen everywhere on all Dify versions:

@tylerdurden4285 commented on GitHub (Mar 30, 2025): I experimented and signed up to the cloud version of Dify (not self hosted at all) and the issue also happens to cloud version so it seems like a deeper issue with the Podcast Generator. Here's a screenshot from the cloud dify doing same thing so it seems to happen everywhere on all Dify versions: 

yindo commented 2026-02-16 10:18:15 -05:00

Author

Owner

Copy Link

Copy Source

@LYMingML commented on GitHub (Apr 10, 2025):

To address the "Expecting value: line 1 column 1 (char 0)" error in the Podcast Generator, please ensure the following:

1. TTS Service Configuration: Verify that you have selected a valid TTS service, such as OpenAI TTS, and that the API key is correctly entered and valid. Also, ensure the OpenAI base URL is correctly configured if applicable [1].
2. Network Settings: Check your network settings to ensure there are no connectivity issues with the TTS service. This includes verifying that the NO_PROXY, HTTPS_PROXY, and ALL_PROXY settings are correctly configured, especially if you have Docker global proxy configurations.
3. Logs Review: Review the logs for any additional error messages that might provide more insight into the issue.

Unfortunately, I couldn't find any similar threads that might offer additional solutions. If the problem persists, consider reaching out to the community for further assistance or checking for updates in the project's repository.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

Thank you for pointing that out! Could you please clarify how to properly configure the NO_PROXY, HTTPS_PROXY, and ALL_PROXY settings for Docker containers or Docker Compose? Specifically:

Should NO_PROXY, HTTPS_PROXY, and ALL_PROXY be configured in the .env file, directly in the docker-compose.yaml under environment:, or elsewhere (e.g., Docker daemon settings)?

If using a mix of global and per-service proxies, how do we prioritize them?

For Docker-internal services (e.g., db, api), what values should NO_PROXY include to bypass the proxy? (e.g., *.internal,172.19.0.0/16,localhost?)

@LYMingML commented on GitHub (Apr 10, 2025): > To address the "Expecting value: line 1 column 1 (char 0)" error in the Podcast Generator, please ensure the following: > > 1. **TTS Service Configuration**: Verify that you have selected a valid TTS service, such as OpenAI TTS, and that the API key is correctly entered and valid. Also, ensure the OpenAI base URL is correctly configured if applicable [[1]](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/builtin/podcast_generator/podcast_generator.yaml). > 2. **Network Settings**: Check your network settings to ensure there are no connectivity issues with the TTS service. This includes verifying that the `NO_PROXY`, `HTTPS_PROXY`, and `ALL_PROXY` settings are correctly configured, especially if you have Docker global proxy configurations. > 3. **Logs Review**: Review the logs for any additional error messages that might provide more insight into the issue. > > Unfortunately, I couldn't find any similar threads that might offer additional solutions. If the problem persists, consider reaching out to the community for further assistance or checking for updates in the project's repository. > > _To continue talking to [Dosu](https://dosu.dev), mention [@dosu](https://github.com/dosu)._ > > Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/f24410c4-49e8-4b4b-9860-ded1158c984f?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/f24410c4-49e8-4b4b-9860-ded1158c984f?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/f24410c4-49e8-4b4b-9860-ded1158c984f?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/f24410c4-49e8-4b4b-9860-ded1158c984f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f24410c4-49e8-4b4b-9860-ded1158c984f?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/f24410c4-49e8-4b4b-9860-ded1158c984f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f24410c4-49e8-4b4b-9860-ded1158c984f?feedback_type=other) Thank you for pointing that out! Could you please clarify how to properly configure the NO_PROXY, HTTPS_PROXY, and ALL_PROXY settings for Docker containers or Docker Compose? Specifically: Should NO_PROXY, HTTPS_PROXY, and ALL_PROXY be configured in the .env file, directly in the docker-compose.yaml under environment:, or elsewhere (e.g., Docker daemon settings)? If using a mix of global and per-service proxies, how do we prioritize them? For Docker-internal services (e.g., db, api), what values should NO_PROXY include to bypass the proxy? (e.g., *.internal,172.19.0.0/16,localhost?)

yindo commented 2026-02-16 10:18:15 -05:00

Author

Owner

Copy Link

Copy Source

@dosubot[bot] commented on GitHub (Aug 24, 2025):

Hi, @tylerdurden4285. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

• You reported a JSON parsing error with the "NotebookLM for Dify" Podcast Generator plugin on both self-hosted Docker and cloud versions of Dify 1.1.3.
• Despite logs indicating success, no audio output is produced.
• I suggested configuring NO_PROXY, HTTPS_PROXY, and ALL_PROXY environment variables to fix internal service communication, but the issue persists.
• There is ongoing uncertainty about the correct proxy setup in Docker environments, as noted by another user.
• The problem seems to affect all Dify versions with no confirmed resolution yet.

Next Steps:

• Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here.
• If I don’t hear back within 5 days, this issue will be automatically closed.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 24, 2025): Hi, @tylerdurden4285. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a JSON parsing error with the "NotebookLM for Dify" Podcast Generator plugin on both self-hosted Docker and cloud versions of Dify 1.1.3. - Despite logs indicating success, no audio output is produced. - I suggested configuring NO_PROXY, HTTPS_PROXY, and ALL_PROXY environment variables to fix internal service communication, but the issue persists. - There is ongoing uncertainty about the correct proxy setup in Docker environments, as noted by another user. - The problem seems to affect all Dify versions with no confirmed resolution yet. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here. - If I don’t hear back within 5 days, this issue will be automatically closed. Thank you for your understanding and contribution!

yindo commented 2026-02-16 10:18:15 -05:00

Author

Owner

Copy Link

Copy Source

@tylerdurden4285 commented on GitHub (Aug 24, 2025):

My apologies. This matter is closed.

@tylerdurden4285 commented on GitHub (Aug 24, 2025): My apologies. This matter is closed.

yindo commented 2026-02-16 10:18:15 -05:00

Author

Owner

Copy Link

Copy Source

@dosubot[bot] commented on GitHub (Sep 9, 2025):

Hi, @tylerdurden4285. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

• You reported that the "NotebookLM for Dify" Podcast Generator plugin fails to produce audio, showing a JSON parsing error despite logs indicating success.
• The problem affected both self-hosted Docker and cloud versions of Dify 1.1.3.
• I suggested configuring NO_PROXY, HTTPS_PROXY, and ALL_PROXY environment variables to fix internal service communication, but the issue persisted.
• Another user requested clarification on proper proxy configuration in Docker environments.
• You later closed the issue, implying no further action was taken or the problem was considered resolved by stopping attempts.

Next Steps:

• Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here to keep the discussion open.
• Otherwise, this issue will be automatically closed in 5 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Sep 9, 2025): Hi, @tylerdurden4285. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that the "NotebookLM for Dify" Podcast Generator plugin fails to produce audio, showing a JSON parsing error despite logs indicating success. - The problem affected both self-hosted Docker and cloud versions of Dify 1.1.3. - I suggested configuring NO_PROXY, HTTPS_PROXY, and ALL_PROXY environment variables to fix internal service communication, but the issue persisted. - Another user requested clarification on proper proxy configuration in Docker environments. - You later closed the issue, implying no further action was taken or the problem was considered resolved by stopping attempts. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here to keep the discussion open. - Otherwise, this issue will be automatically closed in 5 days. Thank you for your understanding and contribution!

yindo referenced this issue 2026-02-16 10:22:02 -05:00

[PR #152] [MERGED] bump: ollama to 0.0.3 #1129

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

dependabot/uv/datasources/google_cloud_storage/uv-0225d4cafc

dependabot/uv/tools/chart/uv-cdf8d38825

feat/moonshot-kimi-k3-k27-code

feat/gemini-system-instruction-semantics

fix/gemini-text-system-parts

dosu/doc-update-3436

feat/openai-gpt-5-6-support

fix/outlook-trigger-readme-permissions

fix/microsoft-oauth-datasource-tenant

fix/byteplus-api-base-url-label

feat/ark-video-generation-custom-models

fix/openai-stream-reasoning-thinking

fix/skip-live-tests-missing-keys

codex/enhance-discord-integrations

codex/harden-trigger-oauth-permissions

update-lemonade-default-port

codex/fix-pr-review-ci

feat/ark-multimodal-polling

copilot/update-mineru-3x-plugin-file-types

feat/action-security-fix

feat/claude-fable5

codex/fix-ollama-model-category

codex/upgrade-ollama-latest

feat/minimax-m3

codex/refine-plugin-readmes

fix/fireworks-model-label-zh-hans

chore/version-bump-plugins-batch-06

chore/version-bump-plugins-batch-05

chore/version-bump-plugins-batch-04

chore/version-bump-plugins-batch-03

chore/version-bump-plugins-batch-02

fix/plugin-sdk-i18n-fields

chore/version-bump-plugins-batch-01

chore/dependencies-high-priority

chore/dependencies-medium-priority

chore/dependencies-low-priority-clean

chore/dependencies-low-priority

fix/tongyi-align-deepseek-model-metadata

codex/update-openrouter-models

codex/azure-ai-studio-cjk-version-bump

feat/ernie-image-tool

claude/cranky-thompson-b6a281

fix/remove-unavailable-volcengine-models

fix/legacy-plugin-daemon-compatibility

copilot/add-deepseek-v4-to-openrouter

codex/merge-tongyi-tts-prs

codex/depot-runners

chore/migrate-selected-plugins-to-uv-lock

fix/repair-failed-plugin-deploys

ci/fix-plugin-change-detection

chore/migrate-aws-s3-storage-to-uv-lock

chore/migrate-somark-dependencies-to-uv-lock

ci/uv-lock-dependency-validation

fix/2911-openai-api-compatible-tool-call-content

chore/remove-deprecated-plugins

copilot/add-more-models-openrouter-provider

copilot/fix-error-connecting-fireworks-ai

fix/openai-compatible-max-completion-tokens-validation

fix/gemini-lockfile

chore/add-React-fallback-desc

feat/add-gemini-embedding-2-preview

copilot/add-claude-sonnet-opus-4-6

codex/update-xai-models-2721

fix/remove-sentence-transformer-for-hubspot

feat/add-gpt-5.4

copilot/fix-ci-errors-and-bump-version

copilot/fix-security-errors-combined

copilot/update-gemini-model-version

fix/anthropic-parallel-tool-call

codex/fix-azure-ai-studio-azure-core-1-38

codex/fix-azure-blob-azure-core-1-38

codex/fix-azure-openai-azure-core-1-38

gitlab-credentials-c

fix/openrouter-validation-model

fix/gemini-null-checks

fix/deepseek-tool-message-ignore

fix/gemini-dependencies

No results found.

Labels

Clear labels

bug

bug

bug

dependencies

documentation

enhancement

good first issue

invalid

pull-request

Mirrored from GitHub Pull Request

question

stale

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

yindo

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#152