I’m implementing the new TS forest library with Nest.js.
Somehow, I had no issue today except for this afternoon.
The collections looks loaded but once I’m trying to access to those on the admin, it doesn’t load.
The authenticate is well made, callback as well, and collection’s routes are accessible.
When I take a look, there is no request made to fetch the data BUT when I create a graph on the dashboard, it works well.
This might be related to how the agent refreshes its cache. We are using SSE to notify the agent of a configuration change, allowing it to request the new set of permissions.
To validate this theory you can restart your agent, this will request our server for the latest permissions.
If this is indeed the cause, you can:
Disable buffering on your reverse proxy (nginx) by adding the following configuration
fastcgi_buffering off;
proxy_buffering off;
Disable via agent creation parameters the instantCacheRefresh by setting it to false
If this is indeed the root cause of your issue, I will take the time to work on a documentation and a mechanism to notify the user in the logs when we detect buffering on proxy level, I feel like more and more users are facing this.