starred/motioneye

Fork 0

mirror of https://github.com/motioneye-project/motioneye.git synced 2026-03-02 22:57:06 -05:00

Running on port 80 alongside apache? #810

New issue

Closed

opened 2026-02-28 00:27:58 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-28 00:27:58 -05:00

Owner

Originally created by @dragonflyuk on GitHub (Apr 25, 2018).

Is there anyway to have MotionEye work in a web subdirectory, so the address would be something like http://raspberrypi.local/cctv

I already have it working on port 80, but I really need it working alongside an apache install on the same port, so that both can be accessed from dataplicity?

Originally created by @dragonflyuk on GitHub (Apr 25, 2018). Is there anyway to have MotionEye work in a web subdirectory, so the address would be something like http://raspberrypi.local/cctv I already have it working on port 80, but I really need it working alongside an apache install on the same port, so that both can be accessed from dataplicity?

deekerman

2026-02-28 00:27:58 -05:00

closed this issue
added the
invalid

question
labels

deekerman commented

2026-02-28 00:28:01 -05:00

Author

Owner

@ccrisan commented on GitHub (Apr 26, 2018):

This is not a valid motionEye issue. Please look for help on Apache docs/forums.

@ccrisan commented on GitHub (Apr 26, 2018): This is not a valid motionEye issue. Please look for help on Apache docs/forums.

deekerman commented

2026-02-28 00:28:01 -05:00

Author

Owner

@dragonflyuk commented on GitHub (Apr 26, 2018):

Not really, how can I change where motion eye responds to, i.e cctv subdirectory instead of root?

@dragonflyuk commented on GitHub (Apr 26, 2018): Not really, how can I change where motion eye responds to, i.e cctv subdirectory instead of root?

deekerman commented

2026-02-28 00:28:01 -05:00

Author

Owner

@ccrisan commented on GitHub (Apr 26, 2018):

@dragonflyuk it's up to Apache to route requests coming to e.g. /your/cams/path to motionEye's "root". Running Behind Nginx might help.

@ccrisan commented on GitHub (Apr 26, 2018): @dragonflyuk it's up to Apache to route requests coming to e.g. `/your/cams/path` to motionEye's "root". [Running Behind Nginx](https://github.com/ccrisan/motioneye/wiki/Running-Behind-Nginx) might help.

deekerman commented

2026-02-28 00:28:02 -05:00

Author

Owner

@dragonflyuk commented on GitHub (Apr 28, 2018):

Thanks @ccrisan that works perfectly, I can actually do all I need with nginx.

@dragonflyuk commented on GitHub (Apr 28, 2018): Thanks @ccrisan that works perfectly, I can actually do all I need with nginx.

deekerman commented

2026-02-28 00:28:02 -05:00

Author

Owner

@ccrisan commented on GitHub (Apr 28, 2018):

@dragonflyuk I know :) Nginx kind of rules.

@ccrisan commented on GitHub (Apr 28, 2018): @dragonflyuk I know :) Nginx kind of rules.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/motioneye#810

No description provided.

Rows
Columns