[SOLVED] 403 when accessing GraphQL API

Bugs Solved Bugs
1

I have…

  • [ ] Checked the logs and have uploaded a log file and provided a link because I found something suspicious there. Please do not post the log file in the topic because very often something important is missing.

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

GraphQL requests return 403.

Expected behavior

No 403 :slight_smile:

Minimal reproduction of the problem

Our graphQL requests return 403 errors like the following for most requests on various clients):

{
  "type": "https://tools.ietf.org/html/rfc7231#section-6.5.3",
  "title": "Forbidden",
  "status": 403,
  "traceId": "00-cb39f46fe654ed42b58b9644fd898575-74ec8866c70a2146-00"
}

It doesn’t matter whether we access the API via the CDN or directly.

Environment

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

Version: latest cloud

Browser:

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

It affects our development and production clients and broke from one minute to the next - I cannot say when exactly but my guess is it started maybe 1 hour ago (that’s at least when I saw it first on a dev version and started to check my in-development code for errors before finding out, that it also affects the live version).

3

What permission do you use?

4

We are using the Reader permission on all clients.

5

I will provide a fix asap.

1 Like
6

Lovely! Can you afterwards (whenever you have time, no need to hurry) let us know what broke? I’m interested in that kind of things. :slight_smile:

7

I have rolled back the last deployment. It should hopefully work again.

1 Like
8

It looks like it works again, many thanks! :pray:

9

I have deployed the final fix.

10

@Sebastian unfortunately we are starting to see 403s again. :frowning:

11

Fuck, do you use the GET or POST endpoint?

12

Sorry for the late reply - we are using GET.

13

I think it has been fixed, can you approve that?

1 Like
14

Works like a charm, many thanks!

1 Like
15

Sorry for the inconveniences. Rough days.

16

No worries, happens to the best. :sweat_smile:

1 Like
17

This topic was automatically closed after 2 days. New replies are no longer allowed.