[Bug]: Opening Frigate after session expires constantly reloads in a loop #21453
-
Checklist
Describe the problem you are havingWhen opening the site from either phone or desktop and the session has expired, the page goes into loop and it refreshes constantly. It also makes the phone browser (Firefox) not respond for awhile. Steps to reproduce
Version0.16.3 In which browser(s) are you experiencing the issue with?Firefox 146.0.1 & Safari 26.2 Frigate config fileIts not needed for the issue (will provide if needed)docker-compose file or Docker CLI commandfrigate:
image: ghcr.io/blakeblackshear/frigate:stable
container_name: frigate
restart: unless-stopped
shm_size: "512mb"
stop_grace_period: 30s
devices:
- /dev/dri/renderD128:/dev/dri/renderD128
volumes:
- /etc/localtime:/etc/localtime:ro
- /opt/silent/frigate/config:/config
- ${STORAGE_PATH}/frigate:/media/frigate
- type: tmpfs
target: /tmp/cache
tmpfs:
size: 1000000000
ports:
- "8554:8554"
- "8555:8555/tcp"
- "8555:8555/udp"
networks:
- defaultRelevant Frigate log outputNothing in the logs regarding thisRelevant go2rtc log outputNot neededOperating systemDebian Install methodDocker Compose Network connectionWired Camera make and modeltp-link Screenshots of the Frigate UI's System metrics pagesAny other information that may be helpfulNginx logs |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
Based on your nginx logs, the Frigate UI is receiving 401 responses from The authentication system in Frigate uses JWT tokens with configurable session lengths. The default session length is 24 hours (86400 seconds).(1) When a JWT token expires, API requests return 401 Unauthorized responses.(1) To adjust the session length and potentially reduce how often you encounter this issue, you can configure the auth:
session_length: 86400You can increase this value to extend how long sessions remain active before requiring re-authentication. For example, setting it to However, the redirect loop behavior you're experiencing appears to be a frontend handling issue where the UI isn't properly detecting the expired session and staying on the login page. This seems like a bug in how the UI handles the 401 responses from multiple API endpoints simultaneously. As a workaround until this is addressed, you could:
📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, this seems like the same race condition between a couple of Frigate's redirect mechanisms that was already fixed for Frigate 0.17, currently in beta. Here are the details of the commit: 0902e4b |
Beta Was this translation helpful? Give feedback.
-
|
Great, will wait for the update to go stable then. |
Beta Was this translation helpful? Give feedback.
-
|
No problem. The issues queue in this repo is for feature requests. Bug reports are in the discussions with the bug tag applied. |
Beta Was this translation helpful? Give feedback.
Thanks, this seems like the same race condition between a couple of Frigate's redirect mechanisms that was already fixed for Frigate 0.17, currently in beta. Here are the details of the commit: 0902e4b
It was originally reported in #21142 and fixed in #21141