# Null Login Bug? Last Couple Betas

**URL:** <https://meta.discourse.org/t/null-login-bug-last-couple-betas/99428>\
**Category:** Bug\
**Created:** [13.Октябрь.2018 12:52:12 UTC](https://meta.discourse.org/t/null-login-bug-last-couple-betas/99428 "2018-10-13T12:52:12Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![yyhmsg](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/yyhmsg/32/115542_2.png) [@yyhmsg](https://meta.discourse.org/u/yyhmsg)\
**Post date:** [13.Октябрь.2018 12:52:12 UTC](https://meta.discourse.org/t/null-login-bug-last-couple-betas/99428/1 "2018-10-13T12:52:12Z")

</div>

I believe this started the last couple beta downloads, but now after logging in “null” is added to the login which takes you to a 404.

To reproduce:  
Login via any mechanism (I’ve tried both facebook and regular user login)  
Logout  
Login again and you will get loginmethod/null (previous beta it was no slash just loginmethodnull) - such as:  
[https://community.yinyanghouse.com/auth/facebook/null](https://community.yinyanghouse.com/auth/facebook/null)

You are actually logged in and everything works fine once you get away from the Oops not found page…

I’m assuming this is some sort of redirect that isn’t happening correctly, but just thought I would report…

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [15.Октябрь.2018 01:11:06 UTC](https://meta.discourse.org/t/null-login-bug-last-couple-betas/99428/2 "2018-10-15T01:11:06Z")

</div>

Can you reproduce this on meta?

---

<div class="post-metadata">

**Author:** ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)\
**Post date:** [15.Октябрь.2018 01:16:28 UTC](https://meta.discourse.org/t/null-login-bug-last-couple-betas/99428/3 "2018-10-15T01:16:28Z")

</div>

I hit this on try earlier today with Google. I was having some internet blips though, so I assumed it was that. ~~Will see if I can repro.~~

Yep, consistent repro on try (can’t test here on Meta due to 2FA). I hit [https://try.discourse.org/auth/google\_oauth2/null](https://try.discourse.org/auth/google_oauth2/null) after clicking “Log in”, then “Google”, then selecting my account. Login is successful, loading [https://try.discourse.org/](https://try.discourse.org/) directly after hitting the null page works.

---

<div class="post-metadata">

**Author:** ![yyhmsg](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/yyhmsg/32/115542_2.png) [@yyhmsg](https://meta.discourse.org/u/yyhmsg)\
**Post date:** [15.Октябрь.2018 01:25:28 UTC](https://meta.discourse.org/t/null-login-bug-last-couple-betas/99428/4 "2018-10-15T01:25:28Z")

</div>

I can’t seem to experience it on meta (but there I use my github account if that matters) - I can seem to get it everytime on my site [https://community.yinyanghouse.com/](https://community.yinyanghouse.com/) - at least with regular login and facebook…

Glad that someone else saw the error as well…

---

<div class="post-metadata">

**Author:** ![przlde](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/przlde/32/76987_2.png) [@przlde](https://meta.discourse.org/u/przlde)\
**Post date:** [15.Октябрь.2018 20:12:59 UTC](https://meta.discourse.org/t/null-login-bug-last-couple-betas/99428/5 "2018-10-15T20:12:59Z")

</div>

Yes, it’s problem with that. When I login to my account (I used only login and password) i see result: [http://mywebsite.com](http://mywebsite.com) **null**

 ![image](https://global.discourse-cdn.com/meta/original/3X/b/6/b6613386635fd470ad528d11b35c7a105b09b73b.png)

---

<div class="post-metadata">

**Author:** ![pmusaraj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pmusaraj/32/119489_2.png) [@pmusaraj](https://meta.discourse.org/u/pmusaraj)\
**Post date:** [15.Октябрь.2018 22:03:53 UTC](https://meta.discourse.org/t/null-login-bug-last-couple-betas/99428/6 "2018-10-15T22:03:53Z")

</div>

I can also reproduce this on [try.discourse.org](http://try.discourse.org) using GitHub login. FWIW, I couldn’t reproduce it using a regular signup/login.

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [15.Октябрь.2018 22:52:38 UTC](https://meta.discourse.org/t/null-login-bug-last-couple-betas/99428/7 "2018-10-15T22:52:38Z")

</div>

@vinothkannans can you have an attempt to repro? I recall you recently changed some of the redirect back logic in the context of sso, maybe this is related

---

<div class="post-metadata">

**Author:** ![vinothkannans](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vinothkannans/32/86465_2.png) [@vinothkannans](https://meta.discourse.org/u/vinothkannans)\
**Post date:** [16.Октябрь.2018 01:49:23 UTC](https://meta.discourse.org/t/null-login-bug-last-couple-betas/99428/10 "2018-10-16T01:49:23Z")

</div>

It’s fixed as per below commit. Clear the cookies and test the social login flow. It shouldn’t redirect back to the null URL again.

[https://github.com/discourse/discourse/commit/08c404e138c5dfbb6e82ac7f6e54976d30b4530a](https://github.com/discourse/discourse/commit/08c404e138c5dfbb6e82ac7f6e54976d30b4530a)

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [29.Декабрь.2018 09:36:31 UTC](https://meta.discourse.org/t/null-login-bug-last-couple-betas/99428/12 "2018-12-29T09:36:31Z")

</div>


