Issue Station
Sign In
Tools hereToolbox

dify - 💡(How to fix) Fix Gemini provider validation fails with no proper instance even when plugin runtime is ready [6 comments, 3 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#35455•Fetched 2026-04-22 08:04:06
View on GitHub
Comments
6
Participants
3
Timeline
16
Reactions
2
Author
CXK6013CXK6013
Participants
CXK6013CXK6013dosubot[bot]dosubot[bot]fateleifatelei
Timeline (top)
commented ×6subscribed ×5mentioned ×4labeled ×1

Fix Action

Fix / Workaround

If the Gemini plugin runtime has already started and plugin-daemon reports the runtime as ready, Dify should dispatch the validation request to that ready instance instead of returning "no proper instance".

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.13.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. Deploy self-hosted Dify with Docker Compose.
  2. Use the following versions:
    • Dify API: 1.13.2
    • Dify Web: 1.13.2
    • Plugin Daemon: 0.5.8-local-linux-amd64
  3. Install Gemini plugin:
    • langgenius/gemini:0.7.20
  4. Open Dify console and go to Model Provider settings.
  5. Add/configure Gemini provider credentials.
  6. Click Save.
  7. The request fails with: 
    PluginDaemonInternalServerError: no proper instance

✔️ Expected Behavior

Gemini provider credentials should be validated successfully after clicking Save.

If the Gemini plugin runtime has already started and plugin-daemon reports the runtime as ready, Dify should dispatch the validation request to that ready instance instead of returning "no proper instance".

❌ Actual Behavior

After clicking Save for Gemini provider credentials, the request fails with: PluginDaemonInternalServerError: no proper instance

extent analysis

TL;DR

The issue can be resolved by ensuring the Gemini plugin runtime is properly started and reported as ready by the plugin-daemon before attempting to validate the Gemini provider credentials.

Guidance

  • Verify that the Gemini plugin runtime is started and reported as ready by checking the plugin-daemon logs or status.
  • Check the compatibility of the Gemini plugin version (0.7.20) with the Dify API version (1.13.2) and Plugin Daemon version (0.5.8-local-linux-amd64).
  • Ensure that the Plugin Daemon is configured correctly to manage the Gemini plugin runtime.
  • Try restarting the Plugin Daemon and Gemini plugin runtime to see if it resolves the issue.

Example

No code snippet is provided as the issue is related to plugin configuration and compatibility.

Notes

The issue may be related to a compatibility problem between the Gemini plugin and the Dify API or Plugin Daemon. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Ensure the Gemini plugin runtime is started and reported as ready before validating the provider credentials, as this may resolve the issue temporarily until a permanent fix is found.

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…
#api#ssr#output truncation#response parsing#generation error

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 Gemini provider validation fails with no proper instance even when plugin runtime is ready [6 comments, 3 participants]