Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

404 Not found when file attachment download #1413

Closed
baek-sang opened this issue Jun 25, 2021 · 2 comments
Closed

404 Not found when file attachment download #1413

baek-sang opened this issue Jun 25, 2021 · 2 comments

Comments

@baek-sang
Copy link

baek-sang commented Jun 25, 2021

Describe the Bug

#1367
Add 2 line global.override.env and restart

globalSettings__attachment__baseDirectory=/etc/bitwarden/core/attachments
globalSettings__attachment__baseUrl=https://site.domain/attachments
  1. 404 not found error when downloading previously uploaded files.
  2. New file upload and download is no problem.

Not exactly, My guess was that there was only bwdata/core/attchments
and it seems that bwdata/core/attachments was added.
Diff is "a", attchment and att[a]chments

Steps To Reproduce

  1. HTTP GET to 'https://site.domain/attachments/rand-string~/rand-string~'
  2. Validate response has '404 Not found'

Expected Result

Downloaded file

Actual Result

404 Not found when previously uploaded file

Screenshots or Videos

Environment

  • Operating system: CentOS 8.4
  • Build Version: 1.41.3
  • Self Hosted: true
  • Environment: Docker
  • Hardware: VPS, AMD Epyc 2gen 4GB RAM

Additional Context

@baek-sang
Copy link
Author

baek-sang commented Jun 26, 2021

Temporary fix
cp -r bwdata/attchments bwdata/attachments

What's different attchments and attachments directory?
If no more using attchments directory, when updated need to delete attchments directory and moving to attachmentsdirectory.

@eliykat
Copy link
Member

eliykat commented Jun 27, 2021

I'll close this issue because it appears to be a duplicate of #1367. Please direct any discussion to that issue report.

This issue will be fixed in the upcoming release.

@eliykat eliykat closed this as completed Jun 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants