motioneye-project/motioneye

Running behind Apache proxy

Open

#2,077 opened on Mar 26, 2021

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Python (636 forks)batch import
help wantedtroubleshooting

Repository metrics

Stars
 (3,533 stars)
PR merge metrics
 (Avg merge 16d 14h) (33 merged PRs in 30d)

Description

I'm trying to run motioneye behind an Apache reverse proxy. I've read quite a few issues on here as well as the wiki on nginx and Apache and I have the following configuration:

RewriteRule /doggycam$        /doggycam/               [R,L]
RewriteRule /doggycam/(.*)$   http://192.168.0.61/$1   [P,L]

This works relatively well. The web interface shows up and all the CSS and everything else loads fine as well. The only issue is that the video itself doesn't show. Looking at the dev console's network tab, I can see a request to http://mydomain:8081/?_=1616781429979 while everything else correctly requests from http://mydomain/doggycam/.

Why is the video the only thing that doesn't seem to work correctly and how can I fix it?

Contributor guide

Research direction
Investigate how motioneye constructs the video stream URL. Look for hardcoded host/port or missing base path handling. Check if there is a configuration option for reverse proxy base path.
Tech stack
pythonjavascript
Domain
backenddevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Apacheproxy configuration basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50