dify - 💡(How to fix) Fix [Bug] online-users endpoint broken due to incorrect runtime type error [5 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langgenius/dify#35712Fetched 2026-04-30 06:45:18
View on GitHub
Comments
5
Participants
2
Timeline
12
Reactions
1
Author
Participants
Assignees
Timeline (top)
commented ×5labeled ×2mentioned ×2subscribed ×2

Error Message

The endpoint should be accessible and the homepage stops showing Internal Server Error. Internal Server Error alert keeps showing in interval, and errors growing in Developer Tools with 500 response from online-users endpoint.

Fix Action

Fix / Workaround

Upgrade to 1.14.0 and then go to the homepage.

RAW_BUFFERClick to expand / collapse

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

1.14.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Upgrade to 1.14.0 and then go to the homepage.

✔️ Expected Behavior

The endpoint should be accessible and the homepage stops showing Internal Server Error.

❌ Actual Behavior

Internal Server Error alert keeps showing in interval, and errors growing in Developer Tools with 500 response from online-users endpoint.

extent analysis

TL;DR

The issue with the Internal Server Error on the homepage after upgrading to version 1.14.0 may be resolved by investigating and fixing the online-users endpoint.

Guidance

  • Check the server logs for any errors related to the online-users endpoint to identify the root cause of the 500 response.
  • Verify that the online-users endpoint is properly configured and deployed in the self-hosted Docker environment.
  • Test the online-users endpoint directly using a tool like curl or Postman to isolate the issue.
  • Review the release notes for version 1.14.0 to see if there are any known issues or changes that could be affecting the online-users endpoint.

Notes

The issue seems to be specific to the self-hosted Docker environment and the online-users endpoint, so the solution may involve environment-specific configuration or code changes.

Recommendation

Apply workaround: Investigate and fix the online-users endpoint, as it is the likely cause of the Internal Server Error.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

dify - 💡(How to fix) Fix [Bug] online-users endpoint broken due to incorrect runtime type error [5 comments, 2 participants]