Amcrest cameras - container error messages

[dpgator33]

When using the "base" docker compose file, I can get my cameras to show up in Protect, but they cannot show "live" video. It wasn't until after I noticed this that I noticed there were vendor specific compose files, so I used the ones for Amcrest cameras, but my containers bomb out and just keep restarting.

Every time I run docker-compose, these errors show up. I've tried using/removing different switches, but nothing is working so far. proxy-2_1 | Traceback (most recent call last): proxy-2_1 | File "/usr/local/bin/unifi-cam-proxy", line 8, in proxy-2_1 | sys.exit(main()) proxy-2_1 | File "/usr/local/lib/python3.8/site-packages/unifi/main.py", line 116, in main proxy-2_1 | cam = klass(args, logger) proxy-2_1 | File "/usr/local/lib/python3.8/site-packages/unifi/cams/dahua.py", line 15, in init proxy-2_1 | super().init(args, logger) proxy-2_1 | File "/usr/local/lib/python3.8/site-packages/unifi/cams/base.py", line 48, in init proxy-2_1 | self._ssl_context.load_cert_chain(args.cert, args.cert) proxy-2_1 | FileNotFoundError: [Errno 2] No such file or directory

My docker-compose is as follows:

version: "3.9" services: proxy-1: restart: unless-stopped image: keshavdv/unifi-cam-proxy volumes:

• "./client.pem:/client.pem" command: unifi-cam-proxy -H x.x.x.x -i x.x.x.x -c client.pem -t BZulnxKYgtxwXbb8qqhpbRTEOnCXgmMa amcrest -u admin -p xxxxxxxxxxx --motion-index 0 --snapshot-channel 1 --ffmpeg-args='-c:a copy -c:v copy -bsf:v "h264_metadata=tick_rate=30000/1001"' proxy-2: restart: unless-stopped image: keshavdv/unifi-cam-proxy volumes:
• "./client.pem:/client.pem" command: unifi-cam-proxy -H x.x.x.x -i x.x.x.x -c client.pem -t BZulnxKYgtxwXbb8qqhpbRTEOnCXgmMa amcrest -u admin -p xxxxxxxxxx --motion-index 0 --snapshot-channel 1 --ffmpeg-args='-c:a copy -c:v copy -bsf:v "h264_metadata=tick_rate=30000/1001"'

Model is IP5M

[0dragosh]

I have the exact same error no matter what cameras I try to use.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.