FAQs
Updated at：2025-11-03
SignatureDoesNotMatch
-
Error reason
- The AccessKey ID and AccessKey Secret do not match
- Version incompatibility detected. Starting from version v0.9.05, the SDK automatically enables bucket virtual hosting by default. If a user encounters an incorrect signature error, it may result from using an outdated SDK version that fails to properly construct a four-level domain name.
- The client’s network layer modifies the HTTP request. Network configurations on the client side may alter the host in the request header, leading to discrepancies between the server-identified host and signature verification results.
-
Solution:
- Users check their own AK and SK
- Update the SDK to the latest version
- The client verifies the outbound network route and displays the header and body fields of the request before transmission. Then, it contacts the BOS on-duty staff to confirm whether the backend has received a request with consistent header and other fields.
Unable to execute HTTP request
-
Error reason
- The network connection to the BOS domain name is unavailable
- Occasional network connection fluctuations or the client environment’s CPU and IO being fully occupied
-
Solution:
- Use ping domain name to check whether the issue is caused by a network failure on the machine
- The business side retries