Failure signing up
-
wrote on Oct 2, 2024, 3:06 PM last edited by
Whenever I try to sign up, I keep getting the error below.
I tried setting it up with and without OAuth support without success. When I do use the OAuth login option, I get another error complaining that the OAuth login failed (right when I press the button). Any ideas?
Invalid or missing XSRF token. Please reload the page and try again.
(CSRF token invalid){ "headers": { "normalizedNames": {}, "lazyUpdate": null }, "status": 403, "statusText": "OK", "url": "https://comments.somesite.com/api/auth/profile", "ok": false, "name": "HttpErrorResponse", "message": "Http failure response for https://comments.somesite.com/api/auth/profile: 403 OK", "error": { "id": "xsrf-token-invalid", "message": "XSRF token is missing or invalid", "details": "CSRF token invalid" } }
-
@Locutus I just tried this now with and without oauth and both work fine. Can you check if you can reproduce this on our demo instance ? https://my.demo.cloudron.io (username & password is 'cloudron')
-
wrote on Oct 4, 2024, 9:08 AM last edited by
I just realized what the problem was. I'm not sure if it can be fixed here or upstream.
I had PIxelfed installed on my root domain (While Comentario was installed on a subdomain in the same domain). Once I removed the cookies for Pixelfed, it started working again.
-
I just realized what the problem was. I'm not sure if it can be fixed here or upstream.
I had PIxelfed installed on my root domain (While Comentario was installed on a subdomain in the same domain). Once I removed the cookies for Pixelfed, it started working again.
-
wrote on Oct 4, 2024, 9:12 AM last edited by
Same problem. When I try to login to Pixelfed first, Comentario gives the same error.
-
@Locutus there goes my "pretty sure" ....
I can't quite make out what is the relation between pixelfed on root domain and comentario on subdomain. Do you think this is because of some issue in localstorage/browser side? What happens when you try another browser?
-
wrote on Oct 4, 2024, 9:31 AM last edited by
I'll wait for them to merge the fix then. Thanks.