[Bug]: Public S3 folder doesn't authorize on Cloudflare R2 #672

New Issue

OVERLORD · 2026-02-04T20:46:52+03:00

OVERLORD commented

2026-02-04 20:46:52 +03:00

Originally created by @adiologydev on GitHub (Mar 26, 2025).

Where is the problem occurring?

I encountered the problem while using the application (Frontend)

What browsers are you seeing the problem on?

Firefox

Current behaviour

Hey,

I'm using Cloudflare R2 as my S3 provider on Planka.
It works great for private uploads i.e. everything that goes in private subdirectory in the R2 bucket because Planka uses proper access key and secret to authorize and retrieve that data.

However, when it comes to things like user profile pictures which are stored public subdirectory of the bucket, it tries to do a direct GET request and fails.

R2 only allows you to use public paths if you use an R2 or custom domain which doesn't behave the same as S3.

Is there any workaround to this?

Desired behaviour

The public data should either authorize with S3 or allow for a workaround with public proxy (such as R2 domain/custom domain) in the case of Cloudflare R2.

Steps to reproduce

Setup a Cloudflare R2 Bucket
Create credentials and add them to Planka docker config.
Upload a profile picture.

Other information

No response

Originally created by @adiologydev on GitHub (Mar 26, 2025). ### Where is the problem occurring? I encountered the problem while using the application (Frontend) ### What browsers are you seeing the problem on? Firefox ### Current behaviour Hey, I'm using Cloudflare R2 as my S3 provider on Planka. It works great for private uploads i.e. everything that goes in `private` subdirectory in the R2 bucket because Planka uses proper access key and secret to authorize and retrieve that data. However, when it comes to things like user profile pictures which are stored `public` subdirectory of the bucket, it tries to do a direct GET request and fails. R2 only allows you to use public paths if you use an R2 or custom domain which doesn't behave the same as S3. Is there any workaround to this? ### Desired behaviour The public data should either authorize with S3 or allow for a workaround with public proxy (such as R2 domain/custom domain) in the case of Cloudflare R2. ### Steps to reproduce - Setup a Cloudflare R2 Bucket - Create credentials and add them to Planka docker config. - Upload a profile picture. ### Other information _No response_

OVERLORD added the enhancement label 2026-02-04 20:46:52 +03:00

OVERLORD referenced this issue

2026-02-04 21:47:30 +03:00

[PR #672] [MERGED] fix: Allow specifying an external dburl in helm #1062

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/planka#672