I'm trying to set up a reverse proxy using Apache to forward requests to my Kubernetes services, but I'm running into SSL handshake errors. Here's the configuration I'm working with:
In my Apache config, I'm utilizing SSL with a proxy-pass setup directed towards an internal service in Kubernetes. When I attempt to access the proxy, I get the following SSL handshake error messages in the logs:
- pass request body failed to internal.prod.dc
- SSL Proxy connect failed
- SSL handshake failed: sending 502
Can anyone provide insight into what's going wrong or how I might resolve this? Any help on debugging this issue would be greatly appreciated!
2 Answers
The key issue might be that your production URL is shared among multiple applications, leading to potential request collisions. Instead of having multiple namespaces use the same root path, try configuring unique paths or even separate hostnames for each application to isolate the traffic better.
It seems like you're trying to proxy a proxy, which can introduce unnecessary complexity. Maybe simplifying your approach could help? Also, consider checking the server name configurations and ensure SSL certificates align properly across the services. Sometimes these errors can stem from hostname mismatches or certificate issues.
Yeah, using different paths for your services can definitely help avoid conflicts. Check what your actual traffic looks like and see if simplifying the structure might resolve the handshake issue.