[Support]: WS Error from Frigate Proxy into Frigate #13857
Unanswered
JoshuaSeidel
asked this question in
General Support
Replies: 1 comment
-
this is showing that the http upgrade is not supported by / not enabled by the client, so a websocket connection could not be opened. This is not a frigate bug and the issue does not fall on frigate. We've not had any reports of websocket not working with the proxy addon so I am not sure if that is the client being referred to here, but in any case this should likely be debugged for whatever client is used here. The snapshot / video behavior also wouldn't be related to this |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Checklist
Describe the problem you are having
Ive been having troubles with notifications on iOS18 they wont display snapshots or clips most of the time, sometimes frigate doesnt even have the images its referencing, sometimes it does. while troubleshooting i noticed the errors in frigate proxy and then coorisponding errors in frigate and i wonder if they are connected to my issue. this is with the /ws endpoint
Steps to reproduce
...
Version
0.14.1-f4f3cfa
In which browser(s) are you experiencing the issue with?
Google Chrome 127.0.6533.122
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
Operating system
Debian
Install method
Docker Compose
Network connection
Wired
Camera make and model
reolink
Screenshots of the Frigate UI's System metrics pages
n/a
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions