[OBSOLETE] Squidex API 500 errors

Bugs Solved Bugs
1

I’m submitting a…

[X] Regression (a behavior that stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Documentation issue or request

Current behavior

API Returns 500 errors

Expected behavior

Minimal reproduction of the problem

GET /api/content/modbenefitscalculatoruat/graphql HTTP/1.1
Host: mod-squidex-sandbox.cloudapps.digital
Content-Type: application/json
Authorization: Bearer eyJhbGciOiJSUzI1NiIsImtpZCI6IjkxRkRENEVCRDYwNjMxNURFREI4MENEMDkzMERFRkZBMjFEREE2NkIiLCJ0eXAiOiJKV1QiLCJ4NXQiOiJrZjNVNjlZR01WM3R1QXpRa3czdi1pSGRwbXMifQ.eyJuYmYiOjE1NTEzNjA2NjUsImV4cCI6MTU1Mzk1MjY2NSwiaXNzIjoiaHR0cHM6Ly9tb2Qtc3F1aWRleC1zYW5kYm94LmNsb3VkYXBwcy5kaWdpdGFsL2lkZW50aXR5LXNlcnZlciIsImF1ZCI6WyJodHRwczovL21vZC1zcXVpZGV4LXNhbmRib3guY2xvdWRhcHBzLmRpZ2l0YWwvaWRlbnRpdHktc2VydmVyL3Jlc291cmNlcyIsInNxdWlkZXgtYXBpIl0sImNsaWVudF9pZCI6Im1vZGJlbmVmaXRzY2FsY3VsYXRvcnVhdDpidWlsZC1zdGVwIiwic2NvcGUiOlsic3F1aWRleC1hcGkiXX0.mt6tIb83ASIxbw5YDrj5fMldaASpFZM1cwr5doyA1voisXWQh1p9tHfsgrrXQRpOF5tuwZfYdybhjvLH0tNTjkNayQtJKAaqSJAaN29pG2Wi8wsb0VPlDj2cwQ0FXd-KhOfttRmArJ4KLYnyVtd4vadRYkR2KvfJb-1mGJNO8WRrNkuS97INJ2kra0Iis1oCCG-uWWOwEAt-tiLSSOuxiAyBngepHTKciop1OD-pquPIpkGxG27J0si2vTdMOFznCTPBE9gVpM2uUBcHz6gx-VyjBkTfau3ggTn5dJqNL_ZzwM_gcrp1Xt87CxNTUunBt0JMVxGKCh3JuSmKcOroiQ
cache-control: no-cache
Postman-Token: 006c4e3a-bfff-49a7-a3e3-de836964e015

Environment

  • [ ] Self hosted with docker
  • [X] Self hosted with IIS
  • [ ] Self hosted with other version
  • [ ] Cloud version

Browser:

  • [ ] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge
  • [x] SERVER

Others:
This issue started today as I wanted to do a release and happened on our TFS servers.
I ran the api request locally and through postman and I’m also getting 500 errors.

2

Sorry, but what do you expect me to do with these information? I have no logs or so

3

Apologies Sebastian, does this not mean there’s an issue with the api?

Do you need more information from me to investigate?

4

500 always means that there is something wrong on the server. Could be IIS, database, squidex…so logs should help.

5

Closed due to inactivity.

6