Closed debu99 closed 3 years ago
I think this is caused by kong reload
I think this is caused by kong reload
Yes, most definitely by that. The reload
is problematic in many ways. E.g. you cannot pass environment vars and it is hard to see what was passed previously.
Hello @debu99 could you try with kong 2.1.4
yes, already updated for 1 day, let's monitor for 1 week
@debu99 How is it looking? Did the update solve the problem?
thanks,looks okay, we can close the issue
We got this error after upgrade to 2.1.3 from 2.0.4