-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.6.0-rc0
-
Component/s: Networking, Security
This is the message when you connect using a client without ssl to a server that requires SSL:
MongoDB shell version: 2.6.0-rc0 connecting to: test 2014-02-28T20:25:27.549+0000 Socket recv() errno:10054 An existing connection was forcibly closed by the remote host. 127.0.0.1:27 017 2014-02-28T20:25:27.550+0000 SocketException: remote: 127.0.0.1:27017 error: 9001 socket exception [RECV_ERROR] server [127.0.0.1: 27017] 2014-02-28T20:25:27.550+0000 DBClientCursor::init call() failed 2014-02-28T20:25:27.551+0000 Error: DBClientBase::findN: transport error: 127.0.0.1:27017 ns: admin.$cmd query: { whatsmyuri: 1 } at src/mongo/shell/mongo.js:146 exception: connect failed
The server logs have great messaging here but the client's message tells me absolutely nothing about SSL being the problem.
- duplicates
-
SERVER-11292 Connecting to ssl-encrypted mongod with non-ssl mongo shell generates confusing error
- Backlog