504 gateway timeout
We have started seeing gateway timeout responses when trying to fetch the token. This is impacting one of our product in production. We are seeing a new setting configuration and our production environment is tagged as "not live".
Can anyone help in getting this fixed?
Can anyone help in getting this fixed?
8 Replies
this issue seems to affect only our apps that are using email + password authentication. We have other apps using different authentication mechanism and those are working fine.
it also strangely only affects our production environment. Email + password authentication works fine on our dev env
Hi, thanks for reaching out! Could you let me know what other authentication methods your apps are using alongside email and password?
we have a total of 7 apps. All of them are using email + code. Except 2 apps that are setup with email + password. The one returning the 504 are setup with email + password only
I am now seeing a
Error: undefined token response when making a call with kindeClient.getToken()
I have also tried switching the authentication mechanism to email + code but that did not fix it. I am not sure if the issue related at all to the authentication mechanismCould you please ensure that Hasura mapping is disabled?
confirming that's disabled
Thanks for confirming! The 'undefined token response' usually happens when trying to retrieve a token before authentication is complete. Could you check if you're fetching the token only after authentication is successfully completed?
we actually make a call to get the token and if that fails we catch the exception and redirect to the login screen. So I think that error is expected in the console. Everything started working now, we made no changes
Confirming we are not seeing 504 responses anymore. It's good to see everything is working again. We made no changes on our end did you notice any issue on your end? I need to complete an internal incident report if you have any high level info to share.
Thank you for your prompt replies š
Thanks for the update! Great to hear that everything is working again. We havenāt made any changes on our end either, and we didnāt observe any issues that would have caused the 504 responses. It seems likely that this was a temporary issue rather than a persistent configuration problem.
I recommend keeping an eye on it and reaching out to us if you experience it again. If we come across any relevant details, Iāll be sure to share them for your internal report.
Let me know if you need anything else!