Intermittent failed fetch, seems a time out

Support
1

I have…

I’m submitting a…

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

Current behavior

Expected behavior

Minimal reproduction of the problem

Environment

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

Version: [VERSION]

Browser:

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

Others:
We have been seen a intermittent graphql end point error where the fetch fails and seem to time out.

image
image1754×224 62.5 KB

WE finally caught it in post man !!

has any one see this kind of thing before …

We cannot find any 504 in the error logs.

2

I sounds a little bit like this: [SOLVED] Surrogate-Key Can Create Header Overflow

I would check your frontend server (nginx or so)

3

Seb
We are using the docker azure image ver 5.
Thanks
Marcus

4

I know, but it could be a reverse proxy server as well…

5

We’re running it as a docker image in Azure App Service and this is also something we noticed when upgrading from version 4 to 5. Using graphql as well.

This graph shows response time before and after the upgrade:

image
image1928×808 99.5 KB

And now it’s always like this:

image
image1912×841 249 KB

It’s not really a huge problem for us because we mitigated it by instantly serving the most recent cached request in our frontend app service anyways.

6

You could turn on APM: https://github.com/Squidex/squidex/blob/master/backend/extensions/Squidex.Extensions/APM/ApplicationInsights/ApplicationInsightsPlugin.cs

Then have a look what takes time.