Skip to main content

Invalid Signature 1d6be727cf981f67fae5999c46ad4ee599fb3333. String to sign - 'timestamp=1670597257'."

Comments

4 comments

  • Tia Esguerra

    Hi there, 

    Thanks for reaching out. 

    Are you using the folder parameter in your upload call as well? If not, 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. 


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

    Kind Regards, 

    Tia

    1
  • msi.shiblee msi.shiblee

    Hi Tia,

    Thanks for your help. It worked.

    regards
    Saidul

     

    0
  • Tia Esguerra

    Hello Saidul,

    You are very welcome. I'm glad it's working now. If you need anything in the future, do not hesitate to reach out. 

    Kind Regards, 

    Tia

    0
  • verhoeven.pascal verhoeven.pascal

    never mind, sorted it out!

    recreated the .env folder and entered the variables again (before the API key numerical kept appearing in a color and when i saved .env it would jump out with spaces around =. Now i recreated it the text stays flat as i entered it, not sure if important or not)

     

     

    just in case it can help others

     

     

    Hi there, 

    getting a same issue here: 

    Invalid Signature 4245b132f09227fbf44f901693deafe0006372a2. String to sign - 'folder=lmis_lao&timestamp=1672728530'.

    const cloudinary = require('cloudinary').v2;
    const { CloudinaryStorage } = require('multer-storage-cloudinary');
    cloudinary.config({
    cloud_name:process.env.CLOUDINARY_CLOUD_NAME,
    api_key:process.env.CLOUDINARY_KEY,
    api_secret:process.env.CLOUDINARY_SECRET
    });
    const storage = new CloudinaryStorage({
    cloudinary,
    params:{
    folder:'lmis_lao',
    allowedFormats: ['jpeg','png','jpg']
    }
    });
    module.exports = {
    cloudinary,
    storage
    }

    got my .env folder in the right place  and 

    if (process.env.NODE_ENV !== "production") {
    require('dotenv').config();
    }
    added
    on top of the app.js
    not sure what else could be wrong....
    but keep getting the invalid signature message with no console out put.
    Is there a something that you see missing? thanks in advance!!
     

     

    0

Post is closed for comments.