# Passwordless with Classing Universal Login responding with "no email or no verification\_code provided" **URL:** \ **Category:** Get Help\ **Tags:** passwordless-email-connection, connections\ **Created:** [February 5, 2024, 7:05pm UTC](https://community.auth0.com/t/passwordless-with-classing-universal-login-responding-with-no-email-or-no-verification-code-provided/126547 "2024-02-05T19:05:39Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![ada\_vlachou](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ada_vlachou/32/60209_2.png) [@ada\_vlachou](https://community.auth0.com/u/ada_vlachou)\ **Post date:** [February 5, 2024, 7:05pm UTC](https://community.auth0.com/t/passwordless-with-classing-universal-login-responding-with-no-email-or-no-verification-code-provided/126547/1 "2024-02-05T19:05:39Z")
Hi, we are trying to use the Next.js sample with a passwordless flow. That works fine with New Universal Login. However, due to a [known issue](https://community.auth0.com/t/passwordless-new-universal-login-shows-no-error-after-denying-access-in-pre-registration-action/119480), we decided to switch to Classic Universal Login. The problem there is that, when clicking on the Login button in the app, it returns a 400 Bad Request, with: 1. error: access\_denied 2. error\_description: no email or no verification\_code provided Trying the connection from the Auth0 admin site, it does send an email. Any ideas what we’re doing wrong/missing? ---
**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\ **Post date:** [February 5, 2024, 11:31pm UTC](https://community.auth0.com/t/passwordless-with-classing-universal-login-responding-with-no-email-or-no-verification-code-provided/126547/3 "2024-02-05T23:31:30Z")
Hi @ada_vlachou, Thanks for reaching out to the Auth0 Community! It appears that you have a Pre-User Registration Action script that only allows sign up to users who are in the whitelist array. Checking your logs, I verified that the error happens when you used an email address that has not been whitelisted. This is the root cause of the issue. There are a couple of ways you could address this. You could temporarily disable the Action script while you test, or alternatively, you could add the email address to the whitelist array. Let me know how this goes for you. Thanks, Rueben ---
**Author:** ![ada\_vlachou](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ada_vlachou/32/60209_2.png) [@ada\_vlachou](https://community.auth0.com/u/ada_vlachou)\ **Post date:** [February 5, 2024, 11:57pm UTC](https://community.auth0.com/t/passwordless-with-classing-universal-login-responding-with-no-email-or-no-verification-code-provided/126547/4 "2024-02-05T23:57:41Z")
Hi, thanks for the prompt response -I think it was probably something else as I created another application (identical as far as I can tell) where it works as expected, i.e., if the email is in the list an email is sent, otherwise, an error is returned. Besides, I wasn’t even getting to the login screen, where I would get a chance to enter any email. The error was appearing on clicking Login. I suppose I must have changed something somewhere and broke it, it’s just weird that it worked for the New Universal Login and not the classic one. I’m curious to know what it was but doubt I’ll find out ---
**Author:** ![river](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/river/32/51810_2.png) [@river](https://community.auth0.com/u/river)\ **Post date:** [February 6, 2024, 10:51pm UTC](https://community.auth0.com/t/passwordless-with-classing-universal-login-responding-with-no-email-or-no-verification-code-provided/126547/5 "2024-02-06T22:51:31Z")
this happens to using React sample as well. All I did is add ‘connection: “email”’ as a authorizationParams ---
**Author:** ![ada\_vlachou](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ada_vlachou/32/60209_2.png) [@ada\_vlachou](https://community.auth0.com/u/ada_vlachou)\ **Post date:** [February 7, 2024, 1:24pm UTC](https://community.auth0.com/t/passwordless-with-classing-universal-login-responding-with-no-email-or-no-verification-code-provided/126547/6 "2024-02-07T13:24:44Z")
I think it was the exact opposite for me - I had added ‘connection:“email”’ so it would work with the new universal login, but seemed to break the Classic Universal Login. The rest was on my side, I removed it but then something was caching and it wouldn’t work with either login - it only later occurred to me to clean & rebuild from scratch, and then it worked ---
**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\ **Post date:** [February 14, 2024, 11:35pm UTC](https://community.auth0.com/t/passwordless-with-classing-universal-login-responding-with-no-email-or-no-verification-code-provided/126547/7 "2024-02-14T23:35:34Z")
Hi @ada_vlachou, Thanks for the updates. Could you check your network activity when accessing your app through the Classic Universal Login experience? There should be some clues about why the page is not rendering. Additionally, it’s possible that there is an error in your Classic Universal Login custom HTML page, which could be causing the page not to render. You might consider resetting it back to the default template to see if that resolves the issue. To do so, please navigate to your [_Auth0 Dashboard \> Branding \> Universal Login \> Advanced Options \> Login_](https://manage.auth0.com/#/login_page) and selecting **Lock** as the default template. Thanks, Rueben ---
**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\ **Post date:** [February 28, 2024, 11:36pm UTC](https://community.auth0.com/t/passwordless-with-classing-universal-login-responding-with-no-email-or-no-verification-code-provided/126547/8 "2024-02-28T23:36:29Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.