CSRF token error

[PerpSearch]

On 1.7.1 with everything else updated as well. I am still getting the CSRF token error, but nothing reflected in admin/errors list.
I normally keep that tab in my browser open all the time (as in weeks/months).
I thought maybe that was the issue so I closed the tab, reopened it, and edited a record. I got the same CSRF token error.
I signed / logged out of the program and signed back in, attempted the same record editing and this time it no longer returned the CSRF error.
In my unskilled analysis, If I take too long between times when I access the program while logged in, or just try to stay logged in forever, it loses track of the users credentials or something like that and starts kicking the CSRF token error. I just can't leave a tab open and I'm probably good.

[nahoijtink]

Great tool, but ......

I also have token errors, i found that when the Koillection server is too busy to respond something causes a timeout on the browser. From that moment you either get the CSRF error if you are lucky, or the page isn't responsive any more and browser cached pages get loaded. Even restarting the Koillection container, keeping the browser open, the login is skipped entirely when the browser had an active session and is refreshed, and you might/will get a resend form error, which might be a security concern.

The CSRF error seems to be caused by slow(er) internet traffic. If i use IP's from local LAN ip-address to access Koillection, less problems and it seems to run pretty smooth, but when i use the duckdns.org domain. errors start happening.

I further noticed that having labels with the same name on the page when committing changes is very likely to cause the issue. The expected behaviour is that you get an error complaining that labels must be unique, but those errors do not (always) appear and in turn results in an unresponsive or CSRF error.

The browser i use is LibreWolf.

Hope this helps better troubleshooting the problems. Please note, all testing was done on LAN only, even if the resolve was done through duckdns.org while being on local LAN.

My Nginx Proxy Manager for resolving LAN hostnames is part of my Home Assistant install, so that might further complicate things regarding time-outs. As i said, when directly using the IP-address (and correct port) thing run way smoother.

Love the tool, keep up the good work !

[lopiv2]

I don´t know if this is related to, but i have similar bugs when accessing with a domain name, and not the IP Address and port. When i create an item scraping from any web, When you click submit, it should go to collection again and the new item should appears in the list, but instead that, it reloads the add item page, like if you click submit and add another item, and the item isn´t added to the collection, and no errors shown. With local IP and port, this doesn´t happen.

[PerpSearch]

I should add that I've only gotten the errors while using the direct local IP on my LAN rather than via the internet. That's not to say that I wouldn't, I just spend most of my time using it locally. And when I do start getting them, they don't stop until I log out and back in.