WebRTC - Default URL incorrect

[DrFate09]

I have WebRTC setup with a Crowsnest config running within Fluidd. My host is a RPi 4B running Bookworm.

I currently do not have my printer connected to my RPi, so Mobileraker is only connecting to the RPi.

Mobileraker is adding a /%20/ to the URL and it is breaking the camera connection. If I go on my browser and remove the /%20/, the camera stream loads correctly.

Can we remove the unnecessary/%20/ from the default WebRTC URL?

Since my MCU is not connected, I cannot edit the camera settings within Mobileraker.

[DrFate09]

The correct URL is shown in the screen capture below.

Screen capture from Fluidd.

[Clon1998]

Hey,
the%20 is a space encoded for the URL. Double check that the configured webcam does not have a leading space character.
Alternatively, you can always use an absolute URL rather than the relative one.

[DrFate09]

@Clon1998 I double checked my Fluidd Webcam section (it is also in the screenshot above) and there is not a leading space character.

How do I set up an absolute URL when a MCU is not connected? I did not find an option in the Mobileraker printer settings.

[Clon1998]

@Clon1998 I double checked my Fluidd Webcam section (it is also in the screenshot above) and there is not a leading space character.

How do I set up an absolute URL when a MCU is not connected? I did not find an option in the Mobileraker printer settings.

I don't remember it but I think Mobileraker and fluidd do not share the webcam settings.

I currently can not test it, but I assume if you open the printer settings in the app it won't show any "additional" settings that would normally include the webcam section without the mcu?
If that's the case I'd need to adjust this behavior in the app.

For now, I'd say the only option is to disable/remove the mcu from the config to temporarily trick Klipper into starting which would allow you to modify the value in the app.

[DrFate09]

These are the only settings that I have available while having a MCU disconnected.

[Clon1998]

These are the only settings that I have available while having a MCU disconnected.

Got it.
That's definitely an UX error on my end.
I will address it but this might take a couple weeks.

As I mentioned, to get it working now, you could temporarily remove the mcu section to trick Klipper into starting.

[DrFate09]

I was able to get my MCU hooked up and Mobileraker fully up and working. I did find that by default, I had the "%20" in front of both the stream and snapshot URLs (see screen capture). Might be worth a check to see if Mobileraker is including that value incorrectly.

[Clon1998]

I was able to get my MCU hooked up and Mobileraker fully up and working. I did find that by default, I had the "%20" in front of both the stream and snapshot URLs (see screen capture). Might be worth a check to see if Mobileraker is including that value incorrectly.

Will do that. Just to confirm, you did not add the webcams in the app initially did you?

[DrFate09]

No, it was set up initially using Fluidd & Crowsnest.

[Clon1998]

No, it was set up initially using Fluidd & Crowsnest.

In that case the space is coming from fluidd