Http://localhost:8080?action=stream only works for localhost (octoprint server)

Get Help Webcams
1

Camera model IDK (a cheap one from amazon), lsusb says "Microdia Webcam Vitade AF"

What is the problem? If I use "h ttp://localhost:8080/?action=stream" for "Stream URL", the test only works for localohost (the octoprint server). However, "http://localhost:8080/?action=snapshot" works for all LAN device, and "http://lan-ip:8080/?action=stream" for streaming actually works for all device.

What did you already try to solve it? "http://localhost:8080/?action=stream" does work in the browser on the localhost.

Logs (/var/log/webcamd.log, syslog, dmesg, ... no logs, no support) No webcamd.log (because I stopped webcamd?).
syslog.log (1.8 MB)
dmesg_output.log (160.6 KB)

Additional information about your setup (OctoPrint version, OctoPi version, ...) I'm running Ubuntu 21.10 on a super old laptop. Installed Python 3.8 via miniconda, then installed octoprint through pip. mjpg-streamer is installed from the snap store.

Honestly, this issue doesn't break any functionality for now, but I just wonder if there is anything serious hidden in the setup...

2

That is the expected behaviour and also stated on the web interface that the LAN IP, or in case pubic IP needs to be entered. The webcam stream is accessed by the browser directly, not by OctoPrint internally. I also found this to be a limitation, especially since it is not possible to secure the stream with HTTP authentication, as long as it does not run behind the same proxy as OctoPrint itself (the preferred setup hence): Mjpg-streamer password-protected or bound to loopback IP

I was already thinking to tinker with OpenCV, which seems to allow catching the stream locally from the backend and forwarding it through OctoPrint to the browser: Access IP Camera in Python OpenCV - Stack Overflow
That way one could enter localhost for the camera and lock it down to not listen an any remote access and/or secure it with HTTP authentication :thinking:.

3

Thanks!
I should have searched before posting. Let me go through your post and replies!

4

Hi everyone! Sorry for necroposting, but found some interesting behavior around this issue.
Using fluid-klipper, i can acces the camera always, from the localhost and the external computers.
So far, that seems to be my workaround. On the local screen i use one tab for octoprint and the other for fluid. Mostly for positioning the camera. So i left octoprint configured for the the external computers.
BUT!! maybe the implemetation used by fluid can be somehow apllied here?
Anyways thanks for all!!