[FIXED] Failed to create bucket: invalid signature
Odd, the default install of Supabase gives me this error when I try to create a new bucket: Failed to create bucket: invalid signature
I'm experiencing a persistent issue with the Supabase instance deployed through Dokploy on my server. When attempting to create a storage bucket, I consistently receive the error:
- This error occurs in the Supabase dashboard when trying to create any storage bucket
- I have not modified any of the Supabase configuration files manually
- The server was set up using cloud-init with security hardening (UFW, Fail2Ban, etc.)
- I've already tried disabling the firewall and restarting the server, but the issue persists
The storage service logs show JWT verification errors:
From checking environment variables, all services appear to be using the same JWT secret:
1. Restarting all Supabase services
2. Disabling firewall to eliminate potential networking issues
3. Checking logs for all related services
4. Verifying environment variables for JWT settings across services
Any assistance in resolving this issue would be greatly appreciated.
- Server OS: Ubuntu (running kernel 6.8.0-55-generic)
- Supabase appears to be running in Docker containers managed by Dokploy
- No modifications have been made to the default Supabase setup provided by Dokploy
Thank you for your help,
Old Man Umby
I'm experiencing a persistent issue with the Supabase instance deployed through Dokploy on my server. When attempting to create a storage bucket, I consistently receive the error:
Details:
- This error occurs in the Supabase dashboard when trying to create any storage bucket
- I have not modified any of the Supabase configuration files manually
- The server was set up using cloud-init with security hardening (UFW, Fail2Ban, etc.)
- I've already tried disabling the firewall and restarting the server, but the issue persists
Logs:
The storage service logs show JWT verification errors:
From checking environment variables, all services appear to be using the same JWT secret:
Troubleshooting Steps Already Tried:
1. Restarting all Supabase services
2. Disabling firewall to eliminate potential networking issues
3. Checking logs for all related services
4. Verifying environment variables for JWT settings across services
Any assistance in resolving this issue would be greatly appreciated.
Additional Details:
- Server OS: Ubuntu (running kernel 6.8.0-55-generic)
- Supabase appears to be running in Docker containers managed by Dokploy
- No modifications have been made to the default Supabase setup provided by Dokploy
Thank you for your help,
Old Man Umby
