The error is in the topic. Appears to be a software issue. I cannot access the printer with the Snapmaker Orca software.
Every time I try to connect with either PIN, IP or find local, it will find it, but when I try to connect, that is the error I get.
The printer appears to be on the network.
My network is up and working fine.
All my other printers (Bambu, Creality, Anker) are not having any issues.
For whatever reason, even though I was able to send jobs to my other printers, this was resolved with a reboot of my computer. It appears the connection to the printer is a bit flaky.
So I’d consider this no longer an immediate issue, but something that does need to be addressed.
If you run into this again, please copy and paste the slicer logs here for us to reference—thanks a lot for the feedback!!
For log collection, please follow the steps in this post.
What solved the issue @Simon_Zhi ?
As I understand it rebooting solved the issue, at least for the short term.
This is a good question. I have seen posts marked solved I suspected were not marked by the original poster. Including now one of my own posts this morning. (I did not choose one, but one was chosen.)
Respectfully request only the OP mark the solution to an issue, unless the OP specifically says something was a solution without marking it.
Can you try this method?
This is likely a weak-network issue causing the print page to load too long and show connection problems. We’ve swapped the resources as a temporary fix:
flutter_web_release_2.2.2+20260107103257.zip (16.0 MB)
step1：open folder as picture
step2：
Close Orca Software window.
Delete everything inside the [ flutter_web ] folder, copy all contents from the extracted folder, paste them in, then reopen Orca and try.
If issues occur after updating the resources, please help collect the Orca logs. Looking forward to your latest feedback.
For log collection, please follow the steps in this post.
Incorrect usage!!
I often notice solutions that haven’t been marked, so I click them to make the outcome clearer—some new users haven’t picked up that habit yet.
Ok. Without the original poster confirming the solution worked (unless it is very obvious), it might be presumptuous or misleading to mark it as correct.
I think of Microsoft forums where sometimes a non-solution gets marked and the problem is never actually solved. It’s very frustrating. 
I hope we don’t do it here too often.
Okay, I understand what you mean.
