starred/motioneye

Fork 0

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

Can't stream by IP address. Only by localhost #1721

New issue

Open

opened 2026-02-28 00:52:27 -05:00 by deekerman · 3 comments

deekerman commented

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

Owner

Originally created by @msmithGH on GitHub (Jul 20, 2020).

Hi,

Just installed MotionEye on Ubuntu 18.04 and love it so far. Have one issue though. I can access
http://localhost:8765 and http://localhost:808X
however going by local ip does not work. e.g. http://192.168.86.10:8765 and http://192.168.86.10:808X does not work (not from other machines on the network and not even from the server). I get "This site can't be reached. 192.168.86.10 refused to connect". I also installed Deepstack on the same machine and I can freely access http://192.168.86.10:5000 from any machine on the network and on the server itself.

I opened motion.conf and stream_localhost to off and webcontrol_localhost to off and restarted motioneye, but it didn't make a difference.

How would I get this to work?

Thanks

Originally created by @msmithGH on GitHub (Jul 20, 2020). Hi, Just installed MotionEye on Ubuntu 18.04 and love it so far. Have one issue though. I can access http://localhost:8765 and http://localhost:808X however going by local ip does not work. e.g. http://192.168.86.10:8765 and http://192.168.86.10:808X does not work (not from other machines on the network and not even from the server). I get "This site can't be reached. 192.168.86.10 refused to connect". I also installed Deepstack on the same machine and I can freely access http://192.168.86.10:5000 from any machine on the network and on the server itself. I opened motion.conf and stream_localhost to off and webcontrol_localhost to off and restarted motioneye, but it didn't make a difference. How would I get this to work? Thanks

deekerman added the

Stale No Activity 60 Days

label

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

deekerman commented

2026-02-28 00:52:32 -05:00

Author

Owner

@msmithGH commented on GitHub (Jul 20, 2020):

Well, I don't know what the real solution is, but I got it working by stopping the motioneye service and then installing the docker version. It picked up all my cameras and settings so I didn't need to reconfigure everything, so it all just worked.

Thanks!

@msmithGH commented on GitHub (Jul 20, 2020): Well, I don't know what the real solution is, but I got it working by stopping the motioneye service and then installing the docker version. It picked up all my cameras and settings so I didn't need to reconfigure everything, so it all just worked. Thanks!

deekerman commented

2026-02-28 00:52:32 -05:00

Author

Owner

@zagrim commented on GitHub (Jul 21, 2020):

I wonder if there's a difference in the default value of listen in /etc/motioneye/motioneye.conf... Anyway, setting listen 0.0.0.0 will bind MotionEye to all network interfaces, alternatively you might use listen 192.168.86.10 if you want to be very specific.

@zagrim commented on GitHub (Jul 21, 2020): I wonder if there's a difference in the default value of `listen` in `/etc/motioneye/motioneye.conf`... Anyway, setting `listen 0.0.0.0` will bind MotionEye to all network interfaces, alternatively you might use `listen 192.168.86.10` if you want to be very specific.

deekerman commented

2026-02-28 00:52:32 -05:00

Author

Owner

@ancris00 commented on GitHub (Aug 23, 2020):

after change motion.conf write sudo motion restart, then again sudo motion restart

@ancris00 commented on GitHub (Aug 23, 2020): after change motion.conf write sudo motion restart, then again sudo motion restart

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#1721

No description provided.

Rows
Columns