Is this being triggered simply by the web interface attempting to use an old token from the previous session, the portal rejecting it, and then my new fresh login (which it accepts) creates a new token that isn’t logged?
Just wondering if ya’ll see this .
Otherwise maybe some parasite on my PC I use to access my webportal/truenas is making it’s own attempts?
I hope you have found your answear, but I was recently bugged with the same question and I have came to the conclusion that is has to do with the fact that I navigate to my server via bookmark in browser that probably tries to access old session and therefore results in the error everytime before my login.
