Old Man Umby Comments - Answer Overflow

Old Man Umby

•Created by Old Man Umby on 3/18/2025 in #old-help

[FIXED] Failed to create bucket: invalid signature

Fixing "Invalid Signature" in Supabase without changing "stub" entries in Compose file ... Assumptions * You’ve installed Supabase via Dokploy’s app templates. * Dokploy UI is at http://<your-dokploy-url>:3000. * Project name: e.g., supabase-test (adjust as needed). The Fix * Check the Current JWT_SECRET: * In the project dashboard, find the "Environment" or "Settings" section (usually a tab or button). * Look for JWT_SECRET in the list of environment variables. * Copy its value (e.g., JWT_SECRET=pregenerated-secret). * Generate a New SERVICE_ROLE_KEY: * Open jwt.io in a new tab. * Set the payload:

{
  "role": "service_role",
  "iss": "supabase",
  "iat": 1741500000,  # Or current timestamp
  "exp": 1899266400,  # Or ~5 years from now
  "sub": "supabase-test-owner"  # Use your project name + "-owner"
}

{
  "role": "service_role",
  "iss": "supabase",
  "iat": 1741500000,  # Or current timestamp
  "exp": 1899266400,  # Or ~5 years from now
  "sub": "supabase-test-owner"  # Use your project name + "-owner"
}

* In "Verify Signature", paste the JWT_SECRET from Dokploy into the secret box. * Copy the new token from the "Encoded" box (e.g., eyJhbGciOiJIUzI1NiIs...). * Update SERVICE_ROLE_KEY in Dokploy: * Back in Dokploy’s project dashboard, go to the "Environment" section. * Find SERVICE_ROLE_KEY. * Replace its value with the new token from jwt.io. * Save the changes (look for a "Save" or "Apply" button). * Restart the Project: * In the project dashboard, find the "Restart" or "Redeploy" button (usually near the top or in a "Services" tab). * Click it to restart all Supabase services. * Test in Supabase Studio: * Open http://<your-dokploy-url>/supabase-test (adjust URL to your project’s domain). * Go to the Storage section, create a bucket (e.g., test-bucket), and check if it works without errors. Why It Works - The "invalid signature" error was due to the missing sub claim in SERVICE_ROLE_KEY. Adding it fixes token validation. - "Stub" values (TENANT_ID, REGION, GLOBAL_S3_BUCKET) don’t need changing for this fix.

3 replies

DDokploy

•Created by Old Man Umby on 3/18/2025 in #old-help

[FIXED] Failed to create bucket: invalid signature

I've confirmed this is an issue. I've deleted and reinstalled Supabase, making no changes, and the issue is still there. It seems to be installing this way straight out of the box.

3 replies

Gaming

Programming