#Changed Crowsnest default stream port, now 403 error connecting to Mainsail webui

39 messages · Page 1 of 1 (latest)

jolly moth
#

Not entirely sure what happened here. Having issues getting my webcam back up and running after a mainboard swap. Used KIAUH to install crowsnest, and figured there was a pot conflict with 8080 at the house so I changed stream port in crowsnest.conf to port 8081 and now I am getting a 403 error when going to my machine's local IP. Seems unrelated, but I have not changed anything else and this issue was immediate after changing the port and saving the config. I can still SSH into the Pi, I changed the default stream port back to 8080 via nano in SSH and am still receiving the error.

restive comet
#

As you already said, this is entirely unrelated and just a bad coincidence.

#

Also I don't know what your mainboard (ig you mean printer board) has to do with your camera and eveerything else of your setup, as your pi should be independent of your printer board, unless you got one of those makerbase boards.

#

Send the website your can see under http://<ip-of-your-pi>:7125

jolly moth
#

It's a Manta M8p with their CB1 on board. Pi is plugged into a port on the manta and recognized with lsusb

#

I'll send that and see what comes back

restive comet
#

What exactly is your problem right now that you want to send me the output of lsusb? Or did I misunderstood that message

restive comet
jolly moth
# restive comet And I guess you mean the CB1 with pi, right?

Correct! I do get a "welcome to moonraker" landing screen at port 7125, I'm accessing it remotely over tailscale currently with the machine IP listed in the moonraker config file.

Currently I can't access Mainsail at all from the machine's tailscale IP

#

But once that is resolved, I'm sure I wont be able to see the webcam stream either.

jolly moth
restive comet
restive comet
restive comet
jolly moth
#

I'll see if I can rip the crowsnest log from winscp real quick. Hold tight, I'm at work at the moment lol

I'll grab a screenshot as well, it's up on another machine in the back.

Previously it was using 'adaptive' stream and running just fine over tailscale. Albeit at 0-1fps due to encryption, but I digress

stiff cobalt
restive comet
#

How do you try to connect to mainsail? With the ip or domain name (of tailscale)?

jolly moth
#

With the tailscale IP when we're here.

restive comet
#

Then try to connect again and open the browser developer tools and have a look at the console

#

And send the moonraker.log

jolly moth
#

You got it, hang tight, connection is pretty slow and spotty it seems like. We're installing a repeater specifically for this machine tonight lol

stiff cobalt
#

[history]

[update_manager]
channel = dev
refresh_interval = 168

[update_manager client ZeroGTheme]
type = git_repo
path = ~/zerog-mainsail-theme
origin = https://github.com/ZeroGDesign/zerog-mainsail-theme.git
install_script = install.sh
is_system_service = False

[update_manager mainsail-config]
type = git_repo
primary_branch = master
path = ~/mainsail-config
origin = https://github.com/mainsail-crew/mainsail-config.git
managed_services = klipper

[update_manager mainsail]
type = web
channel = stable
repo = mainsail-crew/mainsail
path = ~/mainsail

#

weid

jolly moth
#

[update_manager mainsail-config] type = git_repo primary_branch = master path = ~/mainsail-config origin = https://github.com/mainsail-crew/mainsail-config.git managed_services = klipper

This is new, I think. I believe it got dumped on there when we did a mainsail re-install via KIAUH. I have a feeling it's conflicting.

restive comet
#

What do you mean? What is conflicting with what?

#

mainsail-config are macros created by the mainsail-crew that you can include inside your printer.cfg. Those macros are some basics that needs to be inside every printer.cfg like virtual_sdcard and PAUSE_PRINT macro

jolly moth
#

Funky, I just wasn't sure as none of my machines have mainsail-config listed in the update manager.

restive comet
#

I'm wondering a bit more about [update_manager client ZeroGTheme]
Where did you get that from? The word client seems to be a bit out of place

jolly moth
#

The ZeroGTheme is managed by KIAUH, just a section of their script that installs themes. I have it running on my Voron as well without issue.

restive comet
#

I just didn't know that a naming like that is viable

restive comet
#

Still a bit new to the crew, so I don't know everything yet 😅

#

Back to the main point of the moonraker.log.
Could you try to add 100.76.222.103 to the cors_domains inside the moonraker.conf?

#

Maybe there is something going on with cors

jolly moth
#

Sure, I can give that a shot before we get out of here. We'll probably continue a bit later once he's home and has his repeater hooked up. We're still not entirely convinced that it isn't local network related. At least, the connection to the Mainsail WebUI. The Crowsnest issue I think is something else entirely, but can't really get far with that without the UI.

restive comet
#

At least, the connection to the Mainsail WebUI.
The weird thing is that you can connect to the moonraker page, and if it's really 403 it should be moonraker blocking it, but that should let you through

jolly moth
#

Agreed, I thought that was weird too. Without specifying the port, it does just sit at the 'initializing' screen forever, which does usually point to the moonraker config missing the terminal's IP. I did run into that with my other machines early on when I was figuring out Tailscale. I may have him set up a subnet as well so we can pass local IP's through tailscale and see if the encryption plays a role.

restive comet
#

Without specifying the port
You mean 7125 or 80/81?