- [ x ] Checked the logs and have provided the logs if I found something suspicious there
I’m submitting a…
- [ x ] Regression (a behavior that stopped working in a new release)
- [ ] Bug report
- [ ] Performance issue
- [ ] Documentation issue or request
Tried to run basic query on existing schema in the graphql ui getting 502 Bad Gateway result.
query to return data records
Minimal reproduction of the problem
I’m unsure how to reproduce it as some of the queries are working and some don’t.
Even in the sample query above, some fields are not working but if we removed those fields the query works. That same working query after sometime stopped working. Very hard to track what’s going on. We haven’t make any changes to the schema or the data since the version 4.3 from 4.0.3 upgrade.
I took the backup of the app and restored it in my local docker as fresh copy and the query seems to be working. Also on the problem app, there is no error logs or anything that make sense comes out of it.
I just like to check if anyone ever experience this kind of 502 error in squidex or know any possible cause of it?
- [ x ] Self hosted with docker
- [ x ] Chrome (desktop)