-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 3.6.2
-
Component/s: Networking
-
None
-
Fully Compatible
-
ALL
-
v3.6
-
-
Platforms 2018-03-12
When accessing MongoDB over HTTP, it returns a simple HTTP response stating that it does not server HTTP:
It looks like you are trying to access MongoDB over HTTP on the native driver port.
This is a nice feature in order to check for principal MongoDB liveness, and we use it, for example, to check whether MongoDB has come up yet in automated experiments running in a Kubernetes cluster (https://github.com/timn/docker-robotics/blob/master/rcll-sim/scripts/run-component#L32).
This used to work with MongoDB 3.4, but does not work anymore with MongoDB 3.6 (using . The server log for each connection request contains something like this:
Error receiving request from client: SSLHandshakeFailed: SSLHandshakeFailed. Ending connection from 127.0.0.1:45380
This is done using the current mongo image from Docker hub.