HTTP ERROR 401 - This page isn’t working right now. However, google Chrome works fine.

%3CLINGO-SUB%20id%3D%22lingo-sub-1104309%22%20slang%3D%22en-US%22%3EHTTP%20ERROR%20401%20-%20This%20page%20isn%E2%80%99t%20working%20right%20now.%20However%2C%20google%20Chrome%20works%20fine.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1104309%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20currently%20getting%20a%20HTTP%20Error%20401%20message%20in%20Edge%20(Beta).%26nbsp%3B%20It%20only%20happens%20when%20trying%20to%20authorise%20via%20ADFS%2C%20Azure%20AD%20authorisation%20is%20working%20as%20expected.%26nbsp%3B%20When%20I%20try%20the%20same%20operation%20in%20Google%20Chrome%2C%20everything%20is%20working%20as%20expected%20(see%20pic).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20completed%20the%20following%3A%3C%2FP%3E%3CUL%3E%3CLI%3ECleared%20browser%20history.%3C%2FLI%3E%3CLI%3ECleared%20password%20history.%3C%2FLI%3E%3CLI%3ERemoved%20any%20relevant%20entries%20from%20credential%20manager%3C%2FLI%3E%3CLI%3ERenewed%20my%20certificate.%3C%2FLI%3E%3C%2FUL%3E%3CP%3EOnly%20other%20relevant%20info%20I%20can%20think%20of%20is%20that%20I%20changed%20my%20password%20at%20some%20point%20last%20week.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMany%20thanks%20in%20advance.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1104309%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E401%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAAD%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eadfs%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ehttp%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESSO%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eunauthorised%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1996392%22%20slang%3D%22en-US%22%3ERe%3A%20HTTP%20ERROR%20401%20-%20This%20page%20isn%E2%80%99t%20working%20right%20now.%20However%2C%20google%20Chrome%20works%20fine.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1996392%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20error%20is%20too%20generic%20and%20does%20not%20tell%20you%20exact%20problem.%20The%20first%20thing%20you%20need%20to%20know%20about%20the%20http%20error%20%3CA%20href%3D%22http%3A%2F%2Fnet-informations.com%2Fq%2Fmis%2F500.html%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E500%20the%20page%20isn't%20working%3C%2FA%3E%20is%20that%20the%20error%20can%20only%20be%20resolved%20by%20fixes%20to%20the%20Web%20server%20software.%20It%20is%20not%20a%20client-side%20problem%20meaning%20that%20the%20problem%20is%20not%20with%20your%20browser%2C%20your%20computer%2C%20or%20your%20internet%20connection.%20The%20error%20is%20too%20generic%20and%20does%20not%20tell%20you%20exact%20problem.%20When%20you%20hit%20an%20internal%20server%20error%20it%20usually%20means%20some%20parts%20of%20your%20web%20server%20is%20not%20configured%20correctly%20or%20the%20application%20is%20trying%20to%20do%20something%20and%20the%20server%20is%20failing%20to%20carry%20out%20the%20request%20due%20to%20a%20conflict%20or%20restriction.%20Please%20check%20the%20error%20logs%20on%20your%20server%20for%20a%20more%20specific%20error%20message%2C%20which%20may%20give%20a%20clue%20to%20why%20this%20is%20happening%20on%20your%20website%2Fserver.%20These%20errors%20are%20often%20caused%20by%20plugin%20or%20theme%20function%20conflicts%2C%20so%20if%20you%20have%20access%20to%20your%20Dashboard%2C%20try%20deactivating%20all%20plugins.%20It%20is%20up%20to%20the%20administrators%20of%20the%20Web%20server%20site%20to%20locate%20and%20analyse%20the%20logs%20which%20should%20give%20further%20information%20about%20the%20error.%20However%2C%20there%20are%20often%20ways%20to%20quickly%20get%20around%20the%20problem%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EReload%20or%20Refresh%20the%20Webpage.%3C%2FLI%3E%3CLI%3ECheck%20you%20server%20permission.%3C%2FLI%3E%3CLI%3ECorrupt%20Plugins.%3C%2FLI%3E%3CLI%3E.htaccess%20file%20may%20be%20corrupt.%3C%2FLI%3E%3CLI%3EExceeded%20PHP%20memory%20limit.%3C%2FLI%3E%3CLI%3EIncrease%20the%20memory%20setting%20in%20the%20wp-config.php%20file.%3C%2FLI%3E%3CLI%3EClear%20your%20browser%20cookies%20and%20cache%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1996393%22%20slang%3D%22en-US%22%3ERe%3A%20HTTP%20ERROR%20401%20-%20This%20page%20isn%E2%80%99t%20working%20right%20now.%20However%2C%20google%20Chrome%20works%20fine.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1996393%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20first%20thing%20you%20need%20to%20know%20about%20the%20http%20error%20500%20the%20page%20isn't%20working%26nbsp%3Bis%20that%20the%20error%20can%20only%20be%20resolved%20by%20fixes%20to%20the%20Web%20server%20software.%20It%20is%20not%20a%20client-side%20problem%20meaning%20that%20the%20problem%20is%20not%20with%20your%20browser%2C%20your%20computer%2C%20or%20your%20internet%20connection.%20The%20error%20is%20too%20generic%20and%20does%20not%20tell%20you%20exact%20problem.%20When%20you%20hit%20an%20internal%20server%20error%20it%20usually%20means%20some%20parts%20of%20your%20web%20server%20is%20not%20configured%20correctly%20or%20the%20application%20is%20trying%20to%20do%20something%20and%20the%20server%20is%20failing%20to%20carry%20out%20the%20request%20due%20to%20a%20conflict%20or%20restriction.%20Please%20check%20the%20error%20logs%20on%20your%20server%20for%20a%20more%20specific%20error%20message%2C%20which%20may%20give%20a%20clue%20to%20why%20this%20is%20happening%20on%20your%20website%2Fserver.%20These%20errors%20are%20often%20caused%20by%20plugin%20or%20theme%20function%20conflicts%2C%20so%20if%20you%20have%20access%20to%20your%20Dashboard%2C%20try%20deactivating%20all%20plugins.%20It%20is%20up%20to%20the%20administrators%20of%20the%20Web%20server%20site%20to%20locate%20and%20analyse%20the%20logs%20which%20should%20give%20further%20information%20about%20the%20error.%20However%2C%20there%20are%20often%20ways%20to%20quickly%20get%20around%20the%20problem%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EReload%20or%20Refresh%20the%20Webpage.%3C%2FLI%3E%0A%3CLI%3ECheck%20you%20server%20permission.%3C%2FLI%3E%0A%3CLI%3ECorrupt%20Plugins.%3C%2FLI%3E%0A%3CLI%3E.htaccess%20file%20may%20be%20corrupt.%3C%2FLI%3E%0A%3CLI%3EExceeded%20PHP%20memory%20limit.%3C%2FLI%3E%0A%3CLI%3EIncrease%20the%20memory%20setting%20in%20the%20wp-config.php%20file.%3C%2FLI%3E%0A%3CLI%3EClear%20your%20browser%20cookies%20and%20cache%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Hello all,

 

I am currently getting a HTTP Error 401 message in Edge (Beta).  It only happens when trying to authorise via ADFS, Azure AD authorisation is working as expected.  When I try the same operation in Google Chrome, everything is working as expected (see pic).

 

I have completed the following:

  • Cleared browser history.
  • Cleared password history.
  • Removed any relevant entries from credential manager
  • Renewed my certificate.

Only other relevant info I can think of is that I changed my password at some point last week.

 

Many thanks in advance.

1 Reply

The first thing you need to know about the http error 500 the page isn't working is that the error can only be resolved by fixes to the Web server software. It is not a client-side problem meaning that the problem is not with your browser, your computer, or your internet connection. The error is too generic and does not tell you exact problem. When you hit an internal server error it usually means some parts of your web server is not configured correctly or the application is trying to do something and the server is failing to carry out the request due to a conflict or restriction. Please check the error logs on your server for a more specific error message, which may give a clue to why this is happening on your website/server. These errors are often caused by plugin or theme function conflicts, so if you have access to your Dashboard, try deactivating all plugins. It is up to the administrators of the Web server site to locate and analyse the logs which should give further information about the error. However, there are often ways to quickly get around the problem:

 

  • Reload or Refresh the Webpage.
  • Check you server permission.
  • Corrupt Plugins.
  • .htaccess file may be corrupt.
  • Exceeded PHP memory limit.
  • Increase the memory setting in the wp-config.php file.
  • Clear your browser cookies and cache