Documentation

While configuring your Google Cloud Storage connection, you may encounter several issues. Understanding these common errors can help streamline the setup process and facilitate quick resolutions.

Wrong private key

Error message:

Solution

Check Key Format and Encryption:

• Ensure your key is an AES-256 key encoded in standard Base64. This is the required format if you're not using the Default Cloud Storage encryption type.
• Verify that the key hasn't been corrupted and is correctly encoded.

Use Cloud KMS Key:

• Alternatively, if you're using a Cloud Key Management Service (KMS) key, ensure that you provide the correct resource name of the Cloud KMS key used to encrypt the blob's contents.

Update Key in Settings:

• Once you have verified or corrected the key, update this information in your Google Cloud Storage settings.

Test the Key:

• After updating the key, test to ensure that it correctly decrypts or accesses the required data.

Refer to the Documentation if necessary.

Wrong Bucket Name

Error message:

Solution

Verify Bucket Name:

• Ensure that the bucket name specified in your request is correct. Check for any typographical errors and confirm that the bucket exists in your Google Cloud Storage.

Check Key Format and Type:

• If the bucket name is correct, review the format and type of the key you are using. Ensure it is compatible with Google Cloud Storage requirements. Google Cloud Storage typically uses AES-256 keys encoded in Base64 or Cloud KMS keys.

Encryption Algorithm Compatibility:

• Verify that the encryption algorithm used for the key is supported by Google Cloud Storage. If it’s encrypted with an unsupported algorithm, this could lead to deserialization issues.

Regenerate or Convert Key:

• If the key is in an incorrect format or encrypted with an unsupported algorithm, consider regenerating the key using Google Cloud's key management tools or converting it to a supported format.

Update Configuration:

• Once you have the correct bucket name and a properly formatted key, update these details in your configuration.

Test Access:

• After making these changes, test accessing the bucket again to ensure the issue is resolved.

‍