Http error 401 the requested resource requires user authentication

New Page

blockedHTTP error 401. The recurso solicitado requires authentication of usuario.power supply RRS

Archived Forums 301-320

 > 

Security for ASP.NET

  • Pregunta

  • Pregunta

    Registrar for voting

    0

    Registrar for voting

    User1462999811 posted

    Tengo un problema al use the authentication of Windows and IIS 7.5. Recibo el error “HTTP Error 401. El recurso solicitado requiere autenticación de usuario” al acceder à mi page. Lo gracioso es que cuando voy a ” https://svr.mysite.com/app “, aparece el error 401. Pero, si modifico mi archivo de host para ir a ” https://svr1.mysite.com/app ” (the misma IP as the previous URL), all functions as deberia. ¿Alguien tiene alguna idea de por qué puede ser esto?

    Tuesday, June 17, 2014 11:07 a.m.

    avatar of anonymous

    Anonymous

    avatar of anonymous

    985

    Points

    5 best

    Anonymous
    Joined in May 2018

    1

    hilos from anonymous

    Show activity

    985 dots

answers

  • Pregunta

    Registrar for voting

    0

    Registrar for voting

    User-484054684 posted

    ¿Está seguro de que estos dos apuntan al mismo servidor (IP), es decir, https://svr.mysite.com/app  y https://svr1.mysite.com/app  ?

    Compruebe también si ha configurado nombres de dominio en algún lugar de la configuración del host IIS.

    Una instrucción de muestra de cómo se podría haber agregado un encabezado de host en su IIS de la siguiente manera de MSDN:

    Abra el Administrador de IIS. Para obtener información sobre cómo abrir el Administrador de IIS, consulte Abrir el Administrador de IIS (IIS 7) .

    • En el panel Conexiones , expanda el nodo Sitios en el árbol y luego seleccione el sitio para el que desea configurar un encabezado de host.

    • En el panel Acciones , haga clic en Enlaces .

    • En el cuadro de diálogo Enlaces del sitio , seleccione el enlace para el que desea agregar un encabezado de host y luego haga clic en Editar o haga clic en Agregar para agregar un nuevo enlace con un encabezado de host.

    • En el cuadro Nombre de host , escriba un encabezado de host para el sitio, como www.contoso.com .

    • Haga clic en Aceptar .

    • Para agregar un encabezado de host adicional, cree un nuevo enlace con la misma dirección IP y puerto, y el nuevo encabezado de host. Repita para cada encabezado de host que desee usar esta dirección IP y puerto.

    • Referencia: http://technet.microsoft.com/en-us/library/cc753195(v=ws.10).aspx
    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM

    Tuesday, June 17, 2014 5:04 PM

    avatar of anonymous

    Anonymous

    avatar of anonymous

    985

    Points

    Top 5

    Anonymous
    Joined May 2018

    1

    Son of Anonymous

    Show activity

    985 dots

All answers

  • Pregunta

    Registrar for voting

    0

    Login to vote

    User-484054684 posted

    Are you sure that these two dots point to the same server (IP), i.e. https://svr.mysite.com/app and https://svr1.mysite.com/app?

    Also check if you have configured domain names anywhere in the IIS host settings.

    A sample instruction explaining how a host header could be added in your IIS as follows from MSDN:

    Open the IIS manager. For more information about opening IIS Manager, see Open IIS Manager (IIS 7).

    • Dans le volet Connexions , développez le nœud Sites dans l’arborescence, puis sélectionnez le site pour lequel vous souhaitez configurer un en-tête d’hôte.

    • Dans le volet Actions , cliquez sur Liaisons .

    • In the Site Bindings dialog box, select the binding for which you want to add a host header and then click Edit or click Add to add a new binding with a host header.

    • In the Host name box, type a host header for the site, such as www.contoso.com.

    • Click OK.

    • To add an additional host header, create a new binding with the same IP address and port, and the new host header. Repeat for each host header that you want to use this IP address and port.

    • Reference: http://technet.microsoft.com/en-us/library/cc753195(v=ws.10).aspx
    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM

    Tuesday, June 17, 2014 5:04 PM

    avatar of anonymous

    Anonymous

    avatar of anonymous

    985

    Points

    Top 5

    Anonymous
    Joined May 2018

    1

    Anonymous’s threads

    Show activity

    985 points

  • Pregunta

    Registrar for voting

    0

    Connectez-vous pour voter

    Utilisateur1815411410 posté

    Salut, je suis d’accord avec Siva, le problème est certainement avec le site Web IIS Bindings. Je pense que vous avez peut-être oublié d’ajouter correctement les liaisons du site.

    mercredi 18 juin 2014 00:24

    avatar of anonymous

    Anonyme

    avatar of anonymous

    985

    Points

    Top 5

    Anonyme
    Inscrit en mai 2018

    1

    Fils d’Anonyme

    Afficher l’activité

    985 points

  1. Maison
  2. Centre de ressources
  3. Base de connaissances
  4. Codes d’état HTTP
  5. How to Fix 401 Unauthorized Error Quickly (5 Methods)

How to Fix 401 Unauthorized Error Quickly (5 Methods)

Last update: June 10, 2022

401 errorclose

Trying to access a WordPress site and encountering an error page is annoying at best, whether that site is yours or someone else’s. As with many HTTP response codes, part of what makes a 401 error so frustrating is the lack of information it offers to diagnose and fix the problem.

The 401 error can happen with any browser, so it’s a pretty common issue people face. In most cases, this problem is relatively simple and straightforward to fix.

In a hurry? Save this article as a PDF.

Tired of scrolling? Download a PDF version for easier offline reading and sharing with coworkers.

Download

In this post, we’ll explain what 401 error messages are and why they happen. Then, we’ll walk you through five methods you can use to fix them.

Let’s get started!

Table of Contents

  1. What is the 401 Error Code?
  2. An Introduction to the 401 Error Code
  3. What Causes a 401 Error?
  4. How to Fix the 401 Error (5 Methods)

What is the 401 Error Code?

The Internet Engineering Task Force (IETF) defines the error 401 Unauthorized as:

The 401 (Unauthorized) status code indicates that the request has not been applied because it lacks valid authentication credentials for the target resource. The server generating a 401 response MUST send a WWW-Authenticate header field containing at least one challenge applicable to the target resource.

An Introduction to the 401 Error Code

HTTP 400 status codes are encountered when there is a problem making a request. A 401 error, in particular, happens when your browser denies you access to the page you’re trying to visit.

See how Kinsta stacks up against the competition. Select your provider WP Engine SiteGround GoDaddy Bluehost Flywheel HostGator Cloudways AWS Digital Ocean DreamHost Other Compare

Par conséquent, au lieu de charger la page Web, le navigateur chargera un message d’erreur. Les erreurs 401 peuvent se produire dans n’importe quel navigateur, de sorte que le message qui s’affiche peut différer.

For example, in Chrome or Edge, you’ll likely see a paper icon with a simple message telling you that the page in question isn’t working. It will include the phrase “HTTP Error 401” at the bottom and ask you to contact the site owner if the problem persists:

http 401 error in ChromeThe 401 error in Chrome

At other times and in other browsers, you might get a slightly less friendly warning which is just a blank page with a “401 Authorization Required” message:

Error 401 Authorization requestNginx 401 Permission Required Error Message

Other variations include:

  • “HTTP Error 401 – Unauthorized”
  • “401 Unauthorized”
  • “Access denied”

Ces erreurs se produisent sur les sites Web qui nécessitent une connexion pour y accéder. Dans la plupart des cas, cela signifie que quelque chose ne va pas avec les informations d’identification ou avec la capacité du navigateur à les lire comme valides.

Ceci est similaire à HTTP 403 Forbidden Error, en ce sens que l’accès n’est pas autorisé à l’utilisateur. Cependant, contrairement à l’erreur 403, le message d’erreur 401 indique que le processus d’authentification a échoué.

Le code est envoyé via l’en-tête WWW-Authenticate, qui est chargé d’identifier la méthode d’authentification utilisée pour accorder l’accès à une page Web ou à une ressource.

The HTTP 401 error is all too common 🤦‍♀️ – and this guide will give you everything you need to fix it the next time you see this message pop up ✅Click to tweet What causes a 401 error?

If you encounter an error code in the 400s, you know you’re dealing with a client-side (or browser-side) issue. While the problem may be happening within your browser, however, it doesn’t necessarily always mean that’s the culprit, which we’ll explain in more detail later.

401 errors occur on restricted resources, such as password-protected pages of your WordPress site. So it’s safe to assume that the cause of the problem has something to do with the authentication credentials.

Outdated Browser Cache and Cookies

One of the most common reasons you might experience a 401 error is that your browser’s cache and cookies are out of date, preventing the authorization from successfully going through. If your browser isn’t using the valid authentication credentials (or any at all), the server will reject the request.

Plugin Incompatibility

At other times, this error is caused by a plugin incompatibility or error. For example, a firewall or security plugin can mistake your login attempt as malicious activity, and return a 401 error to protect the page.

Incorrect URL or Outdated Link

It’s also possible that the source of the problem can be attributed to a minor mistake. Common culprits in this category include an incorrectly-typed URL or an outdated link.

How to Fix the 401 Error (5 Methods)

Now that we’ve gone through a bit of background on the 401 error, it’s time to discuss how you can resolve it.

Let’s take a look at five methods you can use:

  1. Look for Errors in the URL
  2. Clear Your Browser’s Cache
  3. Flush Your DNS
  4. Deactivate Your WordPress Plugins
  5. Check the WWW-Authenticate Header Response

1. Look for Errors in the URL

We’ll start off with the easiest potential fix: making sure you used the correct URL. This may sound simple, but 401 errors can sometimes appear if the URL wasn’t correctly entered in.

Another possibility is that the link you used to visit the page in question points to the wrong URL. For example, it might be outdated, or leading to a page that no longer exists (and no redirects are in place).

Therefore, it’s worth double-checking the URL you used. If you typed it in yourself, verify that you spelled everything correctly. If you clicked on a link, confirm that it’s pointing to the page you’re trying to access (or try to visit that page directly through the website).

Sign Up For the Newsletter

Sign Up Now

En soumettant ce formulaire, j’accepte les conditions générales et la politique de confidentialité, y compris le transfert de données aux États-Unis. En partageant votre e-mail, vous acceptez également de recevoir des informations occasionnelles liées aux services, événements et promotions de Kinsta. Vous êtes libre de vous désabonner à tout moment.

Vous voulez savoir comment nous avons augmenté notre trafic de plus de 1000 % ?

Join over 20,000 other people who receive our weekly newsletter with insider WordPress tips!

Subscribe now

2. Clear your browser cache

Your browser’s cache is designed to improve your online experience by reducing page load times. Unfortunately, this can sometimes also cause unwanted interruptions.

As we mentioned earlier, one of the common causes of the 401 error is outdated or incorrect cache data or cookies. Therefore, if you don’t notice any issues with the page URL, the next step is to clear your browser’s cache.

This will erase all invalid information stored locally in your browser, which may interrupt the authentication process. Similarly, your browser’s cookies may contain authentication data that only needs to be refreshed.

If you are a Google Chrome user, you can do this by clicking the menu icon in the top right corner of the browser and then going to  Settings . In the  Privacy and security section , click Clear browsing data :

borrar datos de navigation para corregir el error 401The Clear browsing data section in Google Chrome

A new window will open. Under the  Basic tab  , make sure all three boxes are selected, then select Clear data  :

clear cromo datesThe clear browsing data window in Chrome

This process will be a little different in other browsers. For example, in Mozilla Firefox, you would click the library icon in the upper right corner of the browser, followed by History  > Clear recent history:

clear firefox historyThe “Clear recent history” option in Firefox settings

In the panel that opens next, select  Everything  from the drop-down menu at the top, make sure “Cache” is selected, then click the Clear Now button  :

firefox hidden borerFirefox’s “Clear History” panel

If you are using another browser, please refer to this guide to clear the cache

3. Flush your DNS

Another method you can try to resolve the 401 error is to flush your Domain Name Server (DNS). Although this is a rarer issue, it could be a possible cause, so it’s worth trying if the first two solutions don’t work.

Tired of below average Tier 1 WordPress Hosting support without the answers? Try our world-class support team! Discover our packages

To do this in Windows, click the Start button and type cmd in the search bar. Press Enter and the command prompt will open. Copy and paste the ipconfig /flushdns command, then press Enter again  :

system symbolThe command prompt interface in Windows

On a Mac, you can do this by going to Finder > Applications > Utilities > Terminal:

The Terminal app on MacThe Terminal app on Mac

Saisissez la ligne de commande sudo killall -HUP mDNSResponder et appuyez sur Entrée . Ensuite, vous pouvez essayer d’actualiser la page que vous tentiez de visiter, pour voir si l’erreur 401 a été résolue.

4. Désactivez vos plugins WordPress

Le problème à l’origine de votre erreur 401 n’est peut-être pas dû à votre navigateur. Si vous rencontrez des difficultés pour accéder à votre site WordPress, il est également possible qu’un ou plusieurs plugins soient à blâmer.

Certains plugins, en particulier les plugins axés sur la sécurité, sont configurés pour afficher une erreur 401 lorsqu’ils suspectent une activité de connexion suspecte qui pourrait indiquer une attaque. D’autres pourraient simplement souffrir de problèmes de compatibilité. Par conséquent, c’est une bonne idée de désactiver tous vos plugins WordPress et de voir si cela résout le problème.

Vous pouvez désactiver tous vos plugins en même temps dans votre tableau de bord, en vous rendant dans Plugins > Plugins installés . Cochez la case en haut pour tous les sélectionner. Ensuite, dans le  menu déroulant Actions groupées, sélectionnez Désactiver  et cliquez sur le bouton Appliquer :

The plugin disable setting in the WordPress dashboardThe plugin disable setting in the WordPress dashboard

After that, try reloading the page that returned the 401 error to see if this has resolved the issue. If it has, you can manually activate each plugin one at a time, in order to determine which one is causing the problem.

Then you can remove that plugin, replace it with a new one, or contact its developer for assistance.

5. Check the WWW-Authenticate Header Response

At this point, if the issue hasn’t been fixed, it may be caused by a server-side problem. This means our last fix will be a bit more involved.

As we saw earlier, the 401 response is sent through the WWW-Authenticate header, which appears as “WWW-Authenticate: <type> realm=<realm>”. It includes ‘challenges’, or strings of data that indicate what type of authentication is required in order for access to be granted.

En un mot, vous voudrez vérifier et voir si la réponse d’en-tête a été envoyée, et plus précisément, quel schéma d’authentification a été utilisé. À tout le moins, cela peut aider à réduire la cause du problème et vous rapprocher d’une solution.

Pour ce faire, accédez à la page Web qui affiche l’erreur 401 et accédez à la console du développeur dans Chrome. Vous pouvez cliquer avec le bouton droit sur la page et sélectionner Inspecter , ou utiliser Ctrl+Maj+J .

Next, click on the Network tab and reload the page. This will generate a list of resources.  Select the Status header to sort the table and locate the 401 status code:

network status error 401The 401 status code in the Chrome Developer Console

Select this entry, then click the Headers tab. Under Response Headers , find the WWW-Authenticate header:

www authenticate headerThe Developer Console Response Headers section

The information in the response header, especially the authentication schemes, can give you more information about what’s going on and point you towards a solution. This can help you understand the type of authentication expected by the server.

Por ejemplo, en el ejemplo anterior, podemos ver que el esquema de autenticación es “Basico”. This means that the solicitud de autenticación solo must require an identificación y una contraseña. For more detailed information and instructions on how to use this information, we recommend that you consult the HTTP Authentication System Registry.

HTTP 401 errors, go for it! 🧙‍♂️ 5 ways to stop those pesky messages (no magic required) ✨Click to tweet resume

Cuando su navegador y servidor tienen problems para comunicarse o autenticar solicitudes, à veces se ve obligado a lidiar con errors como el error 401. If well este problema es irritante, el mensaje suele ser temporal y repairable.

Aquí hay cinco métodos que puede usar para corregir el error 401:

  1. Busque errors in the URL.
  2. Limpia the hidden memory of your browser.
  3. Limpia you DNS.
  4. Disable your WordPress add-ons.
  5. Verify the respuesta del encabezado WWW-Authenticate.

Ahorre tiempo, costos y maximice el rendimiento del sitio con:

  • Instant support from WordPress alojamiento experts, 24/7.
  • Cloudflare enterprise integration.
  • Global Audience Alcance with 35 data centers worldwide.
  • Optimización con nuestro monitoreo de rendimiento de applications integrado.

Todo eso y mucho más, en un solo plan sin contratos a largo plazo, migraciones asistidas y una garantía de devolución de dinero de 30 días. Consult nostros planes o hable con ventas para encontrar el plan adecuado para usted.


Video Http error 401 the requested resource requires user authentication

Related Posts

Free chat room code for my website

Contents1 How to set up a free chat room on the website.2 3 comentarios2.1 Trackbacks/Pingbacks2.2 Submit a Comment Cancel reply3 How to Create a Chat Room Website…

Background image full screen css

Contents1 Cómo – Full Page Image1.1 Example1.2 Example2 CSS background image tamaño tutorial: how to codify a complete page background image3 Perfect Full Page Background Image3.1 Méthode CSS géniale,…

WordPress leverage browser caching

Contents1 Aproveche el almacenamiento in hidden del navegador1.1 Will it works for my website?1.2 Where are plugin options1.3 Some JavaScript files still display under Leverage Browser Caching1.4…

WordPress post to facebook page

Contents1 How to Automatically Post to Facebook from WordPress1.1 Download Now: How to Launch a WordPress Website [Free Guide + Checklist]1.2 1. Create an IFTTT account.1.3 2….

Download images from wordpress media library

Contents1 How to export your WordPress media library1.1 Download maintenant : How to launch a WordPress website [Free Guide + Checklist]1.2 How to export your WordPress media…

WordPress single post template

Contents1 How to Create Custom Unique Post Templates in WordPress2 Post Template Files2.1 author.php2.2 Fecha.php3 Handbook navigation4 How to Create Custom Single Post Templates in WordPress5 Video…