cannot login after upgrading from 16.4 to 17.1

[joutain]

Hey not sure if anyone else have the similar issue as i am observing right now.

my frigate is running with Synology container manager with almost exact compose file with below but only the highlight enabled in the device section.

after upgrading to 17.1, i am seeing error being reported from the container manager, while at the same time, when i try to login, it gives me error as below. not sure the 127.0.0.1:5000/5001 is mandatory now? as synology use these 2 ports as default ones which can't be modified. is there anything i should change in the compose file to make the system working again?

Thanks!

2026-03-23 13:06:33.841669184 2026/03/23 13:06:33 [error] 211#211: *194 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"

2026-03-23 13:06:31.868202925 192.168.80.1 - - [23/Mar/2026:13:06:31 -0400] "POST /api/login HTTP/1.1" 502 559 "https://192.168.1.12:8971/login" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36 Edg/146.0.0.0" "-" request_time="0.000" upstream_response_time="0.000"

[inkeep-ai-assistant[bot]]

The error you're seeing indicates that Frigate's internal nginx is trying to connect to port 5001 for authentication but the connection is being refused. This is an internal port conflict issue on your Synology NAS.

Frigate uses these ports internally: (1)

• Port 8971: Authenticated UI and API access (for external/reverse proxy use)
• Port 5000: Internal unauthenticated UI and API access (intended for use within the docker network)

The error message shows nginx trying to reach http://127.0.0.1:5001/auth which suggests an internal authentication service isn't starting properly. Since Synology uses ports 5000/5001 by default for DSM, there may be a conflict even though these are internal container ports.

Possible solutions:

1. Check if the container is fully starting - The curl: (22) The requested URL returned error: 500 suggests Frigate's internal services may not be initializing correctly. Check the full container logs for startup errors.

2. Ensure you're accessing via port 8971 - You should be connecting to https://your-nas-ip:8971 for the authenticated interface. (2)

3. Verify your port mappings - Your compose file shows "8971:8971" which is correct. Make sure there are no conflicts with other containers.

4. Check for database or config issues - After a major version upgrade, there may be migration issues. Look for errors in the logs related to the database at /config/frigate.db. (3)

5. Try resetting the admin password - Add this to your Frigate config.yml and restart: (2)

auth:
  reset_admin_password: true

The 502 error on login suggests the backend authentication service isn't responding, which points to a startup problem rather than a port mapping issue.

📚 Sources:

1. Installation
2. Authentication
3. Advanced Options

---

Have another question? Just tag @inkeep.

[hawkeye217]

You'll want to read the breaking changes in the 0.17 release notes. One common symptom of Frigate not completely starting is related to the detect resolution for your cameras.

[joutain]

just saw that after posting, it's in the discussion category, earlier searching the issue space, didn't find anything. thanks! fixed after enforcing the resolution