Backblaze B2 - Invalid URL #321

Closed
opened 2026-04-05 16:17:24 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @jkop-xyz on 8/4/2025

Hi,
Trying to add backblaze b2 as an s3 endpoint in the env file but no mather how i seem to configure it, it just returns a invalid URL error.

I have tried s3.eu-central-003.backblazeb2.com and s3.backblazeb2.com as the ENDPOINT aswell as both eu-central-003 and uncommenting/leaving REGION blank.

STORAGE_S3_ENDPOINT=s3.eu-central-003.backblazeb2.com STORAGE_S3_BUCKET=xxxx STORAGE_S3_ACCESS_KEY_ID=xxxx STORAGE_S3_SECRET_ACCESS_KEY='xxxx' STORAGE_S3_REGION=eu-central-003 STORAGE_S3_FORCE_PATH_STYLE=true

[0] [0] Ingestion worker started [1] packages/backend start: Backend listening at http://localhost:4000 [1] packages/backend start: Delete ingestion source 3b29ac9d-2d82-4115-92db-dd3ecbcfa68d error: TypeError: Invalid URL [1] packages/backend start: at new URL (node:internal/url:825:25) [1] packages/backend start: at parseUrl (/app/node_modules/.pnpm/@smithy+url-parser@4.0.4/node_modules/@smithy/url-parser/dist-cjs/index.js:29:21) [1] packages/backend start: at toEndpointV1 (/app/node_modules/.pnpm/@smithy+middleware-endpoint@4.1.14/node_modules/@smithy/middleware-endpoint/dist-cjs/index.js:123:41) [1] packages/backend start: at customEndpointProvider (/app/node_modules/.pnpm/@smithy+middleware-endpoint@4.1.14/node_modules/@smithy/middleware-endpoint/dist-cjs/index.js:254:65) [1] packages/backend start: at process.processTicksAndRejections (node:internal/process/task_queues:105:5) { [1] packages/backend start: code: 'ERR_INVALID_URL', [1] packages/backend start: input: 's3.eu-central-003.backblazeb2.com' [1] packages/backend start: } [0] [0] Scheduler running: Looking for active or error ingestion sources to sync.

Any idea whats happening here?

*Originally created by @jkop-xyz on 8/4/2025* Hi, Trying to add backblaze b2 as an s3 endpoint in the env file but no mather how i seem to configure it, it just returns a invalid URL error. I have tried s3.eu-central-003.backblazeb2.com and s3.backblazeb2.com as the ENDPOINT aswell as both eu-central-003 and uncommenting/leaving REGION blank. `STORAGE_S3_ENDPOINT=s3.eu-central-003.backblazeb2.com STORAGE_S3_BUCKET=xxxx STORAGE_S3_ACCESS_KEY_ID=xxxx STORAGE_S3_SECRET_ACCESS_KEY='xxxx' STORAGE_S3_REGION=eu-central-003 STORAGE_S3_FORCE_PATH_STYLE=true` `[0] [0] Ingestion worker started [1] packages/backend start: Backend listening at http://localhost:4000 [1] packages/backend start: Delete ingestion source 3b29ac9d-2d82-4115-92db-dd3ecbcfa68d error: TypeError: Invalid URL [1] packages/backend start: at new URL (node:internal/url:825:25) [1] packages/backend start: at parseUrl (/app/node_modules/.pnpm/@smithy+url-parser@4.0.4/node_modules/@smithy/url-parser/dist-cjs/index.js:29:21) [1] packages/backend start: at toEndpointV1 (/app/node_modules/.pnpm/@smithy+middleware-endpoint@4.1.14/node_modules/@smithy/middleware-endpoint/dist-cjs/index.js:123:41) [1] packages/backend start: at customEndpointProvider (/app/node_modules/.pnpm/@smithy+middleware-endpoint@4.1.14/node_modules/@smithy/middleware-endpoint/dist-cjs/index.js:254:65) [1] packages/backend start: at process.processTicksAndRejections (node:internal/process/task_queues:105:5) { [1] packages/backend start: code: 'ERR_INVALID_URL', [1] packages/backend start: input: 's3.eu-central-003.backblazeb2.com' [1] packages/backend start: } [0] [0] Scheduler running: Looking for active or error ingestion sources to sync.` Any idea whats happening here?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/OpenArchiver#321