#All of my printers will not connect to the Mainsail interface after recent changes.

78 messages · Page 1 of 1 (latest)

placid pilot
#

Okay, so I recently did a full overhaul of my printer lab and moved all of my printers up onto some industrial shelving and then reconfigured the entire room, long story short my printers have all been sitting idle for about a month. Today I completed all of my projects and fired up all of the printers so that I could run updates and make sure everything was working. Here's where it gets weird. I can see all of the printers connecting to my local network through my router's dashboard, so I know the router and the Pi's are playing nicely. I can SSH into each printer's Pi and run updates through KIAUH, no problem there. I can even pull up the interface for each printer on Mobileraker. What I can't do is pull up the Mainsail page for each of my printers. It simply refuses to connect. It is worth mentioning here that I created my own home file server from a spare SSD and a RPi5 that I had laying around during the downtime. This server uses Port 80 so that I can upload/download files from anywhere in the world that has an internet connection. The server has been operating flawlessly for about 2 weeks now. The problem is that Mainsail also listens at Port 80 and I believe that is what is causing the problem. I've already SSHed into a few of the printers and changed the Port that Mainsail listens at to Port 81. Specifically by using this Linux command: sudo nano /etc/nginx/sites-available/mainsail. That hasn't worked and I'm kind of out of ideas at this point. Can anyone point me in the right direction? Thanks in advance!

Just tried: sudo systemctl status mainsail.service and it says "Unit mainsail.service could not be found" when I ran the same command for the moonraker service, it was running properly, so it looks like mainsail is definitely the problem here.

scenic dirgeBOT
#

Ahoi @placid pilot!
It looks like you did not provide all the necessary information we need to help you.
Please upload your logfiles and a detailed description of your problem.
For further information see: https://docs.mainsail.xyz/faq/getting-help/discord#provide-information
Note: We only accept .log and .txt files as log files.
This is an automated message

Discord | Mainsail

We are glad to help and chat with you on our Community Discord, but if you need help and want the best support possible you should, follow a few simple rules:

placid pilot
#

I am unsure how I'm supposed to access the logs when I can't access the GUI.

placid pilot
#

I can't download a log file but i was able to screenshot this after digging around in the mainsail-error log through SSH. I would really appreciate if anyone could just say something, Im at the end of my rope here.

vivid sparrow
vivid sparrow
#

About the home file server:
It's reading like it's a separate device from your printers. So if every printer is using it's own pi, that home server is not blocking anything, as it has it's own IP. If one device in a network would block a port for every other device, the Internet could not work, as it's just a huge network of devices.

#

Just tried: sudo systemctl status mainsail.service and it says "Unit mainsail.service could not be found" when I ran the same command for the moonraker service, it was running properly, so it looks like mainsail is definitely the problem here.
There is no Mainsail service.
The file you edited with the sudo nano command was the following: /etc/nginx/sites-available/mainsail
The second part of that path tells you what the service is: nginx
It's a web server hosting Mainsail or other kind of websites. Mainsail is just a normal website showing you stuff

placid pilot
vivid sparrow
#

The home file server uses a Linux based service called Caddy to create a reverse proxy, it controls all traffic through ports 80 and 443
But it is not controlling traffic on port 80 for a different device!!!
E.g. your pi5 with caddy is on ip 192.168.1.5, but your printer is on 192.168.1.6. Therefore 192.168.1.5:80 is not blocking port 192.168.1.6:80 or is in any way related to it.

#

When I try to change which ports nginx listens at (for mainsail) that also doesn’t work.
Yes, as your issue is not that port 80 is blocked

#

If your setup is a Pi5 with Caddy and it itself is also hosting Mainsail for your instances, then it would be a problem. But you told us that each printer has it's own IP (most likely it's own Pi) and that they are all hosting their own Mainsail

placid pilot
placid pilot
placid pilot
#

It appears that Caddy is in fact claiming all traffic on Port 80, what I don’t get is why changing the port that mainsail is listening at isn’t working.

vivid sparrow
vivid sparrow
#

You are not blocking port 80 in the whole world, just because you are using it on your Pi. The internet is just a bigger home network

#

Just making a screenshot without the question does not proof anything. As you can see, caddy is not blocking it for other devices on your home network

image.png
placid pilot
#

No those are the most recent logs that I pulled this morning.

#

I’m not trying to argue man, I’m just trying to find a solution and I’m getting conflicting info. Here’s the question I posed.

IMG_5427.png
vivid sparrow
# placid pilot

I hate chatbots... Just trust me, if the devices are separate, they won't interfere

placid pilot
#

I have no newer logs, I’ve given everything that’s been asked of me. I’m just trying to solve this myself while I wait for answers and I’ve got questions out in at least 4 different Discord communities okay? You obviously know more about how this works than I do and that’s why I’m here asking for help.

#

I trust you

vivid sparrow
#

The second question after yours gave me this

image.png
vivid sparrow
placid pilot
#

Okay so port binding is the issue? Then why won’t mainsail work when it’s set up to access other ports like 81, 8080, 800 etc?

vivid sparrow
#

I’ve got questions out in at least 4 different Discord communities
Please also don't do that. Everyone is doing it in their free time. So if multiple people start to help, it gets messy and you might waste other peoples time, if it's already solved somewhere else

vivid sparrow
placid pilot
#

10-4

vivid sparrow
vivid sparrow
# placid pilot Okay so port binding is the issue? Then why won’t mainsail work when it’s set up...

I just read again, the chatbot and got your confusion. So just a bit chatter on why the chatbot gets you confused, and why it's not always a good source of information.

The question:

But how is caddy blocking the traffic to the other devices locally?
The answer:
Caddy isn't blocking traffic to other devices on the network; it's blocking other services on the same machine from using port 80.

But after that it just continued as Chatbots love to give unnecessary additional stuff (GPT-5 is in that regard better):

The issue is a fundamental network concept called port binding. [continues on explaining port binding]
This has nothing to do with the issue. The chatbot just assumed from my previous messages, that the port 80 is blocked. But that assumption is wrong and comes from the initial question:
I'm using a reverse proxy server via Caddy for linux, but now all of my lan sites that are accessed via port 80 no longer work.
You told him that because of setting up Caddy, everything stopped working. You basically told it, that the reason is Caddy, so it tries to explain, why Caddy could be the reason, and the only reason is port binding. It just ignores the fact that you wrote all of my lan sites as it thinks the information might be unnecessary, as you said yourself that the installation of Caddy is the reason for the problem.

#

Working with Chatbots in some technical fields can be very tricky, if you are yourself not sure about the problem. I see this way too often when I use chatbots for something new. It's just ignoring stuff or hallucinates, resulting in very bad responses

placid pilot
#

I absolutely hate chatbots and avoid them at all cost. After waiting for almost 3 hours for anyone to respond to one of my questions last night I just figured I’d have to try. It gave me false information several times. I still don’t know why mainsail isn’t working though.

#

I’m at work right now and can’t access my home network.

#

If I type the IP address of my printer into my browser with :7125 at the end it does the same thing, ie it doesn’t work. However, if I open Mobileraker on my phone my printers are all there, camera feeds are working and I can control them.

vivid sparrow
#

You wrote for me at 6 am and responded at 2 pm with logs, just that you get the rough time difference.
Sometimes you just need to wait, as most of support in 3D printing communities is doing that in their free time

vivid sparrow
placid pilot
vivid sparrow
#

But ssh is working, so it would be kinda weird, if it would be e.g. a different local network

vivid sparrow
placid pilot
vivid sparrow
#

A proof in form of a screenshot together with the url visible would be actually great. It's just a sanity check for me

placid pilot
vivid sparrow
#

Just to be sure, you downloaded the logs, when you were at home, right?

placid pilot
placid pilot
vivid sparrow
placid pilot
#

I also have octoeverywhere set up so my Mobileraker actually will work from outside my home network, and octoeverywhere was working last night.

vivid sparrow
placid pilot
#

I have a printer that’s isn’t on octoeverywhere and it was also visible on Mobileraker last night, so I don’t think that’s a hint actually.

vivid sparrow
#

Hm, ok. But I will wait now for the screenshots. Just don't forget it's now 7:47pm at my place, so I won't respond in 7h, as I will most likely sleep already ^^

placid pilot
#

10-4

placid pilot
placid pilot
placid pilot
#

Okay so I can access my mainsail dashboard through my phones browser, my wife’s laptop’s browser, and… get this… my PC, but only when I switch browsers from Chrome to Safari or Firefox. Chrome is my preferred browser so I’m now trying to figure out if it’s a security setting, I already cleared my cache and reset and that didn’t fix it. I’m getting close though I think.

placid pilot
#

Ended up having to completely uninstall and then reinstall Chrome. Now everything works. My best guess is something got corrupted on a recent update. So glad to finally put this one to rest.

alpine ocean
vivid sparrow
alpine ocean
placid pilot
alpine ocean
placid pilot
# alpine ocean In datasecure and chrome?

Not sure what you mean by datasecure but in the MacOS settings and in my Chrome settings everything was configured correctly. If it was a setting in my MacOS preferences it shouldn’t have let me open the mainsail pages in other browsers, and since my Chrome account is synced to all of my devices it shouldn’t have let me open the mainsail pages on my other devices. A complete reinstall on one device and then syncing my settings to what was on my other devices fixed the problem. This leads me to believe that it wasn’t a settings issue but an issue with the particular application (Chrome) on that device. Since a reinstallation fixed it, that seems like a correct assumption to me.

alpine ocean
#

this setting is per app. so other browsers have different value for this setting

placid pilot
alpine ocean
#

this is the setting i mean (sry... my os is in german). here you can enable and disable the local access per app. if you reinstall an app, it will "reset" this value

placid pilot
# alpine ocean its a MacOS setting, not a chrome setting. when you reinstall it on your mac, it...

Also, I have been to all of these sites that run my multiple printers literally thousands of times over the last idk, 5 years? All of my printers have DHCP address reservation applied, so the site I go to never changes. You think that in the last 3 years that I’ve had this computer I haven’t chosen to allow local LAN traffic? Your photo above is exactly the MacOS settings I was referring to. You are wrong, please stop. Chrome was the problem and a reinstall was what fixed it.

alpine ocean