Could not connect to Prusa Connect: HTTP 401: Missing or invalid API key
Hello, I have a problem.
I have a printer connected to prusa connect, but I can't connect the prusa slicer to prusa connect.
The test returns an error: Could not connect to Prusa Connect: HTTP 401: Missing or invalid API key
I copied the API key from prusaconnect. I'm using the correct apikey (Prusa Connect API key)
I tried disabling all firewalls - it didn't help.
I tried deleting the printer and adding it again (changed the APIKEY) - it didn't help.
I can see the printer normally in prusaconnect. I can see its status, print progress and I can control the printer normally.
The problem is only in the slicer vs connect app.
I also tried curl (I don't know if it's correct, I somehow got to it), but it comes back to me: Missing or invalid API key
curl -X GET -H "Authorization: Bearer MY_APIKEY" https://connect.prusa3d.com/api/version
RE: Could not connect to Prusa Connect: HTTP 401: Missing or invalid API key
I've forgotten the information:
MK4 printer
slicer: version 2.7.1+win64
RE: Could not connect to Prusa Connect: HTTP 401: Missing or invalid API key
I tried it on another computer and it worked there.
I tried reinstalling slicer -> it didn't help.
I removed the physical mk3 printer that had the settings to send to octoprint.
And then mk4 works 🙂
Obviously mixing settings from multiple printers 🙂
So, solved for me 🙂
RE: Could not connect to Prusa Connect: HTTP 401: Missing or invalid API key
Huh, you were faster than my forum checking frequency. Good job figuring it out tho.
RE: Could not connect to Prusa Connect: HTTP 401: Missing or invalid API key
I have the same "Could not connect to Prusa Connect: HTTP 401: Missing or invalid API key" issue with PrusaSlicer 2.7.4 and my MK4 on firmware 5.1.3+13503.
It worked for a few months and stopped suddenly (after I updated either the firmware or PrusaSlicer, I cannot recall), but I switched to PrusaLink and worked with it.
However, now I have to start large print jobs, and it takes ages to upload even bgcode to PrusaLink.
I also have MK3 printer profiles, which are not mixed with the MK4 ones. Anyhow, that shouldn't be a breaking issue, and PrusaSlicer should discriminate correctly.
Is anyone else having that issue?
Cheers,
Martin
-- www.martinmajewski.net --
Thingiverse: www.thingiverse.com/MartinMajewski
Instagram: www.instagram.com/martinjmajewski
Twitter: www.twitter.com/MMajewskiNet
YouTube: www.goo.gl/QJTQKv
RE: Could not connect to Prusa Connect: HTTP 401: Missing or invalid API key
For testing, I removed all other printers but one MK4 from PrusaSlicer, but I still get the same error.
-- www.martinmajewski.net --
Thingiverse: www.thingiverse.com/MartinMajewski
Instagram: www.instagram.com/martinjmajewski
Twitter: www.twitter.com/MMajewskiNet
YouTube: www.goo.gl/QJTQKv
RE: Could not connect to Prusa Connect: HTTP 401: Missing or invalid API key
I had to remove the MK3 connected to the octoprint, after restarting slic3r it worked as it should.
RE: Could not connect to Prusa Connect: HTTP 401: Missing or invalid API key
The duplicate button is in the three dot dropdown. Yes, I agree that we are missing a UX person. That is one of the things I said first year I was working here. (I have been introduced to ux and its testing at uni). I believe things will improve tho
RE: Could not connect to Prusa Connect: HTTP 401: Missing or invalid API key
For anyone else who finds this, I had the same issue with 2 printers but didn't want to delete them. I found that I had PrusaLink configured for both printers but it was using "HTTP Digest" as the authentication method (which worked fine to upload directly to PrusaLink on each printer). I changed this to 'API Key' and then changed the Host Type back to PrusaConnect and entered the PrusaConnect API key and it was able to connect to PrusaConnect correctly. Seems like a bug where the PrusaConnect window is incorrectly using the authentication method info from the PrusaLink window, even though PrusaConnect doesn't support HTTP Digest authentication through PrusaSlicer.
RE: Could not connect to Prusa Connect: HTTP 401: Missing or invalid API key
Thank you for this. It stopped working and I couldn't figure out why. Your post got me back up and running again. Cheers.
For anyone else who finds this, I had the same issue with 2 printers but didn't want to delete them. I found that I had PrusaLink configured for both printers but it was using "HTTP Digest" as the authentication method (which worked fine to upload directly to PrusaLink on each printer). I changed this to 'API Key' and then changed the Host Type back to PrusaConnect and entered the PrusaConnect API key and it was able to connect to PrusaConnect correctly. Seems like a bug where the PrusaConnect window is incorrectly using the authentication method info from the PrusaLink window, even though PrusaConnect doesn't support HTTP Digest authentication through PrusaSlicer.
RE: Could not connect to Prusa Connect: HTTP 401: Missing or invalid API key
I had no idea why my MK4S started showing erratic behavior with PrusaConnect (crashing file transfers, not showing online).
Turns out I had the parameter also set to PrusaLink as you described, I switched the settings to PrusaConnect API and now not only is the problem solved but file transfers to the printer are much faster.
Thanks a lot for the help.
For anyone else who finds this, I had the same issue with 2 printers but didn't want to delete them. I found that I had PrusaLink configured for both printers but it was using "HTTP Digest" as the authentication method (which worked fine to upload directly to PrusaLink on each printer). I changed this to 'API Key' and then changed the Host Type back to PrusaConnect and entered the PrusaConnect API key and it was able to connect to PrusaConnect correctly. Seems like a bug where the PrusaConnect window is incorrectly using the authentication method info from the PrusaLink window, even though PrusaConnect doesn't support HTTP Digest authentication through PrusaSlicer.