motioneye-project / motioneyeos

A Video Surveillance OS For Single-board Computers
Other
7.88k stars 902 forks source link

Connection Refused - front-end admin interface not loading on Raspberry Pi Zero W #1550

Open billy-syrett opened 6 years ago

billy-syrett commented 6 years ago

Preliminary Docs

motionEyeOS Version

I am running motionEyeOS version: 20180224 (but have also tried 20180401, nightly-dev, 20180602)

Board Model

I am using the following board/model: Raspberry Pi Zero W

Camera

I am trying to set up a fast network camera.

My camera model is: Standard Raspberry Pi Camera v2.1

Network Connection

My motionEyeOS unit is connected to the network via: WiFi

Log Files

Cannot get log files due to connection issue

Issue

I currently have 1 Raspberry Pi 3B+ running as a hub. I am trying to connect a Raspberry Pi Zero W as a camera. motionEyeOS seems to install fine on the Zero without any error messages but refuses connections to port 80. This means I cannot configure the camera or any other settings (such as setting the device up as a fast network camera). The device does allow connections to port 8081 to view the camera stream.

The hub device works absolutely fine and both devices have official power supplies so don't believe power is an issue.

Screenshot of hub front-end refusing to connect

Screenshot from Google Chome refusing to connect

Screenshot of working :8081 connection

ccrisan commented 6 years ago

Connection refused on port 80 could be caused by one of the following (as far as I can tell):

mike-o-tronic commented 5 years ago

motionEyeOS Version 20190413

Board Model Raspberry Pi Zero W

Log Files Had weird character lines with /00/00/00... in between reboots. Don't know if that's supposed to be there, but the editor definitely complained about this.

Issue Web interface was at port 8765 instead of 80 and the system kept rebooting every 5 minutes or so.

And in case someone does stupid like me the solution is: Reflash the sdcard, save the wpa_supplicant.conf on the boot partition with the other files (bootcode.bin etc) not in the empty boot folder and voilà!