RE: Octoprint HTTPS Validation on Mac with 2.3.0
Hello
This seems like an old issue, but I was dealing with this too. At least I think I was. I am on OS X 12.3.1 and Prusa Slicer 2.4.2. and Octoprint 1.7.3
I have my octoprint setup listed as "https://<name-of-octoprint-here>.local" in the PrusaSlicer setup window. It gave me this whole failure as above. But when I changed it to: <name-of-octoprint-here>.local then all was well.
How silly.
RE: Octoprint HTTPS Validation on Mac with 2.3.0
Hey
Yes, it's still a problem. Using http:// works. https:// does not ... even with a fully validated SSL certificate.
I can only guess that removing the https:// part in fact reverted to http:// in the background.
RE: Octoprint HTTPS Validation on Mac with 2.3.0
We are looking into this topic (again). The issue is with the OSX built in SSL library, which does not accept self signed certificates for an unknown reason. However OSX ships with curl application that links libcurl library, which accepts the self signed certificates happily. We have verified, that the OSX built in libcurl does not link the built in SSL library, but OpenSSL (sic!). In Cuppertino, they do not eat their own dog food! We are now trying to link the system libcurl library, however it is a painful undocumented process and we need to test on a range of OSX versions. In worst case we will have to compile libcurl & OpenSSL ourselves and include it into PrusaSlicer. As you see, such a seemingly trivial task may be quite demanding and due to the lack of support / documentation by Cuppertino our team already lost around two manweeks on the topic.
RE: Octoprint HTTPS Validation on Mac with 2.3.0
Have not looked into this in a while. Seems to be resolved by now.
Using: Prusa Slicer 2.6.0+MacOS-x64
Thank you!
RE:
18 months on from the last post, I'm running into this same problem -- self-signed cert with signing root accepted in the system keychain, https connection works fine in browsers etc, but not in prusa slicer. I can open http and things work fine, but the https connection inside prusa slicer is still refusing the cert 🙁
I see there's a bug report ( https://github.com/prusa3d/PrusaSlicer/issues/13005, which references the prior bug https://github.com/prusa3d/PrusaSlicer/issues/5506) which says the problem re-appeared somewhere between 2.7.x and 2.8.0.
MacOS 15.3.2 (sequoia), Octoprint (https forwarding via haproxy 2.2.9-2), PrusaSlicer 2.9.1