Gemini Plugins cannot upload file #908

New Issue

Closed

opened 2026-02-16 10:20:55 -05:00 by yindo · 5 comments

yindo commented 2026-02-16 10:20:55 -05:00

Owner

Copy Link

Copy Source

Originally created by @fatcatloversknnymonkey on GitHub (Dec 27, 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 Dify issues & Dify Official Plugins, 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

.11.2

Plugin version

0.7.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When using the Gemini model in Dify, file uploads fail during conversation. Attempting to upload images or other files results in an error indicating that the file upload URL could not be created.

FILES_URL=http://api:5001
INTERNAL_FILES_URL=http://api:5001

✔️ Error log

No response

Originally created by @fatcatloversknnymonkey on GitHub (Dec 27, 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 [Dify issues](https://github.com/langgenius/dify/issues) & [Dify Official Plugins](https://github.com/langgenius/dify-official-plugins/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 .11.2 ### Plugin version 0.7.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When using the Gemini model in Dify, file uploads fail during conversation. Attempting to upload images or other files results in an error indicating that the file upload URL could not be created. FILES_URL=http://api:5001 INTERNAL_FILES_URL=http://api:5001 <img width="1504" height="870" alt="Image" src="https://github.com/user-attachments/assets/5eec7826-9811-4849-b1ec-f75bf412db25" /> <img width="1978" height="1556" alt="Image" src="https://github.com/user-attachments/assets/47a452ba-91ff-41dc-99ec-b17ba3bc46b0" /> <img width="3414" height="612" alt="Image" src="https://github.com/user-attachments/assets/0614ad64-6e57-49f1-86cb-fb3c4c32c088" /> ### ✔️ Error log _No response_

yindo added the bug label 2026-02-16 10:20:55 -05:00

yindo closed this issue 2026-02-16 10:20:55 -05:00

yindo commented 2026-02-16 10:20:55 -05:00

Author

Owner

Copy Link

Copy Source

@dosubot[bot] commented on GitHub (Dec 27, 2025):

This error is almost always caused by a misconfiguration or networking issue with FILES_URL and INTERNAL_FILES_URL in Docker. Here’s a checklist to resolve it:

1. Make sure both FILES_URL and INTERNAL_FILES_URL are set to http://api:5001 in your .env file.
2. In your docker-compose.yaml, confirm that the API service exposes port 5001 with ports: - "5001:5001". If you add this, restart all containers for changes to take effect.
3. If the error persists, try setting FILES_URL to http://host.docker.internal and restart Docker—this can help with inter-container networking problems in some environments.
4. If you still see the error, check the logs for both the API and plugin containers for more details.

This setup is required because the Gemini plugin fetches files from the Dify file store using these URLs, and if the plugin can’t reach the file server at the specified address, upload URL creation will fail. Users have confirmed that exposing port 5001 and setting these variables correctly resolves the issue in self-hosted Docker setups. More details and examples are available in this issue and this one.

Let me know if you need help interpreting any new log output!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

  

@dosubot[bot] commented on GitHub (Dec 27, 2025): <!-- Answer --> This error is almost always caused by a misconfiguration or networking issue with FILES_URL and INTERNAL_FILES_URL in Docker. Here’s a checklist to resolve it: 1. Make sure both FILES_URL and INTERNAL_FILES_URL are set to `http://api:5001` in your `.env` file. 2. In your `docker-compose.yaml`, confirm that the API service exposes port 5001 with `ports: - "5001:5001"`. If you add this, restart all containers for changes to take effect. 3. If the error persists, try setting FILES_URL to `http://host.docker.internal` and restart Docker—this can help with inter-container networking problems in some environments. 4. If you still see the error, check the logs for both the API and plugin containers for more details. This setup is required because the Gemini plugin fetches files from the Dify file store using these URLs, and if the plugin can’t reach the file server at the specified address, upload URL creation will fail. Users have confirmed that exposing port 5001 and setting these variables correctly resolves the issue in self-hosted Docker setups. More details and examples are available in [this issue](https://github.com/langgenius/dify-official-plugins/issues/2110) and [this one](https://github.com/langgenius/dify-official-plugins/issues/1816). Let me know if you need help interpreting any new log output! <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- ^{How did I do? [Good](https://app.dosu.dev/response-feedback/69d2b3e5-522f-44c6-b0ae-1071ee5e3149?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/69d2b3e5-522f-44c6-b0ae-1071ee5e3149?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/69d2b3e5-522f-44c6-b0ae-1071ee5e3149?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/69d2b3e5-522f-44c6-b0ae-1071ee5e3149?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/69d2b3e5-522f-44c6-b0ae-1071ee5e3149?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/69d2b3e5-522f-44c6-b0ae-1071ee5e3149?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/69d2b3e5-522f-44c6-b0ae-1071ee5e3149?feedback_type=other)} [](https://cursor.com/link/prompt?text=This%20error%20is%20almost%20always%20caused%20by%20a%20misconfiguration%20or%20networking%20issue%20with%20FILES_URL%20and%20INTERNAL_FILES_URL%20in%20Docker.%20Here%E2%80%99s%20a%20checklist%20to%20resolve%20it%3A%0A%0A1.%20Make%20sure%20both%20FILES_URL%20and%20INTERNAL_FILES_URL%20are%20set%20to%20%60http%3A//api%3A5001%60%20in%20your%20%60.env%60%20file.%0A2.%20In%20your%20%60docker-compose.yaml%60%2C%20confirm%20that%20the%20API%20service%20exposes%20port%205001%20with%20%60ports%3A%20-%20%225001%3A5001%22%60.%20If%20you%20add%20this%2C%20restart%20all%20containers%20for%20changes%20to%20take%20effect.%0A3.%20If%20the%20error%20persists%2C%20try%20setting%20FILES_URL%20to%20%60http%3A//host.docker.internal%60%20and%20restart%20Docker%E2%80%94this%20can%20help%20with%20inter-container%20networking%20problems%20in%20some%20environments.%0A4.%20If%20you%20still%20see%20the%20error%2C%20check%20the%20logs%20for%20both%20the%20API%20and%20plugin%20containers%20for%20more%20details.%0A%0AThis%20setup%20is%20required%20because%20the%20Gemini%20plugin%20fetches%20files%20from%20the%20Dify%20file%20store%20using%20these%20URLs%2C%20and%20if%20the%20plugin%20can%E2%80%99t%20reach%20the%20file%20server%20at%20the%20specified%20address%2C%20upload%20URL%20creation%20will%20fail.%20Users%20have%20confirmed%20that%20exposing%20port%205001%20and%20setting%20these%20variables%20correctly%20resolves%20the%20issue%20in%20self-hosted%20Docker%20setups.%20More%20details%20and%20examples%20are%20available%20in%20%5Bthis%20issue%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/2110%29%20and%20%5Bthis%20one%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1816%29.%0A%0ALet%20me%20know%20if%20you%20need%20help%20interpreting%20any%20new%20log%20output%21)&nbsp;[](https://go.dosu.dev/discord-bot)&nbsp;[](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-official-plugins/issues/2343)

yindo commented 2026-02-16 10:20:55 -05:00

Author

Owner

Copy Link

Copy Source

@fatcatloversknnymonkey commented on GitHub (Dec 27, 2025):

I have already provided the error message, but this solution did not work. Additionally, your cloud service has the same issue.

@fatcatloversknnymonkey commented on GitHub (Dec 27, 2025): I have already provided the error message, but this solution did not work. Additionally, your cloud service has the same issue.

yindo commented 2026-02-16 10:20:55 -05:00

Author

Owner

Copy Link

Copy Source

@dosubot[bot] commented on GitHub (Dec 27, 2025):

You’re right—this isn’t just a configuration issue. The Gemini plugin file upload error (“Failed to create file. Upload URL did not return from the create file request”) is a known, unresolved bug that affects both self-hosted and cloud environments. Multiple users have reported that the problem persists even after following all recommended steps, and maintainers are actively tracking it but haven’t published a definitive fix yet. You can see ongoing discussion and confirmation of the issue here: dify-official-plugins issue #2110.

A recent update in Dify core changed the file URL logic to prioritize INTERNAL_FILES_URL over FILES_URL, which may impact plugin behavior (Dify PR #29962), but this hasn’t resolved the Gemini upload bug for everyone. Other plugins have shown similar symptoms, suggesting a systemic issue in how plugins access files internally.

For now, the best course is to monitor the linked issue for updates and provide detailed logs if you notice any new patterns. If you see any changes after future upgrades, sharing your environment details in the issue thread may help maintainers narrow down the root cause.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

  

@dosubot[bot] commented on GitHub (Dec 27, 2025): <!-- Answer --> You’re right—this isn’t just a configuration issue. The Gemini plugin file upload error (“Failed to create file. Upload URL did not return from the create file request”) is a known, unresolved bug that affects both self-hosted and cloud environments. Multiple users have reported that the problem persists even after following all recommended steps, and maintainers are actively tracking it but haven’t published a definitive fix yet. You can see ongoing discussion and confirmation of the issue here: [dify-official-plugins issue #2110](https://github.com/langgenius/dify-official-plugins/issues/2110). A recent update in Dify core changed the file URL logic to prioritize `INTERNAL_FILES_URL` over `FILES_URL`, which may impact plugin behavior ([Dify PR #29962](https://github.com/langgenius/dify/pull/29962)), but this hasn’t resolved the Gemini upload bug for everyone. Other plugins have shown similar symptoms, suggesting a systemic issue in how plugins access files internally. For now, the best course is to monitor the linked issue for updates and provide detailed logs if you notice any new patterns. If you see any changes after future upgrades, sharing your environment details in the issue thread may help maintainers narrow down the root cause. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- ^{How did I do? [Good](https://app.dosu.dev/response-feedback/b57959f2-bbcd-496c-8d37-57b43edeb8fb?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/b57959f2-bbcd-496c-8d37-57b43edeb8fb?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/b57959f2-bbcd-496c-8d37-57b43edeb8fb?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/b57959f2-bbcd-496c-8d37-57b43edeb8fb?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b57959f2-bbcd-496c-8d37-57b43edeb8fb?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/b57959f2-bbcd-496c-8d37-57b43edeb8fb?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b57959f2-bbcd-496c-8d37-57b43edeb8fb?feedback_type=other)} [](https://cursor.com/link/prompt?text=You%E2%80%99re%20right%E2%80%94this%20isn%E2%80%99t%20just%20a%20configuration%20issue.%20The%20Gemini%20plugin%20file%20upload%20error%20%28%E2%80%9CFailed%20to%20create%20file.%20Upload%20URL%20did%20not%20return%20from%20the%20create%20file%20request%E2%80%9D%29%20is%20a%20known%2C%20unresolved%20bug%20that%20affects%20both%20self-hosted%20and%20cloud%20environments.%20Multiple%20users%20have%20reported%20that%20the%20problem%20persists%20even%20after%20following%20all%20recommended%20steps%2C%20and%20maintainers%20are%20actively%20tracking%20it%20but%20haven%E2%80%99t%20published%20a%20definitive%20fix%20yet.%20You%20can%20see%20ongoing%20discussion%20and%20confirmation%20of%20the%20issue%20here%3A%20%5Bdify-official-plugins%20issue%20%232110%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/2110%29.%0A%0AA%20recent%20update%20in%20Dify%20core%20changed%20the%20file%20URL%20logic%20to%20prioritize%20%60INTERNAL_FILES_URL%60%20over%20%60FILES_URL%60%2C%20which%20may%20impact%20plugin%20behavior%20%28%5BDify%20PR%20%2329962%5D%28https%3A//github.com/langgenius/dify/pull/29962%29%29%2C%20but%20this%20hasn%E2%80%99t%20resolved%20the%20Gemini%20upload%20bug%20for%20everyone.%20Other%20plugins%20have%20shown%20similar%20symptoms%2C%20suggesting%20a%20systemic%20issue%20in%20how%20plugins%20access%20files%20internally.%0A%0AFor%20now%2C%20the%20best%20course%20is%20to%20monitor%20the%20linked%20issue%20for%20updates%20and%20provide%20detailed%20logs%20if%20you%20notice%20any%20new%20patterns.%20If%20you%20see%20any%20changes%20after%20future%20upgrades%2C%20sharing%20your%20environment%20details%20in%20the%20issue%20thread%20may%20help%20maintainers%20narrow%20down%20the%20root%20cause.)&nbsp;[](https://go.dosu.dev/discord-bot)&nbsp;[](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-official-plugins/issues/2343)

yindo commented 2026-02-16 10:20:55 -05:00

Author

Owner

Copy Link

Copy Source

@fatelei commented on GitHub (Jan 17, 2026):

this is upload file to google failed, google plugin support use inline parameter, enable this parameter, will not upload file to google

@fatelei commented on GitHub (Jan 17, 2026): this is upload file to google failed, google plugin support use inline parameter, enable this parameter, will not upload file to google

yindo commented 2026-02-16 10:20:55 -05:00

Author

Owner

Copy Link

Copy Source

@dosubot[bot] commented on GitHub (Feb 3, 2026):

Hi, @fatcatloversknnymonkey. 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 file upload failures with the Gemini model in Dify 0.11.2 on self-hosted Docker despite setting FILES_URL and INTERNAL_FILES_URL correctly.
• This is a known unresolved bug affecting both self-hosted and cloud setups related to internal plugin file access.
• A checklist for Docker networking was provided but did not resolve your issue.
• Another user noted a workaround for Google plugin uploads by enabling an inline parameter to avoid uploading files externally.
• The issue remains open and is being tracked in issue #2110 for further updates.

Next Steps

• Please confirm if this issue is still relevant with the latest version of dify-official-plugins by commenting here.
• If no further activity occurs, I will automatically close this issue in 5 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Feb 3, 2026): Hi, @fatcatloversknnymonkey. 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 file upload failures with the Gemini model in Dify 0.11.2 on self-hosted Docker despite setting FILES_URL and INTERNAL_FILES_URL correctly. - This is a known unresolved bug affecting both self-hosted and cloud setups related to internal plugin file access. - A checklist for Docker networking was provided but did not resolve your issue. - Another user noted a workaround for Google plugin uploads by enabling an inline parameter to avoid uploading files externally. - The issue remains open and is being tracked in issue #2110 for further updates. **Next Steps** - Please confirm if this issue is still relevant with the latest version of dify-official-plugins by commenting here. - If no further activity occurs, I will automatically close this issue in 5 days. Thank you for your understanding and contribution!

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

[PR #908] [MERGED] Gitee AI:update name, Support customizable model #1617

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 bug

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#908