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

Under certain conditions, the access log cannot be displayed from the Web UI #7568

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

Originally created by @fujita-h on GitHub (Jan 7, 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 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.14.2

Cloud or Self Hosted

Cloud, Self Hosted (Docker), Self Hosted (Source)

Steps to reproduce

  • Create new chatflow.
  • Set single file input to start node.
  • Connect start node to Answer node.
  • Publish App.
  • Add API Key.
  • Call the API like below
curl -X POST 'http://localhost:5001/v1/chat-messages' \
--header 'Authorization: Bearer {api_key}' \
--header 'Content-Type: application/json' \
--data-raw '{
    "inputs": {
       "file": {
            "transfer_method": "remote_url",
            "type": "image",
            "url": "https://cloud.dify.ai/logo/logo-site.png"
       }
    },
    "query": "test",
    "response_mode": "blocking",
    "conversation_id": "",
    "user": "abc-123",
    "files": []
}'
  • View the logs for this request in the WebUI.

✔️ Expected Behavior

The log is displayed

❌ Actual Behavior

"invalid file url" error message displayed.

Originally created by @fujita-h on GitHub (Jan 7, 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 [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.14.2 ### Cloud or Self Hosted Cloud, Self Hosted (Docker), Self Hosted (Source) ### Steps to reproduce - Create new chatflow. - Set single file input to start node. - Connect start node to Answer node. - Publish App. - Add API Key. - Call the API like below ``` curl -X POST 'http://localhost:5001/v1/chat-messages' \ --header 'Authorization: Bearer {api_key}' \ --header 'Content-Type: application/json' \ --data-raw '{ "inputs": { "file": { "transfer_method": "remote_url", "type": "image", "url": "https://cloud.dify.ai/logo/logo-site.png" } }, "query": "test", "response_mode": "blocking", "conversation_id": "", "user": "abc-123", "files": [] }' ``` - View the logs for this request in the WebUI. ### ✔️ Expected Behavior The log is displayed ### ❌ Actual Behavior "invalid file url" error message displayed.
yindo added the 🐞 bug label 2026-02-21 18:21:14 -05:00
yindo closed this issue 2026-02-21 18:21:14 -05:00
yindo commented 2026-02-21 18:21:14 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 7, 2025):

I found a similar open issue regarding the "Invalid file url" error in Dify version 0.14.2. The suggested solution is to ensure that the FILES_URL environment variable is correctly configured in your docker-compose.yaml file. This variable should be set to a valid base URL pointing to where your files are hosted. For example, if your files are accessible at http://yourdomain.com/files, update the configuration as follows:

FILES_URL: 'http://yourdomain.com/files'

After making this change, restart your Dify services to apply the updates. You can find more details in the related issue here [1].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot[bot] commented on GitHub (Jan 7, 2025): <!-- Answer --> I found a similar open issue regarding the "Invalid file url" error in Dify version 0.14.2. The suggested solution is to ensure that the `FILES_URL` environment variable is correctly configured in your `docker-compose.yaml` file. This variable should be set to a valid base URL pointing to where your files are hosted. For example, if your files are accessible at `http://yourdomain.com/files`, update the configuration as follows: ```yaml FILES_URL: 'http://yourdomain.com/files' ``` After making this change, restart your Dify services to apply the updates. You can find more details in the related issue [here](https://github.com/langgenius/dify/issues/12209) <sup>[[1]](https://github.com/langgenius/dify/issues/12209)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/863f5a31-37cf-43bc-b316-734309438236?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/863f5a31-37cf-43bc-b316-734309438236?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/863f5a31-37cf-43bc-b316-734309438236?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/863f5a31-37cf-43bc-b316-734309438236?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/863f5a31-37cf-43bc-b316-734309438236?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/863f5a31-37cf-43bc-b316-734309438236?feedback_type=other)</sup>
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#7568
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?