500 Error returned from proxy to Heroku API

Support
1

Hi everyone, I’m currently facing the same issue here.
When I try making a post request to an API endpoint I get a 500 server error, but If I use the API locally on my PC, it works perfectly. Please what could be the issue?

Screenshot from 2022-01-03 17-27-48
Screenshot from 2022-01-03 17-27-481920×1053 246 KB

This is a screenshot of my netlify.toml config

Screenshot from 2022-01-03 17-36-14
Screenshot from 2022-01-03 17-36-141044×823 108 KB

2

Hi @Ayomi

Welcome to the forums

You have a wildcard in the from of the redirect, but you are not using a :splat.

Does it work if you change the redirect to

[[redirects]]
  from = "/v1/*"
  to = "https://gamp-server-staging.herokuapp.com/v1/:splat"
  status = 200
  force = true
  headers = {X-From = "Netlify"}
1 Like
3

Yeah, I tried doing this.
It’s still gives me the same error

4

Can you share the URL to a live site to look at?

5

Yeah, sure.
This is the link:- https://heuristic-liskov-2971b8.netlify.app

6

I’m trying to login to the application using an API endpoint

7

If you remove the proxy and use the herokuapp.com URL directly in the code deployed to Netlify, does everything work as intended?

8

Yeah, locally, it works.
But if I deployed it to netlify and test it, it gives this “CORS” error.

9

I suspect the CORS issue may still have an impact when used via the proxy method. Suggest settings up CORS headers. See here and here for CORS information, and custom headers in Netlify’s documentation.

1 Like
10

Thank you! @coelmay
Apparently, there was a CORS rule on the API itself. I have reported it.

1 Like