[Solved] Prusa Connect Print/Add to Queue function is resulting in http 503 error  

RE: Prusa Connect Print/Add to Queue function is resulting in http 503 error

I have the same issue, and I'm pretty fed up at this point.

RE:

Posted by: @konrad-stang

Prusa Connect Print/Add to Queue function is resulting in http 503 error.

Printer model: mk4s

Printer UUID: 5acb44cb-6e3e-482d-845d-a155619d5d83
prusaSlicer version: 2.9.4

Problem started: a few days ago, don't have an exact time. Was working before that.

Things tried:

• upgraded printer firmware to latest, (6.2.6+8948) same results.
• rebooted printer
• attempted from prusa connect within prusa slicer and through prusa connect within web browser at "https://connect.prusa3d.com/printer/..."
  • failing endpoint is https://connect.prusa3d.com/app/printers/5acb44cb-6e3e-482d-845d-a155619d5d83/queue

I've tried searching to see if this is a widespread issue, but I haven't been able to find anything. Any help or info would be appreciated.

 

Glad and upset to see that I'm not the only one experiencing this issue. This started happening to me several weeks ago, but google searching even now only leads me to old posts with and suggests Prusa server issues the shouldn't be the case.

Going to add my bug report as well:

Using latest firmware on core one and latest prusa slicer, I consistently get HTTP 503 error.

PrusaConnect is still working though. I can control the printer through prusa connect with no issue. I can still re-arrange queue, I can select files from storage to print. So it's not a network connectivity issue. Printer is set to use DHCP but is assigned static IP from router based on MAC address.

PrusaLink works flawlessly, I can copy the file to the storage and it succeeds 100% of the time. So currently.. my workflow has to be, receive error in newest PrusaSlicer with PrusaConnect, expport the gcode to a file instead, open a browser and use PrusaLink to copy that same file to Core One, go back to PrusaConnect and either print, or arrange the queue.

I double-checked to ensure windows firewall is allowing all connections for PrusaSlicer.

This should not be happening on a brand new printer with all the latest firmware/software.

I've tried reconnecting the printer several times to PrusaConnect, renaming printer each time and re-adding into PrusaSlicer. And same symptoms result, PrusaConnect is working flawlessly, except for uploading the file to PrusaConnect servers.

It would suggest a problem on Prusa's end, but then why is it only happening to a small amount of users?

• PrusaLink type (Raspberry Pi Zero / Pi 3 / Pi 4)
  • Core One
• PrusaLink version
  • Doesn't indicate. Whatever is with Core One firmware 6.3.4+10511 
• Printer type
  • Core One
• Printer UUID (you can find it in Printer detail page - address line)
  • Did not see this on my Core One
• Printer firmware version
  • 6.3.4+10511 (current latest)
• PrusaSlicer version (if applicable)
  • PrusaSlicer 2.9.4 (current latest)
• Description of the bug, including steps to reproduce (if possible)
  1. Sent a print to printer by slicing and then using "set ready and print now" option.
  2. Perhaps it works, as it sometimes, but very rarely works.
  3. Once that print is complete, either:
     1. leave printer as is after clearing/cleaning bed
     2. or, after cleaning bed manually set printer to set ready and return back to home screen manually on printer
  4. Slice another print and in prusa connect, click either
     1. "print now" or "set ready and print now" depending on step 3.
     2. copy to printer
     3. add to queue
  5. Get HTTP 503 error as in the attached image

     

RE: Prusa Connect Print/Add to Queue function is resulting in http 503 error

oops, I guess I missed the Core One firmware update released 4 days ago (I've been troubleshooting/avoiding this issue for a couple months now). So I'm not running latest firmware anymore.

After current print completes I will update my firmware to latest and see if the issue was resolved. I hope so, but not confident because it doesn't seem to be anything wrong on the printer's side of things.

RE: Prusa Connect Print/Add to Queue function is resulting in http 503 error

Unfortunately removing and reinstalling Prusa Slicer didn't solve anything for me.

Also, I can't use connect to print: the model is uploaded, then I get the 503 error, and the print won't start. The printer is ready and displays the model on the screen, but it won't start printing, even if I click "start printing" again on Connect I also get an error message 

RE:

Posted by: @konrad-stang

Solution: uninstall prusa slicer and reinstall. 

 

I don't know why this worked for me, but it fixed my issue and it hasn't happened in a few days now.

I already had a slicer update and had same issue, but I tried this anyways (uninstall, reinstall, and also deleting an old alpha version) and unfortunately no change.

Even first try to send to connect it immediately failed.

RE: Prusa Connect Print/Add to Queue function is resulting in http 503 error

503 is a server side error with multiple potential triggers. As it is only affecting some users, it would be worth checking how much storage you have used on the Connect server (not printer). Getting too close to the storage allocation limit may be the issue so deleting files from there may resolve it. 

RE: Prusa Connect Print/Add to Queue function is resulting in http 503 error

Posted by: @mvh3032

503 is a server side error with multiple potential triggers. As it is only affecting some users, it would be worth checking how much storage you have used on the Connect server (not printer). Getting too close to the storage allocation limit may be the issue so deleting files from there may resolve it. 

Thanks, I didn't know this was a thing. Unfortunately shouldn't be the issue. I checked it out and I'm at 45% used.

RE: Prusa Connect Print/Add to Queue function is resulting in http 503 error

Instead of just uninstalling and reinstalling, I'm going to wipe the directory that stores all the profiles in windows. Not sure what else I could rule out.

I've only sent a few prints from a linux machine, but I don't think I've ever encountered the error ever from my linux machine, only on win11.

RE: Prusa Connect Print/Add to Queue function is resulting in http 503 error

It looks like Prusa eventually fixed it ! Took them some time, though.
I did nothing and today it's working.

RE: Prusa Connect Print/Add to Queue function is resulting in http 503 error

well shoot, i guess i'll never know what fixed it then... i deleted the PrusaSlicer folder from %appdata%.. which was odd in itself because it kept saying something was using the folder, even after uninstalling prusa slicer and rebooting and ending every unnecessary process I could find. I deleted the files inside the folder looking for which one was being accessed, but then I was able to delete all of them, and subsequently the folder itself.

Reinstalled prusa slicer after, sent two prints and haven't encountered the error yet.
So maybe delete the profiles folder, or maybe prusa coincidentally fixed it today, who knows.

Posted by: @reivax

It looks like Prusa eventually fixed it ! Took them some time, though.
I did nothing and today it's working.