Unable to start print job from PS 2.7.0 alpha 1 with XL5 using PrusaConnect
Used to be able to start a print job immediately after slicing using PrusaConnect. However, after the latest firmware and slicer upgrades, PrusaConnect does not work any more and the print jobs are started using PrusaLink. Here's the weird part. If the connection is tested using the PrusaLink API Key instead of the PrusaConnect API key, the connection works. But the print will still not start and complain about an 401 Unauthorized error. Have removed the printer from PrusaConnect and re-registered it from the printer, and there was no change to the result.
PrusaConnect is still able to monitor and start print jobs for the printer. This is about starting print jobs from within PrusaSlicer 2.7.0 alpha 1 and meeting with 401 Unauthorized errors.
XL 5 toolhead with 5.1.0 Alpha 2 firmware Version: 2.7.0-alpha1+MacOS-x64 Build: PrusaSlicer-2.7.0-alpha1+MacOS-x64-202310191614 Operating System: Macintosh System Architecture: 64 bit System Version: macOS Version 14.0 (Build 23A344) Total RAM size [MB]: 34,360MB
Best Answer by Tojik:
Hi, which one do you have selected?, if you select PrusaConnect, you need to also fill out the address to be connect.prusa3d.com (i think). If you choose PrusaLink, you need the printer ip. Of course also put their respective API keys there
Sorry if i misread your situation
RE: Unable to start print job from PS 2.7.0 alpha 1 with XL5 using PrusaConnect
Sorry, it should be 403, instead of 401.
Error uploading to print host:HTTP 403: 403: Forbidden
RE: Unable to start print job from PS 2.7.0 alpha 1 with XL5 using PrusaConnect
Hi, which one do you have selected?, if you select PrusaConnect, you need to also fill out the address to be connect.prusa3d.com (i think). If you choose PrusaLink, you need the printer ip. Of course also put their respective API keys there
Sorry if i misread your situation
RE: Unable to start print job from PS 2.7.0 alpha 1 with XL5 using PrusaConnect
Now that is interesting. In PS 2.6, when connecting to PrusaConnect, I set the IP to the printer's IP, and it worked! So I've taken your advice and entered the hostname for PrusaConnect, and now under PS2.7.0 alpha 1, this works! Thank you!
Now, if I may offer a suggestion for consideration. That this be made automatic, to ease the cognitive load for the user. Since Prusa has full control over hostnames, DNS registration etc, it would be trivial to send a configuration update over PS and set the correct configuration for PrusaConnect. The user only has to enter the API key. Then this "issue" would be moot.
RE: Unable to start print job from PS 2.7.0 alpha 1 with XL5 using PrusaConnect
Yea, the address is there more for debugging at our end, might be worthwhile to set it automatically