Error <Code>SignatureDoesNotMatch</Code> when I try Download CSV (for October 2024)

[SkylitSparks]

Hi, 

Is anyone else having this issue? On the Monthly Statement page, when I set it to the month of October 2024 and click Download CSV, I get at error message (see below). I was able to download the tax statement and the other files that are obtained through  Settings > Options > Download Data for your statements.

I use Google Chrome. I've trying clearing the last four weeks of my cache and then trying again. I also logged in via Bing and get the same error message there.

I've seen posts for this issue that date back to 2022 and apparently it was eventually resolved by Etsy without communication to sellers. I'm hoping they'll do the same this time.

Otherwise, if anyone has a solution. I'd like to hear it.

Here is the error message:

<Error>

<Code>SignatureDoesNotMatch</Code>

<Message>Access denied.</Message>

<Details>The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method.</Details>

<StringToSign>GOOG4-RSA-SHA256 20241028T132850Z 20241028/auto/storage/goog4_request 858279be2e70bf31690e30b348f1c30eda011b39fcf9bc87437cc1467d5ab940</StringToSign>

<CanonicalRequest>GET /etsy-monthlystatement-prod-csv-2uq2mw/user/932158947/etsy_statement_2024_10.csv X-Goog-Algorithm=GOOG4-RSA-SHA256&X-Goog-Credential=etsyweb-dsworker%40etsy-web-prod.iam.gserviceaccount.com%2F20241028%2Fauto%2Fstorage%2Fgoog4_request&X-Goog-Date=20241028T132850Z&X-Goog-Expires=604800&X-Goog-SignedHeaders=host host:storage.googleapis.com host UNSIGNED-PAYLOAD</CanonicalRequest>

</Error>

Thanks,

Martine

[ArtDollsbyJD]

I use Edge and was able to download with no problem.

Try a different browser

[SkylitSparks]

Hi,

Thanks, I had tried Edge, I wrote Bing by mistake. I’ll give it another day’s rest and give Firefox a try.

[PincushionFabrics]

Was this ever resolved for you? I'm running into the same problem.

[SkylitSparks]

Hi, trying a different browser didn’t work. I got fed up, waited a week and then tried again in Chrome and it worked. Sorry, no magical solution!