-
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Hello @caolijun1166, the first thing that draws my attention is that your kong version (1.4.3) is very old. A lot of problems on previous versions of the software have been solved in more modern versions. It might be that your problem gets solved by simply upgrading. That said, the second thing that is a bit surprising is that your logs don't seem to include any IP or port:
This makes me think that there is something wrong in your log configuration options. I would recommend leaving the default options for a while (even if you don't get JSON logs for those requests, you might get their IPs). Once you make the unknown clients "known" (by knowing their IP/Port) you can start thinking about solutions. Depending on what you see, you might decide to start using the IP restriction plugin. Another option might be setting a Service for the In short:
|
Beta Was this translation helpful? Give feedback.
Hello @caolijun1166, the first thing that draws my attention is that your kong version (1.4.3) is very old. A lot of problems on previous versions of the software have been solved in more modern versions. It might be that your problem gets solved by simply upgrading. That said, the second thing that is a bit surprising is that your logs don't seem to include any IP or port:
This makes me think that there is something wrong in your log configuration options. I would recommend leaving the default options for a while (even if you don't get JSON logs for those requests, you might get their IPs). Once you make the unknown clients "known" (by knowing their IP/Po…