Please follow the below template, it will help us to help you!
If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.
Expected Behaviour:
Using Raspberry Pi 4 with 4gb ram, 32gb micro SD
-operating system Raspberry pi Debian released 2021-05-07
Actual Behaviour:
Try to modify block or allow list and get error: Error, something went wrong!
Session expired! Please re-login on the Pi-hole dashboard.
pihole
Your debug log looks normal, showing your Pi-hole to be fully operational, receiving, filtering and answering DNS:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] go.rainn.org is 0.0.0.0 via localhost (127.0.0.1)
[✓] go.rainn.org is 0.0.0.0 via Pi-hole (10.0.0.2)
[✓] doubleclick.com is 142.250.69.206 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: contents of /var/log
-rw-r--r-- 1 pihole pihole 18412 Jun 15 15:56 /var/log/pihole-FTL.log
-----tail of pihole-FTL.log------
[2021-06-15 15:56:17.339 576M] Imported 284 queries from the long-term database
[2021-06-15 15:56:17.339 576M] -> Total DNS queries: 284
[2021-06-15 15:56:17.339 576M] -> Cached DNS queries: 65
[2021-06-15 15:56:17.339 576M] -> Forwarded DNS queries: 190
[2021-06-15 15:56:17.339 576M] -> Blocked DNS queries: 4
[2021-06-15 15:56:17.339 576M] -> Unknown DNS queries: 25
[2021-06-15 15:56:17.339 576M] -> Unique domains: 62
[2021-06-15 15:56:17.339 576M] -> Unique clients: 4
[2021-06-15 15:56:17.339 576M] -> Known forward destinations: 2
It also shows you've replaced Pi-hole's webserver lighttpd with apache2.
Your observation may be related to disallowing or incorrectly handling session cookies, either in your client browser or in your chosen webserver.