motionEyeOS – Embed URL no longer accessible without authentication (now requires username/password)

[holzfelix]

Hello motionEyeOS team,
we are using motionEyeOS and embed the live stream / embed URL into an external interface. This worked without authentication until recently. Now, accessing the embed URL always triggers an authentication prompt (username + password), which breaks the embedding.

Issue:

Embed URL is no longer publicly accessible

Username and password are always required

iFrame / embedding no longer works

Expected behavior:

The embed URL should be optionally accessible without authentication (as before), e.g. via an anonymous viewer, unauthenticated stream, token-based URL, or a documented alternative for authenticated embedding.

Steps to reproduce:

Open motionEyeOS

Access the previously used embed/stream URL or load it in an iFrame

A login prompt (HTTP Basic Auth) appears

Context / notes:

This looks like a recent change in default security settings or a regression after an update or configuration change.

Please clarify whether there is a new setting to allow unauthenticated embeds or what the recommended approach is now.

Request:

Is this behavior intentional or a known change?

Which configuration or option is required to allow embed URLs without authentication?

If this is a security change: is there an official alternative (token-based embed, headers, cookies, etc.)?

Thank you for your support.

[Marijn0]

The motionEyeOS repository can be found here: https://github.com/motioneye-project/motioneyeos

However, this issue also exists in the recent releases of motionEye. Someone has already provided a temporary fix for this in the existing issue #2686.

[holzfelix]

I use it in docker. but it worked halfway ... I can now click on cancel and the video is shown.....

[zagrim]

Just to avoid any further confusion: The most recent release of MotionEyeOS is still from 2020 and I assume it does not have the changes that changed the authentication for embed URL (I think that was changed during of after of conversion to Python 3). So I guess this is indeed about MotionEye as such, not MEOS. One does not run MEOS in Docker, one writes it on a SD card and boots with it 😄

[MichaIng]

Closing this as duplicate.