When we make a request to the backend directly for example https://backend.com/api/v1/movies the request succeeds without any issues whereas https://frontend.com/api/v1/movies throws 500 error.
Is there a way to know what’s causing this issue?
Here are a few of the nf-request-ids for the failed requests
Hi, @bravokeyl. The 500 error in this case was because the SSL certificate using used on the proxied to service was invalid.
I’m now showing the same URL that returned a 500 status for an x-nf-request-id above is working now. Did you resolve the issue? If so, was the resolution to update the SSL certificate?
The 500 error, in this case, was because the SSL certificate using used on the proxied to service was invalid.
May I know what was the invalid ssl cert message? It should not be an issue because we were able to access the proxied service over https(https://backend.com/) by hitting it directly.
Did you resolve the issue? If so, was the resolution to update the SSL certificate?
We were trying to setup a WAF for that it is not working temporarily we disabled, but we need to resolve it.
It would be very helpful if we can identify the issue.
If our system cannot connect to the proxied resource for SSL or other reasons (anytime the connection itself fails), we will return a 500 status response for the request.
Again, it is working when I test it now, though. If there are other questions we are happy to answer.