#6609·lemmy

OAuthLoginFailed error

Author: NutomicCreated Jul 10, 2026Updated Aug 8, 2026
Labelsbug

A user reported this error when attempting to login via Github OAuth to voyager.lemmy.ml:

callback?code=3ed55281d78996fe5c2f&state=82f04f1d-37b2-42fd-b9ae-459081aa151a:9 [unlazy] Missing data-src or data-srcset attribute <img class=​"overflow-hidden pictrs-image object-fit-cover img-icon me-1" src=​"https:​/​/​voyager.lemmy.ml/​api/​v4/​image/​a32c32b6-c8c3-4d17-ab40-46c4ca518868.webp?max_size=96" alt title loading=​"lazy" width=​"96" height=​"96">​ (anonymous) @ callback?code=3ed55281d78996fe5c2f&state=82f04f1d-37b2-42fd-b9ae-459081aa151a:9 (anonymous) @ callback?code=3ed55281d78996fe5c2f&state=82f04f1d-37b2-42fd-b9ae-459081aa151a:9 requestAnimationFrame (anonymous) @ callback?code=3ed55281d78996fe5c2f&state=82f04f1d-37b2-42fd-b9ae-459081aa151a:9 (anonymous) @ callback?code=3ed55281d78996fe5c2f&state=82f04f1d-37b2-42fd-b9ae-459081aa151a:9 9046.client.js:2 Bad element for masonry: .post-listings-grid l @ 9046.client.js:2 i @ 9046.client.js:2 y @ client.js:2 await in y onLoad @ client.js:2 client.js:2 POST https://voyager.lemmy.ml/api/v4/oauth/authenticate 400 (Bad Request) wrapper @ client.js:2 authenticateWithOAuth @ client.js:2 doLogin @ client.js:2 componentDidMount @ client.js:2 (anonymous) @ client.js:2 u @ client.js:2 d @ client.js:2 await in d (anonymous) @ client.js:2 (anonymous) @ client.js:2 3585 @ client.js:2 n @ client.js:2 (anonymous) @ client.js:2 (anonymous) @ client.js:2 client.js:2 Request error while calling POST /oauth/authenticate with {“code”:“3ed55281d78996fe5c2f”,“oauth_provider_id”:1,“redirect_uri”:“https://voyager.lemmy.ml/oauth/callback”} wrapper @ client.js:2 await in wrapper authenticateWithOAuth @ client.js:2 doLogin @ client.js:2 componentDidMount @ client.js:2 (anonymous) @ client.js:2 u @ client.js:2 d @ client.js:2 await in d (anonymous) @ client.js:2 (anonymous) @ client.js:2 3585 @ client.js:2 n @ client.js:2 (anonymous) @ client.js:2 (anonymous) @ client.js:2
error “oauth_login_failed” cause “invalid type: null, expected a string”

I suspect that it comes from this line, which indicates that the user profile cannot be read properly.