I'm facing an issue while trying to set up a proxy from Apache to a Kubernetes service and I'm getting an SSL handshake error. Here's my Apache configuration for HTTPS: I have the necessary SSL settings, including the certificate and key files. The backend service in Kubernetes is defined in the ingress, but whenever I hit the proxy, it fails with error messages indicating that the SSL handshake was unsuccessful. Here's a snippet of the error log: "SSL Proxy connect failed" and others indicating connection issues. Could someone help me troubleshoot this?
2 Answers
You're right about the potential for collisions. Ingress rules in Kubernetes can manage different paths, so ensure each service has its own unique path. You can actually have numerous hosts using the same hostname but with distinct paths. Also, remember to review your ingress controller configurations thoroughly—testing with `nginx -T` in your controller pod might give you insights into what’s going wrong. From what you've described, you might not even need Apache for this.
You might be over-complicating things by trying to proxy a proxy. It's generally cleaner to avoid this setup if possible. Also, keep in mind that different applications sharing the same production URL could cause path collisions. Make sure your pathing is unique between services to prevent issues. Check if using different paths can help you avoid this problem altogether.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures