langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 12:36:14 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Using the online langfuse Application error #16453

New Issue
Closed
opened 2026-02-21 19:26:09 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 19:26:09 -05:00
Owner
Copy Link
Copy Source

Originally created by @hippo730 on GitHub (Aug 26, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

Version 1.0.1

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

Image Image

✔️ Expected Behavior

Using the online langfuse Application suessfull

❌ Actual Behavior

No response

Originally created by @hippo730 on GitHub (Aug 26, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version Version 1.0.1 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce <img width="1485" height="366" alt="Image" src="https://github.com/user-attachments/assets/207ffde0-def1-438b-9d3f-92faf5697194" /> <img width="843" height="606" alt="Image" src="https://github.com/user-attachments/assets/9c4bedd0-16fb-49ba-b429-12efcb172502" /> ### ✔️ Expected Behavior Using the online langfuse Application suessfull ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:26:09 -05:00
yindo closed this issue 2026-02-21 19:26:09 -05:00
yindo commented 2026-02-21 19:26:09 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi @hippo730! I'm Dosu and I’m helping the dify team.

This error is common in Dify v1.0.1 when integrating Langfuse, especially in self-hosted setups. The most frequent causes are misconfigured URLs (missing http:// or https://), network/proxy issues, or outdated code that mishandles the Langfuse host URL. If your Langfuse host URL includes a path (like /api/v1), Dify v1.0.1 may strip it, causing backend validation to fail and the frontend to show a generic application error or React error #130. This affects both cloud and local Langfuse deployments and usually results in a 400/500 error in the browser console or backend logs1 2 3 .

Troubleshooting steps:

  1. Double-check your Langfuse host URL in the config—make sure it includes the full protocol and path (e.g., https://api.langfuse.com or your custom endpoint).
  2. Only set public_key, secret_key, and host in the Langfuse config—extra fields like project_key will break validation4 .
  3. If running in Docker, use host.docker.internal instead of localhost for service URLs to avoid container networking issues5 .
  4. Make sure your .env.local file is present in the web folder, run cp .env.example .env in the Docker folder, and restart containers with docker compose stop && docker compose up -d6 .
  5. Check your CSP and CORS settings in .env—all necessary domains should be whitelisted.
  6. If you see a React error #130 or a 500 error in the browser console, check backend logs for ValueError or authentication errors around the time of the failure.

Most effective fix: Upgrade to Dify v1.4.1 or later. Many Langfuse integration bugs (including host URL handling and error masking) were fixed in newer releases7 8 9 .

If you still see the error after these steps, please share the exact error message or stack trace from your frontend console and backend logs for more targeted help.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Aug 26, 2025): <!-- Greeting --> Hi @hippo730! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This error is common in Dify v1.0.1 when integrating Langfuse, especially in self-hosted setups. The most frequent causes are misconfigured URLs (missing `http://` or `https://`), network/proxy issues, or outdated code that mishandles the Langfuse host URL. If your Langfuse host URL includes a path (like `/api/v1`), Dify v1.0.1 may strip it, causing backend validation to fail and the frontend to show a generic application error or React error #130. This affects both cloud and local Langfuse deployments and usually results in a 400/500 error in the browser console or backend logs[^1][^2][^3]. **Troubleshooting steps:** 1. Double-check your Langfuse host URL in the config—make sure it includes the full protocol and path (e.g., `https://api.langfuse.com` or your custom endpoint). 2. Only set `public_key`, `secret_key`, and `host` in the Langfuse config—extra fields like `project_key` will break validation[^4]. 3. If running in Docker, use `host.docker.internal` instead of `localhost` for service URLs to avoid container networking issues[^5]. 4. Make sure your `.env.local` file is present in the web folder, run `cp .env.example .env` in the Docker folder, and restart containers with `docker compose stop && docker compose up -d`[^6]. 5. Check your CSP and CORS settings in `.env`—all necessary domains should be whitelisted. 6. If you see a React error #130 or a 500 error in the browser console, check backend logs for `ValueError` or authentication errors around the time of the failure. **Most effective fix:** Upgrade to Dify v1.4.1 or later. Many Langfuse integration bugs (including host URL handling and error masking) were fixed in newer releases[^7][^8][^9]. If you still see the error after these steps, please share the exact error message or stack trace from your frontend console and backend logs for more targeted help. [^1]: [Dify issue #15695: React error #130 and 500 Internal Server Error after Langfuse config](https://github.com/langgenius/dify/issues/15695) [^2]: [Dify issue #19867: 400 Bad Request/Invalid Credentials with Langfuse](https://github.com/langgenius/dify/issues/19867) [^3]: [Dify PR #22766: Fix Langfuse host URL path handling](https://github.com/langgenius/dify/pull/22766) [^4]: [Dify issue #21450: Unexpected config fields break Langfuse integration](https://github.com/langgenius/dify/issues/21450) [^5]: [Dify issue #12691: Docker networking and Langfuse service URL](https://github.com/langgenius/dify/issues/12691) [^6]: [Dify issue #15695: Environment setup steps for server errors](https://github.com/langgenius/dify/issues/15695) [^7]: [Dify issue #19867: Upgrading to v1.4.1 resolves Langfuse errors](https://github.com/langgenius/dify/issues/19867) [^8]: [Dify issue #21450: Langfuse integration fixed in v1.4.3](https://github.com/langgenius/dify/issues/21450) [^9]: [Dify PR #22766: Host URL validation bug fix](https://github.com/langgenius/dify/pull/22766) <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/18d3078e-a9ae-485f-9ad5-fce89c1614bf?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/18d3078e-a9ae-485f-9ad5-fce89c1614bf?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/18d3078e-a9ae-485f-9ad5-fce89c1614bf?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/18d3078e-a9ae-485f-9ad5-fce89c1614bf?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/18d3078e-a9ae-485f-9ad5-fce89c1614bf?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/18d3078e-a9ae-485f-9ad5-fce89c1614bf?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/18d3078e-a9ae-485f-9ad5-fce89c1614bf?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/24562)
yindo commented 2026-02-21 19:26:09 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 26, 2025):

The version is outdated. Please upgrade to latest version to see if this persists.

We do not provide technical support for starting from the source. Thank you for your understanding. We assume you have the necessary expertise to set it up independently. If you require technical support, please obtain our business license by contacting us at business@dify.ai.

@crazywoola commented on GitHub (Aug 26, 2025): The version is outdated. Please upgrade to latest version to see if this persists. We do not provide technical support for starting from the source. Thank you for your understanding. We assume you have the necessary expertise to set it up independently. If you require technical support, please obtain our business license by contacting us at business@dify.ai.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#16453
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?