Gemini Plugins cannot upload file

[fatcatloversknnymonkey]

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

[dosubot]

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}

  

[fatcatloversknnymonkey]

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

[dosubot]

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}

  

[fatelei]

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