Was working fine, but now get a 400 error -- hard to triage

Question

Was working fine, but now get a 400 error -- hard to triage

Closed this issue 6 months ago · 3 comments

https://zight.fong888.com/jkupQpWr

I get a 400 error, but I don't know how to address it.

Answer 1 · 2024-05-21T20:27:22.000Z

Hi @timfong888 , 400 usually means the request to Cloudinary was improperly formatted. I can't reproduce your error. Can you send a screenshot of what the plugin settings look like? Feel free to blur out your cloud name / template name.

These need to be set correctly for the call to succeed. Have you validated that these values match exactly with what is defined in your Cloudinary account?

Thanks

Answer 2 · 2024-06-01T10:35:50.000Z

Closing. No activity

Answer 3 · 2024-06-04T00:53:42.000Z

Thanks for responding. As far as I know I haven’t changed the settings. I just resynced and then I went back to check the settings. I will take another look. Thanks. Inline image Tim Fong p: 415-508-6888 e: ***@***.***

…

On Tue, May 21, 2024 at 1:27 PM Jordan Handy ***@***.***> wrote: Hi @timfong888 <https://github.com/timfong888> , 400 usually means the request to Cloudinary was improperly formatted. I can't reproduce your error. Can you send a screenshot of what the plugin settings look like? Feel free to blur out your cloud name / template name. These need to be set correctly for the call to succeed. Have you validated that these values match exactly with what is defined in your Cloudinary account? Thanks — Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAADNZZYCCEWUPRGASJJMGLZDOU4BAVCNFSM6AAAAABH5YLMT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRTGM4DOMJWGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>