Hey @riggsba,
This is most likely an issue with the Cloud Name<=>API Key combination provided in the plugin’s credentials.
Can you please share you Cloud Name with me, so I can find the request in our logs and provide you with more details?
Thanks,
Raz
Thanks for the additional information @riggsba.
Upon checking our logs, I can see requests to our API coming from your site https://brunoriggs.com.br, which use you API Key and Secret, but with incorrect cloud name – dvmvbjfsx. Are you familiar with this cloud name? Any idea why the requests are made with this cloud although API Key and Secret are associated with the brunoriggs cloud?
Can you please navigate your plugin’s Connect page and check what are credentials within the environmental variable? If you see the incorrect cloud name is used there, then change it to the correct one, then try again.
Let me know if that solved the issue for you?
Best,
Raz
the URL is right, API_KEY:API_SECRET@brunoriggs.
I migrated the server site yesterday, could this be the cause?
Hey @riggsba,
Can you please open a support ticket at support@cloudinary.com so we can proceed with helping you in the debugging process where you can share some additional details about your environment over a private channel?
Thanks,
Raz
Raz, the Cloudnary team guided me. I copied and the data as a guide and it is showing the same error. Is there a database table or configuration file that we can reset?
