Constantly warning log: Satori configuration invalid

Runtime Framework
1

Hello,

We are constantly getting spammed with the warning log
‘Satori configuration invalid: api_key_name not set, api_key not set, signing_key not set’
on our Nakama server even though we are not using Satori. We aren’t using any Satori functions on the server side. Why are we receiving this log? How to fix that?

Nakama Server version : v3.17.1

1 Like
2

Hello @lgnozk,

Upgrading to the latest v3.18.0 release should prevent these logs from being written.

Best.

1 Like