Changing spam lockout settings

Using Ghost
1

Does anyone know if the spam settings for config.production.json have changed? I can’t change them via adding this snippet. It throws a json error despite it being valid json, which makes me think it’s actually that the spam lockout parameters are no longer accepted. Or is that they must be in default. .json? Various places are unclear about this.

"spam": {
    "user_login": {
        "minWait": 600000,
        "maxWait": 604800000,
        "freeRetries": 4
    },
    "user_reset": {
        "minWait": 3600000,
        "maxWait": 3600000,
        "lifetime": 3600,
        "freeRetries": 4
    },
    "global_reset": {
        "minWait": 3600000,
        "maxWait": 3600000,
        "lifetime": 3600,
        "freeRetries":4
    },
    "global_block": {
        "minWait": 3600000,
        "maxWait": 3600000,
        "lifetime": 3600,
        "freeRetries":99
    },
    "private_block": {
        "minWait": 3600000,
        "maxWait": 3600000,
        "lifetime": 3600,
        "freeRetries":99
    },
    "content_api_key": {
        "minWait": 3600000,
        "maxWait": 86400000,
        "lifetime": 3600,
        "freeRetries": 99
    }
}
2

If the error is saying invalid JSON, you probably have a syntax error in your config.production.json. Can you try running the entire file (not just the snippet) through a JSON validator?

3

Yes, I tried that, and it passed as valid, which is what made it so strange.

4

Can you share the exact error?