Hey there!
Hey there!
I've been trying to use R2 as an drop-in replacement to S3, but I've been running into some troubles. Intermittently my multipart uploads fail with the following error
SignatureDoesNotMatch. I've tried to reproduce this locally and it seems like it happens when I simulate a temporary network disconnect / connect to a vpn. If I try the same reproduction steps with S3, the bug never occurs. Its making using r2 in any s3 compatible project quite flakey as a result.
Any help would be greatly appreciated, please lmk if there is any more details I can provide that would help!5 Replies
Hey folks gentle bump on this. This bug is completely workflow breaking
Does this happen in prod/staging when you disconnect the network/connect to vpn too?
I can't tell whats happening in prod because an external vendor is the one hosting the servers.
That being said its odd that R2 returns a 403 SignatureDoesNotMatch in this case.
IIUC S3 signature process should not be dependent on the netowork being stable
That does seem strange, but if you knew it was fine in prod it might be easier to debug since then you'd know it's not just a local issue
Oh I see! Sorry I misunderstood your question.
Yea the issue occurs in prod as well, that's how I discovered it