Hello,
Latest BlueCherry 3 installed and working great in the web UI. However, only playback is functioning in the iOS client. Windows client works great. I can even play the live stream in Safari on my iPad, just not in the mobile app.
Server: Docker install. Ports 7001-7003 forwarded on the router to local ip of camera server.
Client: Latest release available from App store, running on an iPad air 4th Gen, on iOS 17. I am on the Public Beta of iOS 17. However, if this is related, you’ll have many more complaints when 17 is released to the public on Monday.
Thanks, I’ll test out iOS 17 and see if i can reproduce this.
Additionally you do not need port 7003 forwarded…I would suggest only port 7001-7002.
Good to know. I’ll close 7003.
I tested on an iPhone 11 with iOS 17 public beta just now and it works fine.
Does this affect only your iPad or do you have problems with an iPhone also?
I have not tried it with my iPhone.
Also, forgot to mention, we have an 8-port license with subdomain and full-SSL setup.
i’m going to download and try to login with my phone.
No change in behavior on my iphone.
Can you try connecting directly to the IP address instead of the DNS name?
Yes, I’ve tried that. Both the external IP from outside the LAN, and the internal IP from inside the LAN. No change in behavior.
Didn’t you have some strange networking issue in the past? Could that problem have resurfaced?
I can stream just fine using iOS 17 (21A329).
Which Bluecherry version 3 release build are you using? I am using beta 9
Beta 8. I didn’t realize Beta 9 was out.
Did you mean which version of Client or which version of Server?
Client is the latest released on the App store.
Server is the docker container. Latest as of about 3 weeks ago.
I just tried to update the docker containers again, and am again getting the notice that my server is unlicensed.
I just opened up SSH. Will PM you shortly.
Disregard for now.
I just did a complete reload of the DVR docker subsystem. Original OS is still in place, but I archived the old DVR files and redownloaded them with your install script.
Will re-test soon.
It still doesn’t function on the mobile app. I’m wondering if it has anything to do with having 2 DVRs?
We have 8 Coax Cameras with 640x480 resolution connected to a Proprietary DVR box. That DVR box has a GigE port, and I connected it to a GigE switch, along with the Bluecherry box. The Camera streams are all the RTSP streams coming from the Main DVR.
I hope this sheds some light on the issue.
I PM’d you, Curtis, with the login info for the WebUI. Perhaps that’ll get you some kind of inside look at the streams.
docker compose logs produces umteen screenfulls of:
bc-mysql | 2023-09-23T04:06:48.647365Z 5635 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:06:58.647477Z 5636 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:07:08.657132Z 5637 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:07:18.650436Z 5638 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:07:28.649042Z 5639 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:07:29.028974Z 5640 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:07:29.028985Z 5641 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:07:38.648747Z 5642 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:07:41.901402Z 5643 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:07:48.645293Z 5644 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:07:57.523602Z 5645 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:07:58.649688Z 5646 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:08:08.647044Z 5647 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:08:10.498662Z 5648 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:08:18.660620Z 5649 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:08:28.663086Z 5650 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:08:29.024732Z 5651 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:08:29.024738Z 5652 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
bc-mysql | 2023-09-23T04:08:38.647023Z 5653 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ‘‘mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’
Output of 'docker logs bc-server":
bc-server.log (76.5 KB)
Hmmm. I had forgotten that I have an old AMD 6570 card installed. It seems that every reboot, the built-in Intel graphics and AMD add-on randomly switch between /dev/dri/renderD128 and /dev/dri/renderD129. Although both are passed via docker-compose.yml, I have no way of manually selecting /dev/dri/renderD129 , and if I choose autodetect, it always chooses D128, even when D129 is the correct choice.
As a temporary work-around, I have manually mapped /dev/dri/renderD129 on the host to /dev/dri/D128 in the container.
I am now back to the original behavior - it works on Windows client and in Safari browser, but not in iOS client, as first reported.
Log files above are retained for completeness, but understand they were the result of using the wrong vaapi device.
Still getting occurrences of this in the logs:
rsyslogd: pidfile ‘/run/rsyslogd.pid’ and pid 10 already exist.
If you want to run multiple instances of rsyslog, you need to specify
different pid files for them (-i option).
rsyslogd: run failed with error -3000 (see rsyslog.h or try You searched for error 3000 - rsyslog to learn what that number means)
Not sure if that is relevant.
Also, docker host time is localtime, but docker client seems set in GMT.
I noticed in the compose file that $TZ gets passed to the client environment, however, ‘echo $TZ’ yields a null output on the host.
Not sure if the previous 2 items are related. Wouldn’t surprise me though.
Host environment is Debian 12.
Any way to sync DVR time to my actual Timezone.