Kong v 1.4.0 - Getting 504s when adding plugin to route via REST (SOLVED)

Questions
1

504 when adding plugin to route via REST
Wondering if anyone else is hitting the issue too?

This takes forever via curl and also used konga GUI to test the same thing, adding a plugin to an existing route is actually working, however the response is always a timeout, and so I have to add plugin, let it time out, move on to the next one. Kong is using DB and is running in docker. Same issue is not apparent in kong 1.3x

eg

curl -s -X POST https://kong-admin/routes/{route id}/plugins
-H ‘Content-Type: application/json’
-d ‘{
“name”: “acl”,
“service”: {“name”:“web-adapter”},
“route”: {“name”:“webcheck-route”},
“config”: {
“hide_groups_header”: false,
“whitelist”: [
“endpoint_A”
]
},
“enabled”: true,
“run_on”: “first”
}’

2

Hi @england_2022,

Do you have the same issue we are discussing here?

3

What DB are you using?

4

Can you try to turn this off:

e.g. with KONG_ANONYMOUS_REPORTS=off

5

We are using DB-Less

6

I’ve been hit by this problem a number of times myself but have not been able to figure out the root cause (yet).

7

thank you yes,
KONG_ANONYMOUS_REPORTS=off has done the trick for me.

8

@bungle What is the underlying issue here? Failure to connect to reports server?

9

After 1 day with these change i confirm we have still 504 errors in some particular routes.

10

We used to use udp and failure on that well… wasn’t that fatal as now when we changed to tcp. So the fix was to use timer (which we should have had in a first place). The issues is about connecting to reports server, yes.