Issues with Secure WebSockets on OpenShift Online
Environment
- OpenShift Online (OSO)
Issue
Our application is using secure websockets with 8443 port. But websocket doesn't connect using alias domain, in the other hand, the application is able to connect using port 8000 with no secure websockets.
# curl -I -N -H "Connection: Upgrade" -H "Upgrade: websocket" -H "Host: www.abc.com" https://www.abc.com:8443
curl: (51) Unable to communicate securely with peer: requested domain name does not match the server's certificate.
Resolution
The issue has been determined as a bug and being worked upon. Below is the link :
Root Cause
The proxy server is always using the *.rhcloud.com SSL certificate. It should use the custom certificate associated with application.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Comments