Web Interface not working- log says "curl: (7) Failed to connect to 127.0.0.1 port 8765: Connection Refused" about motioneye HOT 7 CLOSED

Hmm.. more digging online (without specifying motioneye or 8765) I found some similar errors on different ports. (All the motioneye-specific pages I found weren't helpful)

Which lead me to try this command on the RasPi:
curl 127.0.0.1:8765
And that returned a screenful of HTML. Which supports the output of netstat showing python3 listening on that port.

Now I'm wondering if the error in the logfile is just a timing issue (i.e. it's coming up, but isn't up yet when that curl command gets run in the log), and the real error lies elsewhere.

I don't have any firewall or proxy configured.
DHCP appears to be working (shown in original testing).

from motioneye.

Okay, so the motion.service is not running, that is good. I wonder why it was running just an hour before the last motionEye logs entries? Did you install motionEye freshly?

You said you changed the line in motioneye.conf to 0.0.0.0, but in the linked file, I see:

listen 127.0.0.1

This means, it accepts connections from the very same system only, no remote access, which would explain perfectly fine that a local curl works, while accessing from another browser does not.

EDIT: And the netstat output proves it: See 127.0.0.1:8765 compared to 0.0.0.0:9081 for the functional motion/camera port.

from motioneye.

I'd manually started/stopped motion, which is why that shows up.

We're thinking along the same lines - I've changed the listen value in motioneye.conf multiple times. (you can see those commented out). Last night I was testing out more things and noticed that the :7999 connection had broken, but the :9081 was still working.
Going from memory, the netstat at that time was:
tcp 0 0 0.0.0.0:8765 0.0.0.0:* LISTEN 26721/python3
tcp 0 0 127.0.0.1:7999 0.0.0.0:* LISTEN 26730/motion
tcp 0 0 0.0.0.0:9081 0.0.0.0:* LISTEN 26730/motion

So that would explain the loss of :7999, but still not explain :8765 not working.

I'll confirm in a few hours when I get home.

from motioneye.

Got home and checked
-motioneye.conf had listen on 0.0.0.0
-motion.conf had webcontrol_localhost on

This gave a netstat result of:
tcp 0 0 0.0.0.0:8765 0.0.0.0:* LISTEN 26721/python3
tcp 0 0 127.0.0.1:7999 0.0.0.0:* LISTEN 26730/motion
tcp 0 0 0.0.0.0:9081 0.0.0.0:* LISTEN 26730/motion

With the ability to connect and see the video on 9081, and "refused to connect" on the others.

Changing motion.conf to "webcontrol_localhost off" and restarting now gives a netstat of:
tcp 0 0 0.0.0.0:8765 0.0.0.0:* LISTEN 26721/python3
tcp 0 0 0.0.0.0:7999 0.0.0.0:* LISTEN 26730/motion
tcp 0 0 0.0.0.0:9081 0.0.0.0:* LISTEN 26730/motion

And:
:9081 shows the video feed
:7999 gives "Motion 4.6.0 running [1] camera"
:8765 refuses to connect

Not sure if it's related, but with this setup I get the

"curl: (7) Failed to connect to 127.0.0.1 port 8765: Connection Refused"

message twice in /var/log/motioneye/motion.log. With "webcontrol_localhost on" in motion.conf the message only appears once.

from motioneye.

To make it more interesting- and since nothing on the RasPi side was coming up wrong, I tried connecting from my phone using a different browser (had been using chrome).

<IP_addr>:8765 came up with the interface right away. Tried again on chrome- no joy.

Went and got my laptop, connected, and opened Chrome. UI came up just fine on :8765.

Restarted the phone. Connected to the RasPi wifi, opened chrome. UI came up fine on :8765.

ARRRRGGGHHH!!

Thanks for the help. Hopefully at least this may help someone else in the future.

from motioneye.

So you still see the "connection refused" in motion.log or has this been sorted? I actually remember seeing something similar, since the motionEye frontend seems to try to connect to the backend already (to get some settings, IIRC) before one has authenticated. Probably it is that one. While it is visual only, makes sense to track down this in code and skip this attempt until authentication has finished.

from motioneye.

Yes, I still see that - doubled in some cases as noted previously.

Thanks

from motioneye.