Frigate records clips but webserver cannot playback H265 clips

[TheSleepySlee]

Hi

Just switched to -rc1, however was facing issue before too.
Frigate works really great, and the new webserver UI is awesome.
However, I'm having issues because there seem to be a link problem between events and their videos.

Before installing rc1, I cleaned my complete media folders.
When I go the the webserver UI, all the events are displayed, and their associated thumbnails.
However impossible to play videos (whether they are H264 or H265).
If I look in my media folders manually, looking for the filename associated with the event ID, I can play the video fine using VLC.
I'm using NFS on local server to store frigate media.

What should I go to investigate this? Picture attached

[blakeblackshear]

What errors do you see in the browser logs?

[TheSleepySlee]

root@f2bb45ca7f05:/opt/frigate# ls -lah /media/frigate/clips
total 7.0G
drwxr-xr-x 3 root root   44K Jan 23 13:44 .
drwxr-xr-x 4 root root  4.0K Jan 22 23:28 ..
drw-r--r-- 2 root users 4.0K Jan 19 18:16 @eaDir
-rw-r--r-- 1 root root   10M Jan 23 13:44 frigate.db
-rw-r--r-- 1 root root   16K Jan 19 15:55 garage-1611068103.682949-52dhkk.jpg
-rw-r--r-- 1 root root   19M Jan 19 15:55 garage-1611068103.682949-52dhkk.mp4

I will try what you suggest.

EDIT: recreated docker container, but no change.

New docker compose:

        - /opt/frigate/media:/media/frigate

New fstab:

192.168.0.100:/volume2/camera/frigate /opt/frigate/media nfs,user rw 0 0

New permissions:

root@8a140d92843d:/opt/frigate# ls -lah /media/frigate/clips
total 159M
drwxr-xr-x 2 root root 4.0K Jan 23 14:42 .
drwxr-xr-x 4 root root 4.0K Jan 23 14:32 ..
-rw-r--r-- 1 root root 440K Jan 23 14:42 frigate.db
-rw-r--r-- 1 root root  33K Jan 23 14:32 garageptz-1611408759.937055-due105.jpg
-rw-r--r-- 1 root root 8.7M Jan 23 14:33 garageptz-1611408759.937055-due105.mp4

New nginx logs:

root@8a140d92843d:/opt/frigate# cat /var/log/nginx/error.log |grep error 
root@8a140d92843d:/opt/frigate# cat /var/log/nginx/error.log            
2021/01/23 14:32:58 [warn] 20#20: *6 an upstream response is buffered to a temporary file /var/lib/nginx/proxy/1/00/0000000001 while reading upstream, client: 192.168.0.24, server: , request: "GET /api/garage/latest.jpg HTTP/1.1", upstream: "http:https://127.0.0.1:5001/garage/latest.jpg", host: "192.168.0.121:5000", referrer: "http:https://192.168.0.121:5000/"
2021/01/23 14:32:58 [warn] 20#20: *2 an upstream response is buffered to a temporary file /var/lib/nginx/proxy/2/00/0000000002 while reading upstream, client: 192.168.0.24, server: , request: "GET /api/z5/latest.jpg HTTP/1.1", upstream: "http:https://127.0.0.1:5001/z5/latest.jpg", host: "192.168.0.121:5000", referrer: "http:https://192.168.0.121:5000/"
2021/01/23 14:32:58 [warn] 20#20: *3 an upstream response is buffered to a temporary file /var/lib/nginx/proxy/3/00/0000000003 while reading upstream, client: 192.168.0.24, server: , request: "GET /api/portailcam/latest.jpg HTTP/1.1", upstream: "http:https://127.0.0.1:5001/portailcam/latest.jpg", host: "192.168.0.121:5000", referrer: "http:https://192.168.0.121:5000/"

[TheSleepySlee]

Here is swhat I have in JS console in chrome. Is that expected @paularmstrong ? thx

<video class="w-100" src="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/clips/japonais-1611732985.254579-un3x9b.mp4" controls=""></video>

[TheSleepySlee]

@paularmstrong @blakeblackshear I found the "bug". My cameras record H265, except one camera which is H264.
I can view the events & associated clips of the H264 camera just fine, but not all the other cameras.
Is that expected?
EDIT: changed title to reflect the actual issue.

[blakeblackshear]

h265 video is not well supported by browsers, so that is expected. Looks like they may play in Safari. https://caniuse.com/?search=hevc

[TheSleepySlee]

Tried in safari too, but with no luck. Need preview version.