I can't login to the admin panel

On my production server, now when anyone tries to sign into the admin panel it gets stuck on the loading spinning wheel. The console outputs this:

Admin-AuthenticatedApp.5f479702.chunk.js:24 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading ‘digest’)
at Object.digestMessage (Admin-AuthenticatedApp.5f479702.chunk.js:24:4912)
at Tt (Admin-AuthenticatedApp.5f479702.chunk.js:24:4992)
at Admin-AuthenticatedApp.5f479702.chunk.js:24:7064
at Admin-AuthenticatedApp.5f479702.chunk.js:24:7076
at Ll (main.c0d82de4.js:6754:25634)
at Oi (main.c0d82de4.js:6754:44744)
at main.c0d82de4.js:6754:42937
at A (main.c0d82de4.js:6833:1597)
at MessagePort.le (main.c0d82de4.js:6833:1966)

What I tried:

  • Deleting .cache, dist, node_modules & package-lock.json. Reinstalling npm packages and rebuilding.
  • Deleting all admin users from the database. Then I was prompted to create a new user account, but once I did the same problem happens.

It was working fine until today when I pulled in an update to the repository which bumped the Strapi version from 4.12.1 to 4.12.6. Just this and a schema change. And it is all working normally on my local machine.

Any ideas? I’m not sure what to do at this stage.

System Information
  • Strapi Version: 4.12.6
  • Operating System: Ubuntu. AWS EC2
  • Database: MySQL
  • Node Version: 18.17.0
  • NPM Version: 9.6.7
  • Yarn Version:

1 Like

Ok I also tried to completely drop and let Strapi rebuild the database, and the same issue happens. I can’t work it out, I feel I’ve tried everything.

1 Like

I do have the same issue, I can’t resolve it yet. seems like the 4.12.6 has the issue.

Same issue

4.12.6 (node v16.15.1)

Don’t know what is the issue?

There is some issue in 4.2.6. downgraded to
“dependencies”: {
@strapi/strapi”: “4.12.1”,
@strapi/plugin-users-permissions”: “4.12.6”,
@strapi/plugin-i18n”: “4.12.6”,
“mysql”: “2.18.1”
it worked!!

1 Like

4.12.1 Worked for me too, Thanks :wink:

1 Like

Open the browser’s developer console and check if there are any additional JavaScript errors or warnings. Sometimes, these can provide more specific information about the problem. Carefully review the code changes made during the update from Strapi 4.12.1 to 4.12.6 and any schema changes. Look for potential areas where the code might be breaking, especially related to authentication and user management.