LogoutLink is not redirecting to my desire URL
I tried to follow the instruction to set up my post logout route.
However, it still redirect me to a default route instead of my home page.
Does anyone have the same issue ? Or did I miss anything?
Thank you
![No description](https://cdn.answeroverflow.com/1263615687373623569/image.png)
![No description](https://cdn.answeroverflow.com/1263615687683739669/image.png)
![No description](https://cdn.answeroverflow.com/1263615687960694868/image.png)
![No description](https://cdn.answeroverflow.com/1263615688350896169/image.png)
9 Replies
Hi, just to check, since you changed the environment variables on vercel, have you redeployed the application?
Yes, I did. I tried couple of times actually
Now it's not even let me login.... just keep loading
![No description](https://cdn.answeroverflow.com/1264101361679597638/image.png)
Now I am keep getting this error.... I have restart a session multiple times, but still getting this. No clue at all. Please help.
![No description](https://cdn.answeroverflow.com/1264268964679385118/image.png)
Hey @summer_teng,
Sorry to hear you are experiencing this issue.
A will reach out to Vercel expert team mate of mine tomorrow who will look into this when he has capacity
Hey @summer_teng,
Your issue has been fixed in the latest version (v2.3.6) of the NextJS SDK.
Please update your NextJS SDK and let me know if you are still experiencing an issue.
Hello @Oli - Kinde Thank you for looking into the issue. However, I am still having the same issue after I upgrade my SDK to the newest version. It works find in my local tho... I have double check a few times of my Vercel setting, they are all correct... not sure where it went wrong
![No description](https://cdn.answeroverflow.com/1265398551958126664/image.png)
Hey @summer_teng,
My team mate is looking into this issue.
Apologies for the inconvenience.
Hey @summer_teng sorry you're having this issue 😦 my hunch is using
permanentRedirect
instead of redirect
my fix the problemHey @summer_teng,
It seems like you are having a similar issue to a customer who posted in our Slack community here.
@Peter (Kinde) - sent the attached video to the Slack community customer to explain the issue and a workaround to fix the issue.
Are you able to review the video and see if Peter's explanation fixes your issue?