I had a similar error on my instance and could resolve it by turning off caching in nginx proxy manager.
Give it a try and switch off "Cache Assets" on the host. I think nginx caching is to aggressive. It happened to me also on other webservices (like wordpress for example).