[Support]: CORS and 502 errors when retrieving .ts files #11104
Replies: 1 comment 1 reply
-
|
The removal of CORS was due to security reasons, I believe a CSRF token can be used 8657688 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for this answer, we have solved the issue about the CORS. The second error was about the 502 Bad Gateway. After doing some testings, we have noticed that this error only happens when trying to load the .ts files which are sent back in the m3u8 but only if this m3u8 content tries to load .ts files which target the last hour of recording. Any recordings older than 1 hour will load but as soon as you try to load a recording section, even if it's 59mins old, it won't do it. Hope you understand what I mean? Many thanks |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
Good morning,
We have an issue when trying to use the following API route:
GET - /vod/camera_name/start/start-timestamp/end/end-timestamp/index.m3u8
In order to consume this m3u8 stream using our Angular code, we add the full path before each .ts segment (see attached).
The m3u8 file comes back correctly with a 200 but when trying to play the segments, we receive the following errors :
We are already using the 0.12 version and this mechanism used to work perfectly, since the upgrade to version 0.13.2-6476f8a, it fails.
Version
0.13.2-6476f8a
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
No response
Operating system
Debian
Install method
Docker Compose
Coral version
CPU (no coral)
Network connection
Wireless
Camera make and model
N/A
Any other information that may be helpful
m3u8 file content:
Beta Was this translation helpful? Give feedback.
All reactions