MichaIng

Thanks, the error trace from the browser console should do to find the issue. I'll have a look into it.

Yes, URLs with embedded credentials are not even supported by modern browsers when present in the HTML document. In this case, when it is processed in the backend, this might...

This is something which needs to be done at host level, hence is outside of the possibilities of the container image. But we could create a little script to get...

PR open to disable the `motion.service` automatically: #2980 Closing this, since you fixed it for yourself already.

Just to be sure: This is really only for Raspberry Pi and software which uses the legacy RPi camera API while the modern libcamera driver/API + KMS is enabled, right?...

Many thanks, makes perfectly sense. This actually makes `target_dir` obsolete, and using a sub directory anyway did never work with S3 as only a bucket and an object name can...

motionEye does support motion v4.4, which is why this change was done: https://github.com/motioneye-project/motioneye/pull/2462 Did you run into any specific issue with latest motion and motionEye? Probably we missed migration for...

You mean a simple MJPEG stream? That is not passed through motion at all, is it? Or do you mean an RTSP or RTMP stream? In this case you should...

Does the URL to the network camera start with `rtsp://` or `rtmp://`? Because only in this case the width/height from the resolution input is used, otherwise it is ignored (not...

So as expected no resolution/width/height is defined at all. With motion 4.5.1, when accessing the stream directly at port 8081 has 640x480 resolution applied as well, or is it full...