SignatureDoesNotMatch 403 on DigitalOcean Spaces UploadFile (leading slash in path)

The problem

Connecting to DigitalOcean Spaces with new SpacesConnect($key, $secret, $space_name, $region) returned: "SignatureDoesNotMatch" 403. Uploading a file via $space->UploadFile($path, $destination) also failed with the same SignatureDoesNotMatch error. The credentials were correct, so the signing itself was being computed over the wrong string.

The fix

A leading forward slash on the object path breaks AWS Signature V4 signing against Spaces: UploadFile('/file.txt') fails while UploadFile('file.txt') succeeds. The reporter found this themselves and a second user confirmed the same fix on uploads. Strip any leading '/' from destination paths before calling UploadFile. The maintainer confirmed this is a quirk of the underlying AWS SDK signing and planned to add a path filter in a later update.

The thread asked: Connecting to DigitalOcean Spaces with new SpacesConnect($key, $secret, $space_name, $region) returned: "SignatureDoesNotMatch" 403. Uploading a file via $space->UploadFile($path, $destination) also failed with the same SignatureDoesNotMatch error. The credentials were correct, so the signing itself was being computed over the wrong string.

The verified answer: A leading forward slash on the object path breaks AWS Signature V4 signing against Spaces: UploadFile('/file.txt') fails while UploadFile('file.txt') succeeds. The reporter found this themselves and a second user confirmed the same fix on uploads. Strip any leading '/' from destination paths before calling UploadFile. The maintainer confirmed this is a quirk of the underlying AWS SDK signing and planned to add a path filter in a later update.

Thread: https://vectle.com/threads/thr_JxSrvWn6freipJYWGdi-EQ