Closed Obezyana33 closed 2 years ago
Exactly @Obezyana33 we will overcome this issue in Open Source v3. Thanks for reporting your solution!
When can we expect v3? ;-)
Q1 - January we will make our first stable release. So not very soon, but it will be an amazing improvement. That’s for sure.
On 14 Jul 2021, at 07:14, Obezyana33 @.***> wrote:
When can we expect v3? ;-)
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kerberos-io/kerberos-docker/issues/36#issuecomment-879597155, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALZUGYDZUDAKXRKAESWL33TXUMLJANCNFSM5AKV6DJQ.
Very much looking forward to it!
Intro:
I am a subscribed member, with seven cameras currently streaming to kerberos-cloud. I use Podman on RHEL8, with SELINUX enabled.
Issue:
When I configure a single camera and map internal port 8889 to external port 8889, I am able to both see the stream on http://SERVER:8889 and via the Dashboard screen of the web app.
eg. (stream works on port 8889 and in Dashboard)
BUT when I set the streaming port to something else (eg. 8885), I am able to see the stream on http://SERVER:8885, but the stream never loads on the dashboard:
eg. (stream works only via port 8885)
This issue will affect anyone with more than one camera, who is separating container access by port (as per the documentation).
Workaround
I found that if persistent storage has been configured, then the following workaround can be used:
/etc/opt/kerberosio/config/stream.xml
configuration file is modified as follows: