OttoHollmann

I had the same problem, but it was resolved after setting proper `overwrite.cli.url`. Are you sure, that your server is running on `http://example.com`? Should it be rather `https://example.com`? Where you...

Just add following line into your config file: ` 'overwrite.cli.url' => 'https://example.com',` this address must be resolvable and reachable from machine where your nextcloud is running. Theoretically it could be...

I'm interested in this issue, but it looks similar to #159. Can you please explain me where is difference between these issues?

I rebased branch and added test and documentation. Unfortunately I don't know how to determine in perl if OCSP responder is ready so that's the reason why there is no...

Thank you for the confirmation. Yes, you’ve understood it correctly. I’d like to use the camera’s motion detection (since it offers advanced motion settings with hardware acceleration) and run Agent...

Thank you for asking. I haven’t had much time, and I also got a little bit stuck with parsing events, but it should be resolved now. I’ve just created a...

Is there any update on this issue? I'm experiencing the same problem. I'm running both Home Assistant and Go2RTC in docker, and while I can access the streams directly through...

Thank you for the suggestion! I found that the issue was caused by a misconfigured Nginx. I initially had only these two location blocks: ``` location / { ... }...

Sorry for the confusion — I was referring to the NGINX configuration for Home Assistant. I had only enabled the `api/websocket` endpoint, but for WebRTC to work, you need to...