503 Error using Heroku
Hi, I keep receving 503 errors whenever I try to upload images with the heroku website. We are using nodejs, multer, and express over on the server side to handle the form data with an image that is uploaded by the user. This is all working perfectly using the localhost. When we ported everything over to the Heroku side and installed the cloudinary add-on, replaced the temp cloudinary IDs to match the heroku add-on, we even changed our code to match the code in the documentation:
we went from ``` cloudImage.url = req.file.url; cloudImage.id = req.file.public_id;``` to ```
We are stuck and don't know what to do. Our class project is due Saturday, and this is the last step we need. What are the causes of a 503? Any information helps. Thank you in advance!
-
Hi,
Thanks for your message.
I can see you've raised this issue via Zendesk and have followed-up there, and to keep things organised, I'll merge the two requests.
Could you please follow the Zedensk ticket for updates on this.
Best regards,
Aleksandar
0 -
hi
please can you point me to this solution?
having the same issue
0 -
Hi Lekan,
This issue previously was caused since the CLOUDINARY_URL environment variable was not set. May I please ask you to check that you have defined this environment variable either directly or through the Heroku config?
You can set the CLOUDINARY_URL (can be copied from the Dashboard after logging into your account) as an environment variable or using the Heroku config to declare it. https://devcenter.heroku.com/articles/config-vars#using-the-heroku-cli
0 -
well i am also facing the same problem ..
You can set the CLOUDINARY_URL (can be copied from the Dashboard after logging into your account) as an environment variable or using the Heroku config to declare it.
i have done this step as well.still it doesnt upload any image there ..and it shows status of 500
at=info method=POST path="/campgrounds" host=arctic-mountie-55057.herokuapp.com request_id=a5dfc5da-c043-40fe-ac92-fd3c196edd0f fwd="49.36.188.116" dyno=web.1 connect=1ms service=251ms status=500 bytes=4798 protocol=https
0 -
Hi @Divansh,
Based on the line at the bottom of your message, it appears the 500 server error is returned in response to a POST request to your site's '/campgrounds' endpoint and not directly returned by Cloudinary.
Are you able to share the full stack trace from your server's logs which would reveal what specifically lead to the error?
In addition, could you please share more details as to what your code does when a POST request is sent to /campgrounds and how you are utilising Cloudinary in that part of the code?
If you would like to share those details directly with us, rather than here in the Forums, then please raise a ticket with us via - https://support.cloudinary.com/hc/en-us/requests/new
0
Post is closed for comments.
Comments
5 comments