Running crowsnest on an external device

[cackmobile]

HI, I have a FF ad5x which has been modded to open klipper but is a limited version. I install crowsnest on a seperate Pi and used the no proxy flag, but now im not sure what to do to find the cameras on my printer. what files do I change etc

I tried the below in crowsnest.config
[cam 1]
mode: ustreamer # ustreamer - Provides MJPG and snapshots. (All devices)
# camera-streamer - Provides WebRTC, MJPG and snapshots. (only RPiOS + RPi 0/1/2/3/4)
ip: 10.0.0.202
port: 8080 # HTTP/MJPG stream/snapshot port
device: /dev/video0 # See log for available devices
resolution: 640x480 # x format
max_fps: 15 # If hardware supports it, it will be forced, otherwise ignored/coerced.
#custom_flags: # You can run the stream services with custom flags.
#v4l2ctl: # Add v4l2-ctl parameters to setup your camera, see log for your camera capabilities.

[cam 2]
mode: ustreamer # ustreamer - Provides MJPG and snapshots. (All devices)
# camera-streamer - Provides WebRTC, MJPG and snapshots. (only RPiOS + RPi 0/1/2/3/4)
ip:10.0.0.202
port: 8081 # HTTP/MJPG stream/snapshot port
device: /dev/video3 # See log for available devices
resolution: 640x480 # x format
max_fps: 15 # If hardware supports it, it will be forced, otherwise ignored/coerced.
#custom_flags: # You can run the stream services with custom flags.
#v4l2ctl: # Add v4l2-ctl parameters to setup your camera, see log for your camera capabilities.

[meteyou]

I think you mixed up something here... Crowsnest is a "server" and not a "client". so the value ip is complete wrong here.

First of all, your browser has nothing todo with that, as long as it can open Mainsail (so loading the static files and execute Javascript) and display a stream (video encoder). Klipper itself is only running on the Pi / SBC itself. So your browser has no contact points with Klipper itself.

So if you have Crowsnest installed on the second Raspberry Pi and it is running without issues (pls check the log), you should be able to open the streams or the crowsnest dashboard via:

• http://<ip from the second pi>:8080 for the first cam
• http://<ip from the second pi>:8081 for the second cam

if not, you haven't disabled the proxy.

In this page, you should also see the URL for the snapshot and the stream from the cam. You have to copy these 2 URLs and add a new cam in Mainsail (in the interface settings) and add these 2 URLs. (you have todo this step for each cam with each port). The URL should look like these:

• http://<ip to the second pi>:<port of the cam>/?action=stream
• http://<ip to the second pi>:<port of the cam>/?action=snapshot

[cackmobile]

Ok thanks very much, I'll try that! Regards Elliott

…

On Mon, 25 Aug 2025, 6:06 pm Stefan Dej, ***@***.***> wrote: I think you have an "thinking issue" here. Crowsnest is a "server" and not a "client". so the value ip is complete wrong here. First of all, your browser has nothing todo with that, as long as it can open Mainsail (so loading the static files and execute Javascript) and display a stream (video encoder). Klipper itself is only running on the Pi / SBC itself. So your browser has no contact points with Klipper itself. So if you have Crowsnest installed on the second Raspberry Pi and it is running without issues (pls check the log), you should be able to open the streams or the crowsnest dashboard via: - http://<ip from the second pi>:8080 for the first cam - http://<ip from the second pi>:8081 for the second cam if not, you haven't disabled the proxy. In this page, you should also see the URL for the snapshot and the stream from the cam. You have to copy these 2 URLs and add a new cam in Mainsail (in the interface settings) and add these 2 URLs. (you have todo this step for each cam with each port). The URL should look like these: - http://<ip to the second pi>:<port of the cam>/?action=stream - http://<ip to the second pi>:<port of the cam>/?action=snapshot — Reply to this email directly, view it on GitHub <#2252 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3ZV6A3MBCM5XOBDLCURPXL3PK7WRAVCNFSM6AAAAACEWK6RAOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMRQG43TQOI> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>