@Soenke can you provide some more information on how the error is being produced? What’s the code/action/setup of your Xano request. That error is not very helpful to diagnose where the issue is. Screenshots are very helpful also.
we take a look at your project, and apparently you had a infinite loop of redirection to the login page. So you overflood Xano with requests, which was causing the issue.
We fixed your checkUser workflow with a filter, so that you do not loop on the login page.
We take note on this problem (you are not the only one) and we will probably add a security so this can’t happen.
Regarding the periodic 502 error I discovered that some of the Xano API calls response headers do not comply with CORS. In detail the “Access-Control-Allow-Origin: *” parameter is missing in the response header. Strange thing is that the response is sometimes CORS compliant and sometimes not
Thats indeed strange. Can you check on Xano side why this behavior is happening? You will probably not being able to fix it by yourself as it is on Xano/server hands.
If you manage to find why can you get back to us ? If there is something on our side, i will be happy to help, but here it seems to be a server issue.
Hi @codage to be honest I cannot really tell you how the issue was solved in my case. I exchanged a couple of emails with the Xano team and Michael and his team investigated. Was tricky. Then suddenly the error did no longer appear A bit strange but until now everything runs smoothly
I suggest that you contact the Xano support. They were really supportive. I recorded a loom video showing the error which helped them to understand the problem.