You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Several users encounter DataTables errors in the interface across all modules.
These errors do not appear in the internal app logs or through Sentry.
We have identified that the server returns inconsistent responses from the API container, leading to many 500 responses when there are no actual errors in the logs.
In the following example we receive status 200 (expected geojson data) or 500 (internal server error) when refreshing, even though nothing changed in between the requests and all responses should be status 200 with correct data.
The command docker compose restart api can be used to fix this, but the behavior is likely to happen again after some time.
Restarting nginx and emptying the web cache do not change this behavior, thus an internal problem in that container is suspected.
The text was updated successfully, but these errors were encountered:
Describe the bug
Several users encounter DataTables errors in the interface across all modules.
These errors do not appear in the internal app logs or through Sentry.
We have identified that the server returns inconsistent responses from the
API
container, leading to many 500 responses when there are no actual errors in the logs.In the following example we receive status 200 (expected geojson data) or 500 (internal server error) when refreshing, even though nothing changed in between the requests and all responses should be status 200 with correct data.
The command
docker compose restart api
can be used to fix this, but the behavior is likely to happen again after some time.Restarting
nginx
and emptying the web cache do not change this behavior, thus an internal problem in that container is suspected.The text was updated successfully, but these errors were encountered: