core: Motioneye media browser not working via reverse proxy

The problem

My scenario involves an access to HA via https from nginx (reverse-proxy) which also does SSL offloading.

In this situation, if I access the MotionEye images via the reverse-proxy (https: //public.domain: 8xxx) I see the names of the files, but not the preview nor the photos themselves.

If instead I access it via internal IP (pure HTTP, http: //192.168.x.y: 8123) I see everything correctly.

What version of Home Assistant Core has the issue?

2021.12.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

motioneye

Link to integration documentation on our website

https://www.home-assistant.io/integrations/motioneye

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

About this issue

Original URL
State: open
Created 3 years ago
Comments: 21 (9 by maintainers)

Most upvoted comments

Still not implemented

chemelli74 on Jul 12, 2023

avoid stale

sibbl on Apr 12, 2023

It’s still a problem.

sibbl on Jan 12, 2023

avoid stale

chemelli74 on Apr 30, 2022

That’s right, or protect your motionEye instance behind an authenticated reverse proxy (that is accessible both internally and externally).

That’s not really safe as it doesn’t allow for MFA.

An easier solution, and what we use in Frigate, is to implement the proxying in the integration itself – but I didn’t implement that for motionEye.

Do you mind adding to your todo list ? 😉

Simone

chemelli74 on Dec 22, 2021