Email Confirmation 'invalid token' in production

System Information
  • Strapi Version: 3.5.1
  • Operating System:
  • Database:
  • Node Version:
  • NPM Version:
  • Yarn Version:

I’m struggling with getting email confirmation working correctly in production. Locally it works fine.

When the user clicks on the link in the email I get:-

 {"statusCode":400,"error":"Bad Request","message":"token.invalid"}

The confirmation true does seem to have been applied though in the database, but the user is stuck here and doesn’t get forwarded to the URL set in advanced settings.

Locally it works correctly.

Any help greatly appreciated.

1 Like

As per documentation I have production server.js with an environment var of my strapi admin url

I can see on github that this issue was described in March but no updates on it, was it solved in a strapi update?

I submitted the issue back in March.

I still have the issue – even with the 3.6.7 update of Strapi.

The issue has forced me to confirm new users manually. (Fortunately, it’s for an internal intranet site – so the work involved in manual confirmation is pretty minimal.)

BTW – your description of the error matches my error exactly.

1 Like

This issue appears to be fixed in 3.6.8.

hello did you find a solution??

We’re intermittently getting this issue in production too. Email confirmation works correctly for most users - and it’s worked correctly every time I’ve tried it - but we’ve had a number of reports of this happening too. We’re on 4.15.0, so it doesn’t look like it has been entirely fixed.