mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 00:29:48 +03:00
Unable to show uploaded avatars and images #1393
Closed
opened 2026-02-05 00:46:37 +03:00 by OVERLORD
·
6 comments
No Branch/Tag Specified
development
l10n_development
further_theme_development
release
llm_only
vectors
v25-11
docker_env
drawio_rendering
user_permissions
ldap_host_failover
svg_image
prosemirror
captcha_example
fix/video-export
v25.12.3
v25.12.2
v25.12.1
v25.12
v25.11.6
v25.11.5
v25.11.4
v24.11.4
v25.11.3
v25.11.2
v25.11.1
v25.11
v25.07.3
v25.07.2
v25.07.1
v25.07
v25.05.2
v25.05.1
v25.05
v25.02.5
v25.02.4
v25.02.3
v25.02.2
v25.02.1
v25.02
v24.12.1
v24.12
v24.10.3
v24.10.2
v24.10.1
v24.10
v24.05.4
v24.05.3
v24.05.2
v24.05.1
v24.05
v24.02.3
v24.02.2
v24.02.1
v24.02
v23.12.3
v23.12.2
v23.12.1
v23.12
v23.10.4
v23.10.3
v23.10.2
v23.10.1
v23.10
v23.08.3
v23.08.2
v23.08.1
v23.08
v23.06.2
v23.06.1
v23.06
v23.05.2
v23.05.1
v23.05
v23.02.3
v23.02.2
v23.02.1
v23.02
v23.01.1
v23.01
v22.11.1
v22.11
v22.10.2
v22.10.1
v22.10
v22.09.1
v22.09
v22.07.3
v22.07.2
v22.07.1
v22.07
v22.06.2
v22.06.1
v22.06
v22.04.2
v22.04.1
v22.04
v22.03.1
v22.03
v22.02.3
v22.02.2
v22.02.1
v22.02
v21.12.5
v21.12.4
v21.12.3
v21.12.2
v21.12.1
v21.12
v21.11.3
v21.11.2
v21.11.1
v21.11
v21.10.3
v21.10.2
v21.10.1
v21.10
v21.08.6
v21.08.5
v21.08.4
v21.08.3
v21.08.2
v21.08.1
v21.08
v21.05.4
v21.05.3
v21.05.2
v21.05.1
v21.05
v21.04.6
v21.04.5
v21.04.4
v21.04.3
v21.04.2
v21.04.1
v21.04
v0.31.8
v0.31.7
v0.31.6
v0.31.5
v0.31.4
v0.31.3
v0.31.2
v0.31.1
v0.31.0
v0.30.7
v0.30.6
v0.30.5
v0.30.4
v0.30.3
v0.30.2
v0.30.1
v0.30.0
v0.29.3
v0.29.2
v0.29.1
v0.29.0
v0.28.3
v0.28.2
v0.28.1
v0.28.0
v0.27.5
v0.27.4
v0.27.3
v0.27.2
v0.27.1
v0.27
v0.26.4
v0.26.3
v0.26.2
v0.26.1
v0.26.0
v0.25.5
v0.25.4
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.3
v0.24.2
v0.24.1
v0.24.0
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.3
v0.20.2
v0.20.1
v0.20.0
v0.19.0
v0.18.5
v0.18.4
v0.18.3
v0.18.2
v0.18.1
v0.18.0
v0.17.4
v0.17.3
v0.17.2
v0.17.1
v0.17.0
v0.16.3
v0.16.2
v0.16.1
v0.16.0
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.3
v0.14.2
v0.14.1
v0.14.0
v0.13.1
v0.13.0
v0.12.2
v0.12.1
v0.12.0
v0.11.2
v0.11.1
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.2
v0.8.1
v0.8.0
v0.7.6
v0.7.5
v0.7.4
v0.7.3
0.7.2
v.0.7.1
v0.7.0
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.0
Labels
Clear labels
🎨 Design
📖 Docs Update
🐛 Bug
🐛 Bug
:cat2:🐈 Possible duplicate
💿 Database
☕ Open to discussion
💻 Front-End
🐕 Support
🚪 Authentication
🌍 Translations
🔌 API Task
🏭 Back-End
⛲ Upstream
🔨 Feature Request
🛠️ Enhancement
🛠️ Enhancement
🛠️ Enhancement
❤️ Happy feedback
🔒 Security
🔍 Pending Validation
💆 UX
📝 WYSIWYG Editor
🌔 Out of scope
🔩 API Request
:octocat: Admin/Meta
🖌️ View Customization
❓ Question
🚀 Priority
🛡️ Blocked
🚚 Export System
♿ A11y
🔧 Maintenance
> Markdown Editor
No Label
🐕 Support
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/BookStack#1393
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
Originally created by @mzch on GitHub (Oct 8, 2019).
Describe the bug
When uploading an avatar or an image to s3 compatible storage, Bookstack shows an empty image.
Steps To Reproduce
Steps to reproduce the behavior:
Expected behavior
Uploaded image is shown.
Screenshots
Your Configuration (please complete the following information):
Additional context
All images uploaded are not shown other than avatars. I tried to upload avatars and images to s3 and local_secure, but the result is the same.
@ssddanbrown commented on GitHub (Oct 9, 2019):
Hi @mzch,
Sorry to hear you are having issues.
When selecting and saving an avatar does the file get created in your selected storage destination? Do you have any luck when using just the 'local` storage option?
@mzch commented on GitHub (Oct 9, 2019):
Hi @ssddanbrown,
Yes, the image was saved on S3 (Compatible storage). When specified local_secure, it was also saved on the right place. When using 'local' option, the image is shown correctly.
@John-OShea-Wordbank commented on GitHub (Jan 12, 2020):
Hi @ssddanbrown,
We're seeing the same thing and it looks to be related to the
STORAGE_S3_REGION.env variable.With it set to
us-east-1, I can see the file uploaded to the correct bucket location and get set to public access. There are no exceptions thrown, either uploading or afterwards, but the image doesn't get shown after that. Subsequent requests for the file are tohttps://s3-us-east-1.amazonaws.com/OUR_BUCKET_NAME/uploads/images/user/2020-01/thumbs-80-80/john_256x256.jpgbut the correct URL should be
https://s3.amazonaws.com/OUR_BUCKET_NAME/uploads/images/user/2020-01/thumbs-80-80/john_256x256.jpg(i.e. no region name as part of the hostname)Removing the STORAGE_S3_REGION setting entirely or setting it to an empty string throws an exception on upload:
Hope that helps!
@mzch commented on GitHub (Jan 12, 2020):
When I removed
STORAGE_S3_REGION, BookStack reported 'An Error Occurred'laravel.logWhen adding
STORAGE_S3_REGION=us-east-1, no error was recorded, but no image was shown.@John-OShea-Wordbank commented on GitHub (Jan 20, 2020):
My original comment was incorrect - sorry for the confusion. Replacing the first hyphen with a full stop seems to be working OK for us (we need to do more testing to confirm though).
Non-working URL format:
https://s3-us-east-1.amazonaws.com/OUR_BUCKET_NAME/uploads/images/user/2020-01/thumbs-80-80/john_256x256.jpgWorking URL format:
https://s3.us-east-1.amazonaws.com/OUR_BUCKET_NAME/uploads/images/user/2020-01/thumbs-80-80/john_256x256.jpgThe line we amended
@ssddanbrown commented on GitHub (May 2, 2021):
Since the last comment on this issue is relatively old I'm going to close this. If the issue remains and is something you still require to be fixed please open a new issue, referencing this one.