Login Request always forbidden.
-
Due to unknown reasons, my Nodebb instance always returns an invalid csrf token when trying to access it, and when attempting to register, it always shows that the name is already taken even though there are no duplicate names.
There's no suspicious logs so I can only provide this information, are there any possibly effective fixes? -
Due to unknown reasons, my Nodebb instance always returns an invalid csrf token when trying to access it, and when attempting to register, it always shows that the name is already taken even though there are no duplicate names.
There's no suspicious logs so I can only provide this information, are there any possibly effective fixes?{
"url": "http://xxx.xxx.xx",
"secret": "16af4904-abb5-4d7d-95ba-593cb6563e7a",
"database": "mongo",
"mongo": {
"host": "127.0.0.1",
"port": 27017,
"username": "",
"password": "",
"database": "nodebb",
"uri": "xxx"
},
"port": 4567,
"bind_address": "0.0.0.0",
"debug": true
} -
Due to unknown reasons, my Nodebb instance always returns an invalid csrf token when trying to access it, and when attempting to register, it always shows that the name is already taken even though there are no duplicate names.
There's no suspicious logs so I can only provide this information, are there any possibly effective fixes?Additionally, when one person is temporarily banned for trying the password too many times, everyone will be banned together which is strange.
-
Due to unknown reasons, my Nodebb instance always returns an invalid csrf token when trying to access it, and when attempting to register, it always shows that the name is already taken even though there are no duplicate names.
There's no suspicious logs so I can only provide this information, are there any possibly effective fixes?The csrf error is usually caused by wrong url in your config.json, make sure it is the same as the address you are accessing the forum. Your other issues are likely caused by something else.
-
Due to unknown reasons, my Nodebb instance always returns an invalid csrf token when trying to access it, and when attempting to register, it always shows that the name is already taken even though there are no duplicate names.
There's no suspicious logs so I can only provide this information, are there any possibly effective fixes?I don't think url cause this issue.
-
I don't think url cause this issue.
M1hono also check that cookieDomain is not set to anything in ACP
Can you share your nginx config?
-
Due to unknown reasons, my Nodebb instance always returns an invalid csrf token when trying to access it, and when attempting to register, it always shows that the name is already taken even though there are no duplicate names.
There's no suspicious logs so I can only provide this information, are there any possibly effective fixes?I restart the whole project and it's fine for now. I might asume it's related to the mismatching between database and nodebb secret.
-
Due to unknown reasons, my Nodebb instance always returns an invalid csrf token when trying to access it, and when attempting to register, it always shows that the name is already taken even though there are no duplicate names.
There's no suspicious logs so I can only provide this information, are there any possibly effective fixes?This seems to be caused by the slug, as my community is a non-English speaking community, and the current slug generates very cumbersome links, so I tried modifying slug.js, and then encountered similar issues.
I reproduce the issue and I think it might be the final answer lol.
-
Due to unknown reasons, my Nodebb instance always returns an invalid csrf token when trying to access it, and when attempting to register, it always shows that the name is already taken even though there are no duplicate names.
There's no suspicious logs so I can only provide this information, are there any possibly effective fixes?Is there any way of chaging the slug in a normal waIs there any way of chaging the slug in a normal way?
-
Due to unknown reasons, my Nodebb instance always returns an invalid csrf token when trying to access it, and when attempting to register, it always shows that the name is already taken even though there are no duplicate names.
There's no suspicious logs so I can only provide this information, are there any possibly effective fixes?I also faced the same.
-
Due to unknown reasons, my Nodebb instance always returns an invalid csrf token when trying to access it, and when attempting to register, it always shows that the name is already taken even though there are no duplicate names.
There's no suspicious logs so I can only provide this information, are there any possibly effective fixes?I've found a plugin that solved it.
