Raspberry Pi 3 Model B运动摄像头网页无法访问问题求助

Hey there, let's troubleshoot this step by step since your Apache is working but Motion's web interface isn't accessible on port 8080. Here are the key checks to run:

By default, Motion often locks its web interface to local-only access. Let's adjust the config:

• Open the main Motion config file: sudo nano /etc/motion/motion.conf
• Look for these parameters and update them:
  • Set webcontrol_localhost off to allow external devices (like your Mac) to access the control panel
  • Set stream_localhost off if you want to view the live camera stream remotely
  • Double-check webcontrol_port 8080 is set to the port you're trying to access
• Save changes (Ctrl+O, press Enter, then Ctrl+X) and restart the service: sudo service motion restart

Even if the service says it's active, it might not be actually listening on the network. Run this on your Raspberry Pi:

sudo netstat -tulpn | grep 8080

You should see an entry like 0.0.0.0:8080 or :::8080—this means Motion is listening on all network interfaces. If nothing shows up, check the Motion logs for startup errors:

sudo cat /var/log/motion/motion.log

Look for lines about failed camera initialization or config syntax issues.

Since Apache works, your network connection is good—but port 8080 might be blocked:

• If you have ufw (Uncomplicated Firewall) enabled on the Pi, allow port 8080:

  sudo ufw allow 8080
  sudo ufw reload
  

• On your Mac, test port connectivity with telnet to rule out network blocks:

  telnet [your-pi-ip-address] 8080
  

  Replace [your-pi-ip-address] with your Pi's actual local IP (e.g., 192.168.1.42). If the connection fails, go back to checking the Pi's firewall or Motion's listening status.
• Critical note: Make sure you're using the full URL in your browser: http://[your-pi-ip-address]:8080—the http://:8080 you mentioned won't work without the Pi's IP.

Another program might be using port 8080. The netstat command from step 2 will show which process is using the port if there's a conflict. If that's the case:

• Either change Motion's port in motion.conf (update webcontrol_port to something like 8081) and restart the service
• Or stop the conflicting process to free up port 8080

Sometimes the service reports as "active" but has underlying issues. Check the detailed status:

sudo systemctl status motion

Look for red error messages or notes about failed camera detection. If you suspect a camera problem, run Motion in foreground mode to see real-time logs:

sudo motion -n

This will show you exactly why Motion might not be initializing properly (e.g., missing camera drivers, loose connections).

内容的提问来源于stack exchange，提问作者pac