@fevzikorkutata I don't understand what you're saying.
That fix is in 1.17.0 so you shouldn't have run into that issue if you went straight from 1.0.3 to 1.17.0 as I recommended.
Run the update process and this is the error that I get in the logs:
10/12 09:39  - info: [database] Checking database indices done! 10/12 09:39  - error: MongoError: Index with name: _key_1_value_-1 already exists with different options at Function.MongoError.create (/opt/gamrhaus-1.0/node_modules/mongodb-core/lib/error.js:31:11) at /opt/gamrhaus-1.0/node_modules/mongodb-core/lib/connection/pool.js:462:72 at authenticateStragglers (/opt/gamrhaus-1.0/node_modules/mongodb-core/lib/connection/pool.js:410:16) at Connection.messageHandler (/opt/gamrhaus-1.0/node_modules/mongodb-core/lib/connection/pool.js:444:5) [cluster] Child Process (22179) has exited (code: 0, signal: null) at Socket.<anonymous> (/opt/gamrhaus-1.0/node_modules/mongodb-core/lib/connection/connection.js:306:22) at emitOne (events.js:96:13) at Socket.emit (events.js:188:7) at readableAddChunk (_stream_readable.js:176:18) at Socket.Readable.push (_stream_readable.js:134:10) at TCP.onread (net.js:548:20)
It is relates to key_1_value-1 already exists issue
The 1.4.1 update seems to have fixed the issue for me. More testing this evening. Thanks.