search

lobehub / lobe-chat

🤯 Lobe Chat - an open-source, modern-design AI chat framework. Supports Multi AI Providers( OpenAI / Claude 3 / Gemini / Ollama / Azure / DeepSeek), Knowledge Base (file upload / knowledge management / RAG ), Multi-Modals (Vision/TTS) and plugin system. One-click FREE deployment of your private ChatGPT/ Claude application.
https://chat-preview.lobehub.com
Other
44.59k stars 10k forks source link

S3 storage: Not able to use bitiful.com as S3 storage #4710

Open YiyangLu opened 2 hours ago

YiyangLu commented 2 hours ago

📝 Reference

https://github.com/lobehub/lobe-chat/tree/main/docs/self-hosting/server-database/vercel.zh-CN.mdx

🐛 Feedback

Success fully deploy cloudflare R2 S3 storage. Then, I switch to other S3 storage provider and meet the problem.

When using bitful.com with correct keys, we would get SignatureDoesNotMatch (error 403) for file uploading: The request signature we calculated does not match the signature you provided. Check your key and signing method.

lobehubbot commented 2 hours ago

👀 @YiyangLu

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. Please make sure you have given us as much context as possible.\ 非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

dosubot[bot] commented 2 hours ago

Hello, @YiyangLu! I'm here to help you with any bugs, questions, or contributions. Let's work together to solve this issue.

The error you're encountering, "SignatureDoesNotMatch," typically indicates an issue with the signature calculation for the S3 request. This can happen if the signing method or the parameters used for generating the signature are not compatible with the specific S3 provider, in this case, bitiful.com.

Here are a few steps you can take to troubleshoot and resolve this issue:

  1. Verify Credentials: Double-check that the access key and secret key are correct and have the necessary permissions for the operations you're trying to perform.

  2. Check Endpoint Configuration: Ensure that the endpoint URL is correctly configured for bitiful.com. Different S3-compatible providers might have different endpoint formats.

  3. Review Signature Version: Some S3-compatible providers may require a specific signature version (e.g., v2 or v4). Verify if bitiful.com requires a specific version and ensure your configuration matches this requirement.

  4. Path vs. Virtual Hosted Style: Check if bitiful.com requires path-style or virtual-hosted-style URLs and configure your requests accordingly.

  5. Custom Signing Method: If bitiful.com has specific requirements for signing requests, you might need to implement a custom signing method. Unfortunately, I couldn't find specific documentation in the Lobe Chat framework for custom signing methods, so you may need to refer to bitiful.com's documentation for guidance.

If these steps do not resolve the issue, you may need to consult bitiful.com's documentation or support for more specific guidance on their S3 implementation.

To continue talking to Dosu, mention @dosu.