Back to Nevada Unemployment

Ava Kim

Unemployment forgot password user not found - Nevada DETR login nightmare

Okay so I'm losing my mind a little bit here. Lost my job at a hotel property three weeks ago after they cut my whole department, went to file on the Nevada DETR CSS portal like I was told to, and hit a wall immediately. First I couldn't remember my password from the last time I filed maybe two years ago, so I went through the reset flow. Entered my email, got the link, clicked it, made a new password - and then when I tried to log in it just said 'user not found.' Not wrong password. Not account locked. Just... user not found. Like I don't exist. I tried my work email, my personal email, two different browsers, cleared everything. Same result every single time. I have no idea if my old account is gone, if I need to create a brand new one, or if there's something broken in the system. Can't file my initial claim, can't do anything. Has anyone hit this exact combination of problems before - the forgot password loop that just dumps you into user not found? What actually fixed it?

Two separate things could be happening here and they look identical on screen but need different fixes. The 'user not found' message after a successful password reset usually means the email you reset with is NOT the one attached to your Nevada DETR CSS account. The system lets you request a reset link to any email but only actually processes it if that email matches a registered account. So your reset 'worked' on an email with no account behind it. Try every email address you've ever used - old jobs sometimes register you under a work email without you realizing.

0 coins

Ava Kim

Author

Which part of the CSS login page shows what email the account is under? I don't see any lookup tool.

0 coins

There isn't one publicly visible, unfortunately. If you can't guess the right email after trying all of them, you'd need to contact Nevada DETR directly to have them look up your account by SSN and tell you which email is on file. That's the only path forward without guessing.

0 coins

same exact thing bit me, turned out my account was under a yahoo address i hadnt checked in like 4 years lol

0 coins

Before calling or creating a new account, one more thing worth trying: the CSS portal at nui.nv.gov sometimes has a username field, not just email. Some older accounts were created with a separate username that isn't your email at all. At the login screen, try entering just your first initial + last name or some variation you might have used years ago instead of your email address.

0 coins

Ava Kim

Author

Are you saying the username field accepts something totally different from the email field, like they're two separate login paths?

0 coins

Exactly right - older Nevada DETR CSS accounts predating a certain system update had alphanumeric usernames. If your account is old enough, the email reset flow won't help at all because email isn't the actual login credential. The username is. And there's no password reset path for those old usernames through the portal - you'd have to call.

0 coins

didnt know this was even a thing, explains why my mom couldnt get in after trying resets for a week

0 coins

Calling Nevada DETR to sort out a login issue sounds simple until you've spent three hours hitting busy signals and getting disconnected. For getting an actual agent on the line without that nightmare, Claimyr worked for me when nothing else did. You go to claimyr.com, there's also a video showing how it works at https://youtu.be/Mc9FNfOF_yY - basically it handles the hold queue for you and calls you back when an agent is ready. Saved me probably four hours of redial attempts when I had an account access problem. For something like this where you literally can't file until it's resolved, getting to an agent fast actually matters.

0 coins

Ava Kim

Author

Does it work specifically for the CSS technical support line or just the main claims line?

0 coins

Main claims line is what I used it for, and the agent there was able to transfer me to someone who handled the account issue. Might not be the dedicated tech line but you can get routed once you're talking to a human.

0 coins

gonna look into this, been trying to reach them about a different issue for two days straight

0 coins

Ask them this when you do reach someone: 'Can you tell me if there's an existing CSS account tied to my Social Security number, and if so, what login credential it uses?' That question gets you past the 'try resetting your password' script they give everyone. The reason to ask it that way is agents have access to the backend account lookup by SSN - they don't need your email to find you. Once they confirm an account exists they can flag it for a manual credential reset, which is different from the self-service reset that keeps failing you.

0 coins

Ava Kim

Author

What happens if they find an account under my SSN but I never created it - could someone else have opened one?

0 coins

That's worth raising with the agent directly. Identity-linked account conflicts do happen, more often in cases where someone else filed under your SSN at some point. The agent would escalate that to a different team. But in most cases it just turns out to be your own old account under a forgotten email or username.

0 coins

Good framing. The specific SSN lookup question bypasses like ten minutes of scripted troubleshooting steps.

0 coins

i went through this same thing two months ago and it turned out i had TWO accounts somehow, one from like 2019 and one i accidentally created when i thought i didn't have one. the system flagged me for duplicate accounts and that's why everything was broken. detr had to merge them on their end and it took about a week but then everything worked fine after

0 coins

Ava Kim

Author

How did you find out about the duplicate - did they tell you or did you figure it out?

0 coins

agent told me when i called. i never would have known otherwise. she said it happens more than people think

0 coins

This actually makes sense, their system apparently doesn't stop you from creating a second account if you use a different email

0 coins

Worth knowing: if the account turns out to be completely unrecoverable or if it was an old account from before Nevada moved everything to the current CSS platform, you may be better off just creating a fresh account. Your claim history is stored separately from your login credentials on the backend, so a new login won't erase your past UI history. The new account just gives you a fresh way in. That said, don't create a new account until you've confirmed with an agent that your old one is dead - duplicate accounts cause more problems than they solve.

0 coins

Ava Kim

Author

If I create a new account, does the new one automatically pull in my wage history from previous employers or do I have to enter everything again?

0 coins

Wage history comes from employer records filed with Nevada - it's not stored in your CSS account itself. When you file a new initial claim through a fresh account the system pulls wages from the state database, not from your old login. So that part is fine.

0 coins

Didn't realize account and claim data were stored separately. That's actually useful to know.

0 coins

Confirmed this is accurate. The CSS account is essentially just a portal login - the actual claim and wage data lives in DETR's separate records system.

0 coins

THE WHOLE LOGIN SYSTEM IS BROKEN AND HAS BEEN FOR MONTHS. I know three people who hit the user not found error and every single one of them got different explanations from different agents. One was told create new account, one was told wait for IT to fix it, one was told it was her fault for using Chrome. This is a systemic problem they're not acknowledging and it's costing real people their ability to file. Meanwhile the bills don't stop.

0 coins

Ava Kim

Author

Did any of the three people you know actually get it resolved eventually?

0 coins

Two of them yes, one is still waiting and it's been 6 weeks. The two who got it fixed both ended up calling multiple times before getting an agent who actually knew what to do. It's luck of the draw who picks up.

0 coins

six weeks is insane. that should not be a thing that happens

0 coins

Something most guides skip: the nui.nv.gov site has a separate 'Create Account' link and a 'Forgot Username' link, and they look almost identical in the interface. A lot of people accidentally click Create Account thinking it's account recovery, start the flow, and when it asks for SSN it throws an error because an account already exists under that SSN - but it shows that error in a confusing way that some people read as 'user not found.' Check which link you're actually clicking.

0 coins

Ava Kim

Author

So the 'user not found' message might actually be a duplicate account rejection error wearing a different label?

0 coins

In that specific scenario, yes. The error message isn't precise. If you accidentally started a new account creation instead of recovery, the system might be rejecting the creation attempt (because you already have one) but displaying generic error language.

0 coins

UI design on that site is genuinely terrible, this kind of confusion is so preventable

0 coins

just here to say i feel this post in my soul. spent three days on the css login issue before i even got to file. the forgot password loop into user not found is like a specific kind of torment

0 coins

Ava Kim

Author

Three days before you could even file - did that delay affect your benefit start date at all?

0 coins

My effective date was tied to when I filed, not when I started trying. Lost probably a week of potential benefits because of the login mess. Never got that back.

0 coins

that is genuinely awful and something they should compensate people for but obviously never will

0 coins

Ask the agent this follow-up if they confirm your account exists: 'Is there any hold, flag, or IT ticket already open on this account?' The reason - sometimes the user not found error is generated by a backend flag placed on the account for review, not by any login credential issue. If there's already a flag, resetting credentials won't help and you'd be chasing the wrong problem. The agent can see active flags on an account and can tell you if that's what's blocking you.

0 coins

Ava Kim

Author

What kind of things typically cause a backend flag on an account that would generate that error?

0 coins

Unusual login attempts from multiple locations, an identity verification mismatch triggered during a previous session, or sometimes just a system migration artifact from when DETR updated their platform. None of those require any wrongdoing on your part, they just get stuck.

0 coins

The migration artifact one is real. A batch of older accounts got partially migrated and are in a weird half-state that shows as nonexistent to the portal but exists on the backend. IT has to manually complete the migration.

0 coins

Went through almost exactly this last spring - couldn't get into my account for two weeks, missed weekly claims because of it. The thing that finally broke the logjam was getting to an agent who actually stayed on the line with me while she escalated to IT. I'd been getting agents who just read the script and hung up. I found Claimyr at claimyr.com through a thread like this one, used it to stop burning hours redialing, and the agent I got through it actually followed through on the escalation rather than bouncing me. The backpay for the missed weekly claims did eventually get sorted out once the account was fixed, so if you've missed any certifications because of the login issue, make sure to bring that up explicitly.

0 coins

Ava Kim

Author

When you say the agent escalated to IT while staying on the line - does that mean IT was available immediately or was there a wait within the call?

0 coins

There was a hold within the call while she contacted their internal IT support. Maybe 15 minutes of hold on top of the original wait. But she came back and confirmed the ticket was opened with a reference number before ending the call. That reference number was what I used to follow up later.

0 coins

Getting a ticket reference number is key - without that you have no leverage to follow up and they can claim no ticket exists

0 coins

ok quick question - if someone cant get into their account at all, how are they supposed to even certify for weekly benefits during this whole mess? like do those weeks just disappear or can they be claimed retroactively once access is restored

0 coins

Missed weekly certifications during a documented account access issue can typically be filed retroactively once the account problem is resolved, but you have to request it explicitly - it doesn't happen automatically. You'd need to explain the access issue to the agent and ask them to flag those weeks for late certification review.

0 coins

Does that mean those weeks are definitely approved or just eligible for review?

0 coins

Eligible for review, not automatically approved. They verify you were otherwise eligible during those weeks - job search activity, able and available, etc. If you meet the requirements for those weeks they should approve them.

0 coins

This is why keeping a job search log even during a login mess is important. You need to show you were doing the searches even though you couldn't file.

0 coins

browsers matter more than people think for css. internet explorer and older edge versions will sometimes return user not found even when credentials are right because of how they handle the session tokens. chrome or firefox, latest version, is the minimum you should be trying. also disable any password managers autofilling the fields - sometimes they populate wrong saved data and you don't notice

0 coins

Ava Kim

Author

By session tokens - does that mean the browser is submitting something malformed to the server and the server is rejecting the whole session rather than just the credentials?

0 coins

Roughly yes. The CSS portal has specific requirements for how the login session gets established and old browsers don't meet them. The error it kicks back isn't precise about why, it just looks like bad credentials.

0 coins

Password manager autofill has gotten me before on other sites, definitely turn that off before assuming it's an account problem

0 coins

Documentation step that most people skip until too late: screenshot every error message you get with the timestamp visible. When you do reach an agent and explain you've been locked out, having dated screenshots of the specific error messages makes the case that this is a real ongoing technical issue, not user error. Agents are more likely to escalate to IT and open a formal ticket when they can see evidence of a persistent technical failure rather than just taking your word for it.

0 coins

Ava Kim

Author

Can those screenshots actually be submitted somewhere as documentation or are they just for describing the problem verbally?

0 coins

Primarily for describing it accurately - 'user not found error on the CSS login page on these specific dates' is more actionable for an agent than 'I couldn't get in.' But if there's ever a formal appeal or grievance about delayed access affecting your benefit start date, documented evidence of the technical block would matter.

0 coins

screenshotting errors is just good general practice for dealing with any government system honestly

0 coins

my cousin works adjacent to this space (not at DETR but handles unemployment related stuff) and said the CSS portal goes through maintenance windows that aren't publicly announced and during those windows users get garbage error messages that don't reflect actual account status. she said if you hit weird errors try again at a totally different time of day, like early morning vs late evening, before assuming the account itself is broken

0 coins

Ava Kim

Author

What time range would count as early morning in terms of when the system is typically most stable?

0 coins

She said before 8am tends to be most stable - before the volume of users hits and before any queued maintenance from overnight runs into active hours. After 7pm is also generally better than midday.

0 coins

THEY SHOULD POST MAINTENANCE WINDOWS PUBLICLY. This is basic website operation. Letting people think their account is broken when it's a scheduled outage is inexcusable.

0 coins

Something I noticed when I had a login issue - the nui.nv.gov site sometimes loads a cached version of the login page that's slightly out of date, and submitting through a cached form can produce weird errors. Hard refresh the page (Ctrl+Shift+R on Windows) right before you enter your credentials rather than just navigating to it normally. Sounds small but fixed a weird authentication loop for me.

0 coins

Ava Kim

Author

So the cached form might be submitting to an outdated endpoint or with outdated form parameters?

0 coins

That's probably the technical mechanism yeah. All I know is the hard refresh worked when regular navigation didn't, and the IT stuff is my guess at why.

0 coins

Hard refresh before submitting any government login form is now just part of my routine after getting burned on this kind of thing

0 coins

For what it's worth I created a new account after going in circles for two weeks and it worked fine. I was scared about the duplicate account issue people mention but I called first, the agent confirmed my old account was completely dead from a migration issue, got her to note that in the record, then created the new one. Having that agent note on file meant if any duplicate account flag came up later there was documentation explaining why two accounts existed under my SSN.

0 coins

Ava Kim

Author

When the agent confirmed the old account was dead, did she do anything to close or archive it on the backend before you created the new one?

0 coins

She said she was flagging it as decommissioned and linking the note to my SSN record. Whether that actually did anything technical versus just being a notation I genuinely can't tell you - but the new account has worked fine for months with no duplicate flag issues.

0 coins

Getting that confirmation and note before creating the new account is exactly the right sequence. The documentation protects you if the system ever gets confused about the two accounts later.

0 coins

Quick update path for anyone still stuck after trying everything here: the EmployNV system is separate from CSS and sometimes an agent there can at least confirm your identity and wage history is intact in DETR's records even if CSS access is broken. It won't fix the login but it confirms you're in the system and that your underlying claim data exists. Also a second Claimyr mention is worth having here - claimyr.com got me past the hold queue bottleneck and the specific agent I reached knew about the CSS migration account issue without me having to explain the whole technical background, which saved a lot of time.

0 coins

Ava Kim

Author

Does the EmployNV system actually share data with DETR's backend or is it a parallel system where they'd only have employment records, not claim records?

0 coins

Primarily employment and job search activity - it ties into DETR but isn't the same as CSS. An EmployNV advisor can see your registration and work search history, and can contact DETR on your behalf in some cases, but they're not going to be able to restore CSS access directly.

0 coins

Didnt know EmployNV advisors could contact DETR on your behalf, that's actually worth knowing

0 coins

Just got through this exact situation last week - want to share what actually worked. After failing at every self-service option, I used Claimyr (claimyr.com - there's a demo at https://youtu.be/Mc9FNfOF_yY) to get an agent callback instead of waiting on hold all day. The agent confirmed my account was stuck in a partial migration state from when Nevada DETR updated their platform. She opened an IT ticket, gave me a reference number, and within 72 hours I got an email that my account credentials had been reset from the backend. Then the forgot password flow actually worked for the first time. Total time from stuck to resolved was about four days once I had the IT ticket open.

0 coins

Ava Kim

Author

With the backend credential reset - did they reset it to a temporary password they gave you, or did it trigger a fresh forgot password email that you then used?

0 coins

They triggered a fresh password reset email from their end, so I went through the forgot password flow on CSS but this time it actually processed correctly because the backend account state had been fixed. The link in the email worked normally and I set a new password without any user not found error.

0 coins

72 hours to fix after years of that account just being broken in the background is pretty wild. glad it worked out

0 coins

The partial migration state explanation is consistent with what I described earlier - those accounts exist on the backend but CSS can't see them properly until IT completes the migration manually. Good to hear the ticket process actually resolved it in a reasonable timeframe.

0 coins

Ava Kim

Author

Update for anyone finding this later: tried the early morning timing suggestion, hard refresh, every email I could think of - no luck on self-service. Called using the method mentioned above and got an agent who ran the SSN lookup immediately. Found my account, confirmed it was in a partial migration state exactly as described in this thread. IT ticket opened, reference number given. 48 hours later got an email, ran through the forgot password flow, and it worked. No user not found. Currently filed and waiting on adjudication determination. For anyone hitting the same wall - the account might genuinely exist but be invisible to the portal, and only an agent with backend access can confirm that and open the right ticket.

0 coins

Reference number is what you asked about earlier - glad that piece of advice held up. The partial migration explanation is consistent with what happens to accounts that were created on an older version of the CSS platform.

0 coins

Good resolution. The specific detail about SSN lookup bypassing the email credential search is worth bookmarking for anyone who finds this thread later - that's the most direct path to diagnosing what type of account issue you're dealing with.

0 coins

Really glad it resolved without needing to create a new account. The clean fix is always better than the workaround.

0 coins

Nevada Unemployment AI

Expert Assistant
Secure