<p>This happened for me when I had the LastPass browser plugin version 3.3.1. Once I upgraded to 4.1.29, the issue went away.</p>

CC BY-SA 3.0
2016-10-19T19:36:15.240Z
Now that you say it, that's the same here! :)
Coen van der Kolk
CC BY-SA 3.0
2016-10-19T19:34:18.133Z
2016-10-19T19:34:18.133Z
Andrew
<p>After logging in to the Craft admin area I sometimes(!) get routed to <code>/admin/undefined</code> instead of <code>/admin/dashboard</code>. </p>

<p>Anyone knows were to start looking to solve this issue?</p>

CC BY-SA 3.0
2016-05-19T18:53:01.990Z
That's... odd.  Do you have any Craft plugins installed? Does it happen across multiple browsers?
Brad Bell
CC BY-SA 3.0
2016-05-22T13:31:33.947Z
Hi Brad,
I already tried to disable and remove all plugins, but that didn't made any difference. Neighter does changing browsers. Right now I've 'solved' the issue by making a redirect in the vhost to push all undefined to dashboard.
Coen van der Kolk
CC BY-SA 3.0
2016-05-22T21:25:10.270Z
Super-strange. Never heard of that behavior before.
Brad Bell
<login>
Sometimes getting sent to /admin/undefined after login
# Sometimes getting sent to /admin/undefined after login

(Asked by: username_0 on 2016-05-19)

After logging in to the Craft admin area I sometimes(!) get routed to `/admin/undefined` instead of `/admin/dashboard`.

Anyone knows were to start looking to solve this issue?

**Tags:** login
> **Comments:**
> **username_1**: That's... odd.  Do you have any Craft plugins installed? Does it happen across multiple browsers?  
> **username_0**: Hi Brad, I already tried to disable and remove all plugins, but that didn't made any difference. Neighter does changing browsers. Right now I've 'solved' the issue by making a redirect in the vhost to push all undefined to dashboard.  
> **username_1**: Super-strange. Never heard of that behavior before.  

---

## 1 answers

### Answer by username_2 on 2016-10-19. Score: 3 | Accepted answer

This happened for me when I had the LastPass browser plugin version 3.3.1. Once I upgraded to 4.1.29, the issue went away.

> **Comments:**
> **username_0**: Now that you say it, that's the same here! :)  

---

