Refer to Webserver.session.timeout - Help - Pi-hole Userspace
Not sure what has been changed in the recent updates for Pi-Hole Core, FTL and Web compared to the updates earlier in the year, but the issue i had raised back then regarding the webserver session timeout each time my instances synchronised from a source with nebulasync, has been resolved and is no longer occurring.
With updates released earlier this month, I had scheduled to auto-update all of my Pi-Hole instances (physical/source and virtuals/targets) in the last 2 nights to:
Core : 6.4 -> 6.4.1
FTL : 6.5 -> 6.6
Web : 6.4.1 -> 6.5
My source had auto-updated via a scheduled bash script 2 nights ago and my target instances updated last night.
After the targets had updated, I noticed that the version of Core and FTL differed from what I had seen the previous night when the source instance had updated.
I then checked the source instance showed that there were updates available for these components, so I updated it accordingly.
After updating, I decided to login to my target instances (Proxmox VMs) by their local IPs and DNS names as well as the keepalived VRRP IP and DNS name (in different browsers and incognito sessions) and watched as nebulasync (installed on a separate Docker VM in Proxmox) activated and successfully updated at the next 15min interval, and the next, and the next, ...
I also added local DNS and CNAME entries on the source several times and these were reflected on the targets each 15min.
Twelve hours on and counting, it seems to be holding and the web server session has not timed out.
Just thought Iād share this update after the original post was auto-closed after 21 days.
Keep up the great work on this fantastic product and project.