No, but the problem did not occur as long as I called the api directly from the IP adress.
As soon as I added a DNS entry on netlify DNS and routed to the IP it causes HTTP 500s.
I’m assuming that the problem is somewhere between netlify and my loadbalancer.
Because direct call to api3.bobits.at/api/v1/company works as expected, but reverse proxying gastserviceapp.bobits.at/api/v1/company doesn’t work.
Maybe some additional headers need to be set, I don’t know.
Meanwhile I’ve changed my DNS records.
I’ve added the dns record for api3.bobits.at again, pointing to my server (not netlify).
Although, when I try to open the reverse proxy redirected endpoint: https://myregi.netlify.app/api/v1/company which in fact should go to api3.bobits.at, I get an HTTP 500.
I’ve following redirects defined in my repo:
This causes any error on the proxied request and a 500 response is returned because of this. If the SSL certificate used is updated to correct the errors reported by SSL Labs, the 500 errors should stop.
I see. So it’s not possible to host bobits.at from netlify, and a subdomain like api3.bobits.at from another server, providing its own let’s encrypt certificate, because then there will be two certificates, which causes problems.
api3.bobits.at and the wildcard certificate *.bobits.at
Is there any workaround or other solution, except using another domain?
Hi, @bobocu. An incomplete certificate chain in the SSL certificate at api3.bobits.at is the cause. The issue is not that there are two certificates. If you fix the certificate chain, the proxying will work.
The screenshot below highlights the issue on the SSL Labs analysis:
That is the issue which must be resolved to fix the 500 response when proxying to that site with our service. Our proxy service won’t look up the missing certificate in the chain and will return an error instead. If you fix the chain, the proxying will succeed.
If there are other questions about this, please let us know.