Hi, I have update Supertokens core to 5.0 and upda...
# support-questions-legacya
amirnoorani
05/26/2023, 10:23 PMHi, I have update Supertokens core to 5.0 and updated supertokens-node to 14.1.1 (latest)
but when I try to login it says SOMETHING_WENT_WRONG_ERROR with error 500
Node express backend log:
Copy code
data: { error: 'invalid_grant', error_description: 'Bad Request' }
POST /auth/signinup 500r
rp_st
05/27/2023, 5:28 AMhey @amirnoorani this usually happens if there is a misconfig in the redirect uri.
It can also happen if this API is being called twice - are you using custom UI in react?
a
amirnoorani
05/27/2023, 5:31 AMBefore updating to core 5 everything worked fine.
No I'm using nextjs with PrebuiltUI.
I'll check the redirect url and let you know
r
rp_st
05/27/2023, 5:32 AMthis error has nothing to do with the core.
rp_st
05/27/2023, 5:32 AMare you using our pre built UI?
rp_st
05/27/2023, 5:32 AMand are there two POSTs requests going to
/auth/signinuprp_st
05/27/2023, 5:32 AM(please share a screenshot of the network tab on chrome)
a
amirnoorani
05/27/2023, 5:32 AMYes I'm using prebuilt UI
amirnoorani
05/27/2023, 8:58 AMhttps://cdn.discordapp.com/attachments/1111781572685860955/1111941414507520031/image.png▾
https://cdn.discordapp.com/attachments/1111781572685860955/1111941414918553660/image.png▾
r
rp_st
05/27/2023, 9:01 AMi mean the network tab - so all the network requests on chrome
a
amirnoorani
05/27/2023, 9:06 AMhttps://cdn.discordapp.com/attachments/1111781572685860955/1111943566957215854/image.png▾
amirnoorani
05/27/2023, 9:18 AM Copy code
Request URL:
https://dl.dizzland.com/auth/signin
Request Method:
POST
Status Code:
500 Internal Server Error
Remote Address:
185.141.107.191:443
Referrer Policy:
strict-origin-when-cross-origin
Access-Control-Allow-Credentials:
true
Access-Control-Allow-Origin:
https://www.dizzland.com
Access-Control-Expose-Headers:
Content-Disposition
Connection:
keep-alive
Content-Length:
144
Content-Type:
text/html; charset=utf-8
Date:
Sat, 27 May 2023 09:15:59 GMT
Etag:
W/"90-YO9NUeRxS59V3MBQMHe6TVyAfpA"
Server:
nginx/1.18.0 (Ubuntu)
Vary:
Origin
X-Powered-By:
Express
Accept:
*/*
Accept-Encoding:
gzip, deflate, br
Accept-Language:
en-US,en;q=0.9,fa-IR;q=0.8,fa;q=0.7
Connection:
keep-alive
Content-Length:
104
Content-Type:
application/json
Cookie:
sAccessToken=eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsInZlcnNpb24iOiIyIn0%3D.eyJzZXNzaW9uSGFuZGxlIjoiMjRhN2M2M2YtYzOP9oJ7FRuez0dHV2xj8xAuHqhVwm1%2BIziz3GVuWdbRqn2fWWHj47rknOPNp7dA94MmXAI9cLtLtYoKCJVZH%2FUdLcSjL%2FITh%2Fpy5EPA3qTtRBrhaGj8fQNf2T05m9MU8dP7YZAN0E5C577kSV51jMRoVlht5Lx9GFvUMt8z8TRNK8Jby4WUViMWvdlDStB3y%2Bg%3D%3D; _ga_S31STK5HWY=GS1.1.1685177959.46.1.1685178914.0.0.0
Fdi-Version:
1.16
Host:
dl.dizzland.com
Origin:
https://www.dizzland.com
Referer:
https://www.dizzland.com/
Rid:
thirdpartyemailpassword
Sec-Ch-Ua:
"Google Chrome";v="113", "Chromium";v="113", "Not-A.Brand";v="24"
Sec-Ch-Ua-Mobile:
?0
Sec-Ch-Ua-Platform:
"Windows"
Sec-Fetch-Dest:
empty
Sec-Fetch-Mode:
cors
Sec-Fetch-Site:
same-site
St-Auth-Mode:
cookie
User-Agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36r
rp_st
05/27/2023, 9:19 AMeven the refresh API is giving a 500..
rp_st
05/27/2023, 9:20 AMwhats the error stack on the backend when the refresh API is called?
a
amirnoorani
05/27/2023, 9:21 AMhttps://cdn.discordapp.com/attachments/1111781572685860955/1111947395173982238/image.png▾
r
rp_st
05/27/2023, 9:22 AMis the supertokens core running fine?
a
amirnoorani
05/27/2023, 9:22 AMshould I run any command to know?
r
rp_st
05/27/2023, 9:23 AMvisit the /hellp path of the core on your browser
a
amirnoorani
05/27/2023, 9:25 AMhttps://cdn.discordapp.com/attachments/1111781572685860955/1111948250929446982/image.png▾
r
rp_st
05/27/2023, 9:25 AMright. So im not sure why your backend is giving a 500
rp_st
05/27/2023, 9:25 AMcan you enable backend debug logs and show the output when refresh API is called?
rp_st
05/27/2023, 9:26 AMhave you added our supertokens error Handler to your backend?
a
amirnoorani
05/27/2023, 9:26 AMhow can I do that?
amirnoorani
05/27/2023, 9:26 AMlet me check
amirnoorani
05/27/2023, 9:27 AMapp.use(errorHandler());
amirnoorani
05/27/2023, 9:27 AMyou mean this?
r
rp_st
05/27/2023, 9:27 AMyea
rp_st
05/27/2023, 9:27 AMcan you enable backend debug logs and show the output when refresh API is called?
a
amirnoorani
05/27/2023, 9:28 AMHow can I enable debug logs?
r
rp_st
05/27/2023, 9:28 AMsee our docs please
a
amirnoorani
05/27/2023, 9:28 AMsure
r
rp_st
05/27/2023, 9:28 AMwould appreciate it you first see our docs and then ask 🙂
a
amirnoorani
05/27/2023, 9:28 AMsorry. I'll check it
amirnoorani
05/27/2023, 9:39 AMr
rp_st
05/27/2023, 9:40 AMit seems like the core is throwing an error.
rp_st
05/27/2023, 9:40 AMwhat happens when the refresh is called on the core side? Can you send me the core logs?
a
amirnoorani
05/27/2023, 9:49 AMI have enabled core debug mode. where can I find the logs?
r
rp_st
05/27/2023, 9:49 AMDocker logs
a
amirnoorani
05/27/2023, 9:49 AMwithout docker
r
rp_st
05/27/2023, 9:49 AMIf not using docker, then find logs in installation dir of the core
a
amirnoorani
05/27/2023, 9:50 AMOK
amirnoorani
05/27/2023, 9:57 AMr
rp_st
05/27/2023, 10:01 AMyou have upgraded to the latest core?
rp_st
05/27/2023, 10:03 AMyou need to run the migration steps. See the core changelog on our github. It has instrs on what migration commands to run for sql
a
amirnoorani
05/27/2023, 10:03 AMI have downloaded the latest linux core in zip file
r
rp_st
05/27/2023, 10:04 AMyea, but you are running it against a database that used to work with the older version of the core.
rp_st
05/27/2023, 10:04 AMSo you need to migrate
a
amirnoorani
05/27/2023, 10:04 AMSure
amirnoorani
05/27/2023, 10:04 AMThank you for your help
amirnoorani
05/27/2023, 10:04 AM👍👍
116 Views