-
-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: failed to find request token in session #6
Comments
I've had the same issue as this. We are using express and session-mongoose. Did you solve it? |
I had the error for a short while too but the code comment below made sense, and after changing my callback url to be the same as the initiaiting host url, it now works fine.
|
Thanks for the pointer @cjroebuck. Changing localhost to 127.0.0.1 solves it. |
the solution @cjroebuck helps me too (the callback had |
I am also getting same issue. please help +1 |
+1 |
1 similar comment
+1 |
Hi, I have the following code:
I have passport-local and passport-linkedin. Both are working in local development environments. However, passport_linkedin doesn't work in production (nodejitsu). I'm getting
I've checked the domain name and subdomains, and found no discrepancy there between /auth/linkedin and /auth/linkedin/callback. I don't know what else could contribute to this error.
The text was updated successfully, but these errors were encountered: