Failed to connect to localhost port 8081: Connection refused - Docker install #2425

New issue

Closed

opened 2026-02-28 01:11:44 -05:00 by deekerman · 1 comment

deekerman commented

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

Owner

Originally created by @UKnau22 on GitHub (Aug 9, 2023).

I have MotionEye installed in Docker and an rtsp camera connected to it. Within MotionEye I can access the camera stream, save motion triggered events/movies to my NAS etc... Everything is working great.

When I try to access the stream through the streaming URL 192.xxx.x.xxx:8081 in any web browser the "ERR_CONNECTION_REFUSED" message comes up.

In HomeAssistant I can access the stream through port 192.xxx.x.xxx:8765, however when I tap on the picture entity card to expand the stream a broken link shows up.

I'm running out of ideas how to fix this...

Any help, pointing me in the right direction would be appreciated

Originally created by @UKnau22 on GitHub (Aug 9, 2023). I have MotionEye installed in Docker and an rtsp camera connected to it. Within MotionEye I can access the camera stream, save motion triggered events/movies to my NAS etc... Everything is working great. When I try to access the stream through the streaming URL 192.xxx.x.xxx:8081 in any web browser the "ERR_CONNECTION_REFUSED" message comes up. In HomeAssistant I can access the stream through port 192.xxx.x.xxx:8765, however when I tap on the picture entity card to expand the stream a broken link shows up. I'm running out of ideas how to fix this... ![Untitled](https://github.com/motioneye-project/motioneye/assets/114884846/57b19e16-7f48-4176-8dcf-49fa01343885) ![Untitled1](https://github.com/motioneye-project/motioneye/assets/114884846/592acd21-c3c3-4816-9736-24eca93b911e) Any help, pointing me in the right direction would be appreciated

deekerman closed this issue

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

deekerman commented

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

Author

Owner

@eregnier commented on GitHub (Dec 9, 2024):

by default motion configuration file sets motion to listen localhost only for both web app and video stream.
It looks like you were able to see video from local software on device hosting motion or something like this, but not from another device by reaching the motion device from a 192.168.x.x lan address.

the principle here is to set stream_localhost off (instead of on) and webcontrol_localhost off (instead of on) in the motion configuration file located in /etc/motion/motion.conf

if you are in a docker execution context depending on how is build motion image, you might be able to mount the configuration file as a volume and update it's content before launching the container.

@eregnier commented on GitHub (Dec 9, 2024): by default motion configuration file sets motion to listen localhost only for both web app and video stream. It looks like you were able to see video from local software on device hosting motion or something like this, but not from another device by reaching the motion device from a 192.168.x.x lan address. the principle here is to set stream_localhost off (instead of on) and webcontrol_localhost off (instead of on) in the motion configuration file located in /etc/motion/motion.conf if you are in a docker execution context depending on how is build motion image, you might be able to mount the configuration file as a volume and update it's content before launching the container.

deekerman referenced this issue

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

Motioneye and Libcamera #2429

deekerman referenced this issue

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

Raspberry Pi 4b Camera Module 3 Support #2500

deekerman referenced this issue

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

motioneye not updating v4l2 camera size & fps. #2504

deekerman referenced this issue

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

how to delete recorded video's on a raspberry pi in terminal #2627