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

The multimodal large model encounters a 403 error when using the image link #6177

New Issue
Closed
opened 2026-02-21 18:14:23 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:14:23 -05:00
Owner
Copy Link
Copy Source

Originally created by @andylzming on GitHub (Oct 20, 2024).

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 search for existing issues, 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

0.8.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  • The multimodal large model encounters a 403 error when using the image link, but the image can be previewed normally through a browser.

0

1

2

3

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @andylzming on GitHub (Oct 20, 2024). ### 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 [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 (我已阅读并同意 [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 0.8.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce - The multimodal large model encounters a 403 error when using the image link, but the image can be previewed normally through a browser. ![0](https://github.com/user-attachments/assets/e7a5ef07-a2d1-49ac-af6d-62aa530428f6) ![1](https://github.com/user-attachments/assets/741337f3-d797-4c37-9e2d-63d21e807fcf) ![2](https://github.com/user-attachments/assets/ab13c0b8-e4c2-4202-ac3f-cf693006e4a9) ![3](https://github.com/user-attachments/assets/a52ee626-4cb8-4027-9aab-47c20a75f951) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:14:23 -05:00
yindo closed this issue 2026-02-21 18:14:23 -05:00
yindo commented 2026-02-21 18:14:23 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 20, 2024):

I found some relevant information regarding 403 errors in the Dify platform. A common cause of a 403 error when accessing image links is missing access permissions. The error message often indicates that the request is denied due to incorrect or missing authorization headers. The expected format for the Authorization header is Bearer <api-key> [1].

Additionally, there are similar discussions and issues related to 403 errors in the Dify repository:

  1. I can't upload the image on dify workflow via api - This discussion is still open and might provide insights or solutions relevant to your issue.
  2. 403 Forbidden - Another open discussion that could be related to your problem.
  3. HTTP 请求时，提示403错误 - This issue is closed, and the suggested solution was related to another issue (#1542).

You might want to check these discussions for any updates or solutions that could help resolve the 403 error you're encountering with the multimodal large model in your self-hosted Dify instance.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Oct 20, 2024): <!-- Answer --> I found some relevant information regarding 403 errors in the Dify platform. A common cause of a 403 error when accessing image links is missing access permissions. The error message often indicates that the request is denied due to incorrect or missing authorization headers. The expected format for the Authorization header is `Bearer <api-key>` <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/jp/.gitbook/assets/Dify-test.openapi.jp.json)</sup>. Additionally, there are similar discussions and issues related to 403 errors in the Dify repository: 1. [I can't upload the image on dify workflow via api](https://github.com/langgenius/dify/discussions/7482) - This discussion is still open and might provide insights or solutions relevant to your issue. 2. [403 Forbidden](https://github.com/langgenius/dify/discussions/6970) - Another open discussion that could be related to your problem. 3. [HTTP 请求时，提示403错误](https://github.com/langgenius/dify/issues/5166) - This issue is closed, and the suggested solution was related to another issue (#1542). You might want to check these discussions for any updates or solutions that could help resolve the 403 error you're encountering with the multimodal large model in your self-hosted Dify instance. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
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#6177
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?