404 on Login

Cadiducho

When some user try to login in the forum, an error is shown: The requested resource was not found.
The cool thing is that flarum actually logs in the user. When the user reload the page (by pressing F5, for example), the user has an active session in the forum and all works fine.
This is what i'm getting on chrome's console with debug mode enabled

(All the same when I login with username or an email, different API params, but the same 404)
Maybe the API fails because you are not yet fully logged in? I am really intrigued, and I cant fix this

I'm using nginx with the lastest config file provided. A few weeks ago I was using Caddy Server and I had the same problem in the login.

Here's my flarum info

Thank you

clarkwinkelmann

Cadiducho what action do you perform before seeing the error? The request causing an error appears to be the request that's made when you access a user's profile, not the one from login.

Have you set an email address as a username? Because that's appears to be what's happening, it's trying to load up a profile based on an email address. Since an email isn't a valid username in Flarum (can't use @ and . in usernames) this would be likely to end up in an error.

Cadiducho

clarkwinkelmann this is right after click Log In button (with keeps with the loading animation).
My username is "Cadiducho", and I have the same error if I use the username

Just to clarify: I actually can log in with my email or with my username, both "works" after the error shown and after I reload the page.

luceos

Disabling debug in your config.php should pop up a better error to the user, seems the user does not exist.

Cadiducho

luceos Unfortunately, it doesnt. I enabled debug because the error was longer, in order to find something

And yes, the user exists. This happens to all users.
I recorded a video just to show the behaviour of the page

Edit: I forgot to change the lang to English in the video. The error is the same that in the Image, The requested resource was not found.

clarkwinkelmann

Can you check the "Network" tab while you do it? Is there a request to /login or not? Does it happen before or after the /api/user/[...] error request?

I'm pretty sure that additional request must be made by an extension, but looking at your extension list I don't know which one it would be. Maybe you could try to disable some of the extensions to see if the issue goes away. If you are logged out of all admin accounts, you can manually disable some extensions by editing the enabled_extensions key in the settings table of the database. It's a JSON array containing the extension IDs to be enabled.

Cadiducho

clarkwinkelmann Yes, there is a POST to /login (and is 200 OK)
Right after that comes the GET to /api/user, the request that fails
(in fact, is Network tab says this request is queued and started AFTER /login request is complete, but I dont know if this is relevant or is always like that, maybe is just a race condition)

I'll check into the extensions, thanks for the idea

Cadiducho

Well, I disabled all the extensions and that wild request disappears. taking the opportunity, I updated the extensions and checking them one by one, enabling and logging in... and none failed.
The error just dissapears.
I don't know which extension cause the problem, but now seems to be fixed.

Thanks for all the support! 😄