Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
 
Notifications
Clear all

Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore  

Page 2 / 2
  RSS
dcorbin13
(@dcorbin13)
Eminent Member
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore

I have, but it's not very helpful. 2.9.3 has this line:

[2025-09-30 21:12:43.110891] [0x00000001eea660c0] [error] OctoPrint: Error getting version: Couldn't connect to server:

that 2.9.2 doesn't when I click Test for that physical printer.

Posted : 01/10/2025 1:18 am
Walter Layher
(@walter-layher)
Noble Member
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore

Hmm, this must be a problem specifically on MacOS. Are there any other MacOS users here who are using PrusaSlicer 2.9.3?
After I installed PrusaSlicer 2.9.3 on my Debian system and started it for the first time, it only had selected one of the generic printer profiles instead of one of my configured physical printers. After changing to the correct physical printer everything worked as before.
I can remember that on a previous update of PrusaSlicer some time ago the host type on the configured physical printers was changed from "OctoPrint" to "PrusaConnect" or "PrusaLink". Are you sure that the host type is still set to "OctoPrint"? Other than that I can't think of anything else to try.

Posted : 01/10/2025 4:29 am
Page 2 / 2
Share: