My instance is working for me and I can connect remotely, but I am stuck on where to set this parameter to false, because it claims that the default value is true:
failIndexKeyTooLong
Installing "failIndexKeyTooLong" is a three-step process:
You need to go to the command console in the "Tools" menu for the administrator database of your database instance. This command will only work in the admin database shown here:
After that, select any command from the list, and it will provide you with short JSON text for this command.
Remove the command they provide (I selected "ping") and enter the following JSON:
{ "setParameter" : 1, "failIndexKeyTooLong" : false }
Here is an example that will help:
Please note if you use a free plan in MongoLab: This will NOT work if you have a free plan; It only works with paid plans. If you have a free plan, you won’t even see the admin database. HOWEVER, I contacted MongoLab, and here is what they offer:
Hello,First of all, welcome to MongoLab. We will be happy to help.The failIndexKeyTooLong = false parameter is only necessary when your data includes indexed values that exceed the maximum key length of 1024 bytes. This only happens when Parse automatically indexes certain ones that may lead to incorrect query results. pars updated its migration guide to add a bit more information about this, here:https://parse.com/docs/server/guide#database-why-do-i-need-to-set-failindexkeytoolong-false-Most likely, your migration will be successful without this setting. Could you ask? If for some reason this does not work, let us know and we can help you in the next steps.Our dedicated and collective plans ( https://mongolab.com/plans/pricing/ ) provide the ability to switch this option, but since our free Sandbox plans work on shared server processes with other Sandbox users, this setting is not configurable.
Hello,
First of all, welcome to MongoLab. We will be happy to help.
The failIndexKeyTooLong = false parameter is only necessary when your data includes indexed values that exceed the maximum key length of 1024 bytes. This only happens when Parse automatically indexes certain ones that may lead to incorrect query results. pars updated its migration guide to add a bit more information about this, here:
https://parse.com/docs/server/guide#database-why-do-i-need-to-set-failindexkeytoolong-false-
Most likely, your migration will be successful without this setting. Could you ask? If for some reason this does not work, let us know and we can help you in the next steps.
Our dedicated and collective plans ( https://mongolab.com/plans/pricing/ ) provide the ability to switch this option, but since our free Sandbox plans work on shared server processes with other Sandbox users, this setting is not configurable.
When you start your mongodb server, you can set this parameter to false:
mongod --setParameter failIndexKeyTooLong=false
I wrote an article that will help you configure Parse-Server and all its dependencies on your own server: https://medium.com/@jcminarro/run-parse-server-on-your-own-server-using-digitalocean-b2a7d66e1205