401 Error on backend after login

  • Resolved Steve Sears

    (@flsocialist)


    5 years, 7 months ago

    about 2 months ago I got a chrome update on my Pixel Book and I could no longer access the backend of any of my WordPress sites. I would log in to a 401 error (Proper authorization is required to access this resource!) At this time, only the Chromebook had this issue. I could use Windows, Linux, and Android with no issue. Today, windows chrome got an update and guess what, the same thing is happening. (strangely, I can not log onto to twitter either, just won’t load). I have to believe this is a chrome thing but even with submitting a bug months ago, it seems like nothing has been down. Does anyone know of a way to fix this? Either chrome has implemented something that breaks the backend, chrome itself is screwed up, or my host has something configured that chrome does not like. But in two months I’ve not figured it out.

    Steve

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator James Huff

    (@macmanx)

    Try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel (consult your hosting provider’s documentation for specifics on these), navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue (theme functions can interfere like plugins).

    Thread Starter Steve Sears

    (@flsocialist)

    I did that when the problem first came up two months ago. But I did end up finding the issue, and it was not what I expected. Because it was not on all OS’s (found out MacOS was not an issue along with Linus and Android) I did not look at the chrome extensions. I did today. The private internet access VPN extension was causing the issue. One uninstalled it worked. funny thing is, it was causing the issue even when NOT running, just activated.

    Thanks for the help

    Steve

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘401 Error on backend after login’ is closed to new replies.