Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • funkwhale funkwhale
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 405
    • Issues 405
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 21
    • Merge requests 21
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • funkwhalefunkwhale
  • funkwhalefunkwhale
  • Issues
  • #826
Closed
Open
Issue created May 10, 2019 by Ciarán Ainsworth@SporiffOwner

Amazon S3 bucket settings incorrect

Steps to reproduce

  1. Store files in Amazon S3
  2. Enable the new PROXY_MEDIA=false setting in .env

What happens?

All GET requests are met with a 400 error, stating The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.

What is expected?

Media should be served directly from the S3 bucket

Context

Funkwhale version(s) affected: 0.19.0-rc2

  • Configuration: Docker, multi container, Nginx
  • OS Ubuntu 16.04
Assignee
Assign to
Time tracking