Hi Danny,
Thanks for getting back. There aren't any error or messages as such. Firefox displayed these warning messages:
Thanks for getting back. There aren't any error or messages as such. Firefox displayed these warning messages:
- Cookie “TS016991b1” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite
- This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see https://firefox-source-docs.mozilla.org/performance/scroll-linked_effects.html for further details and to join the discussion on related tools and features!
None of them seems to be related. I was monitoring the memory usage of the server when I load the problems in the Library Browser, it did not go unusually high. I have set the
Also, the test instance, which is locally hosted and is not behind our proxy, is also rendering the problems a bit slow. It looks like this issue has nothing to do with moving the site behind our NGINX proxy.
MaxRequestWorkers
value to 40 since I have 8 GB RAM. Should I change this value?Also, the test instance, which is locally hosted and is not behind our proxy, is also rendering the problems a bit slow. It looks like this issue has nothing to do with moving the site behind our NGINX proxy.
Any suggestions would be appreciated!
Thank you,
Harshal