[GH-ISSUE #6499] [Bug] Self-Hosted: Unable to Download Attached File #2861

New issue

Closed

opened 2026-03-23 21:25:47 +00:00 by mirror · 1 comment

mirror commented

2026-03-23 21:25:47 +00:00

Owner

Originally created by @capybaras-team on GitHub (Oct 7, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/6499

Bug Description

When clicking on an attached file in the File block, the browser opens and displays the following error:
{"code":1017,"message":"Can't find the user uuid from the request: No Authorization header"}

How to Reproduce

Install Appflowy Cloud on your server.
Create a new document.
Add a "File" block.
Attach a file.
Click on the attached file.

Expected Behavior

The file should be downloadable from any device that has access to the workflow.

Operating System

Windows, Android

AppFlowy Version(s)

0.7.0.0

Screenshots

No response

Additional Context

No response

Originally created by @capybaras-team on GitHub (Oct 7, 2024). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/6499 ### Bug Description When clicking on an attached file in the File block, the browser opens and displays the following error: {"code":1017,"message":"Can't find the user uuid from the request: No Authorization header"} ### How to Reproduce 1. Install Appflowy Cloud on your server. 2. Create a new document. 3. Add a "File" block. 4. Attach a file. 5. Click on the attached file. ### Expected Behavior The file should be downloadable from any device that has access to the workflow. ### Operating System Windows, Android ### AppFlowy Version(s) 0.7.0.0 ### Screenshots _No response_ ### Additional Context _No response_

mirror

2026-03-23 21:25:47 +00:00

closed this issue
added the
self-hosted

mobile

platform-windows

bug
labels

mirror commented

2026-03-23 21:25:47 +00:00

Author

Owner

@khorshuheng commented on GitHub (Oct 7, 2024):

The main reason is due to the fact that there is no authentication information attached to the URL itself. So for the time being, the workaround would be to set APPFLOWY_ACCESS_CONTROL to false.

@khorshuheng commented on GitHub (Oct 7, 2024): The main reason is due to the fact that there is no authentication information attached to the URL itself. So for the time being, the workaround would be to set APPFLOWY_ACCESS_CONTROL to false.

mirror referenced this issue

2026-03-23 22:18:46 +00:00

[PR #2861] [MERGED] feat: put all user data into a folder when choosing a custom storage path #5444