Signature no longer valid, out of the blue.

JordanUnitedForGood
JordanUnitedForGood Member Posts: 1 ✭
in Developer APIs

I had been testing a video-upload feature using the Cloudinary API for about 2-3 hours and took a break to make something to eat.

Now the uploads on my devices are returning a 401 "Invalid Signature" error.

I haven't touched the backend which fetches my valid signature and returns it to the client, and checking the Cloudinary Console shows the API Key and Secret Key are the same as they have been for months.

What's going on here? Is Cloudinary having some issue?

Tagged:

Comments

  • Tamara
    Tamara Member, Cloudinary Staff Posts: 124

    Hi @JordanUnitedForGood,

    Thanks for reaching out. 

    Looking at our logs, this is the error you have received:
    Invalid Signature c59359d0e929b970d03cd4eb85038d4071676396. String to sign - 'timestamp=1732744356'.

    Are you using another parameter in your upload call besides 'timestamp' as well? If the answer is yes, then that is why you are receiving this message - because we are only expecting to sign a timestamp. When you see 'String to sign', the value immediately following is exactly the value that we are expecting to receive. 

    If that didn't help - Can you please share your code here or in a private support ticket?

    I hope this helps. If you have any questions do not hesitate to ask.

    Kind Regards, 

    Tamara

Categories