search

prusa3d / PrusaSlicer

G-code generator for 3D printers (RepRap, Makerbot, Ultimaker etc.)
https://www.prusa3d.com/prusaslicer/
GNU Affero General Public License v3.0
7.51k stars 1.9k forks source link

Prusa Slicer 2.8.0 SSL Connectivity with Octoprint #13005

Open mcstoufer opened 5 days ago

mcstoufer commented 5 days ago

Description of the bug

Versions:

Attempts to send sliced files to a local LAN Octoprint server are failing with:

Could not connect to OctoPrint: SSL peer certificate or SSH remote key was not OK:
SSL: certificate verification failed (result: 5)
[Error 60]
Note: OctoPrint version at least 1.1.0 is required.

Its a self-signed cert that has been trusted in the Keychain and does not expire until next year. I'm attempting to reach it via https://octoprint.local/ I've also verified the API key is correct. It worked just fine in prior PS versions.

Cert was generated per instructions: https://community.octoprint.org/t/setup-a-new-self-signed-ssl-certificate-on-octoprint-enable-https/30256

I can reach the web front end just fine from seperate Chrome browser and the embedded "Physical Printer" tab. Chrome tells me the self-signed cert is all valid and its happy to use it.

I can provide both Octoprint and PrusaSlicer? logs if needed.

Project file & How to reproduce

  1. A valid SSL cert is installed on OctoPrint server and trusted in the keychain on the host for which the PrusaSlicer app is run on.
  2. Attempt to create a new OctoPrint physical printer with an https:// prefix.
  3. Attempt to "test" connectivity. The aforementioned error will be displayed.

Checklist of files included above

Version of PrusaSlicer

2.8.0 MacOS-x64

Operating system

Mac OS 12.7.5

Printer model

MK4

mcstoufer commented 4 days ago
Screen Shot 2024-07-03 at 1 21 41 PM

One other odd issue: When I scan to see if the Octopi host is discoverable, it immediately finds this. However, this IP is the for the WiFi on the raspberry PI and not in use. I disabled WiFi on the raspberry Pi and now PS properly scans and finds its real ethernet address. Even selecting that as the source results in the same issue.

mcstoufer commented 4 days ago

Some Console logs when the OctoPrint host is "tested":

default 17:40:16.535793-0700    mDNSResponder   [R7543] DNSServiceQueryRecord(1D000, 0, <mask.hash: 'AK30i3nEo+OFQAtrqSvPhg=='>, Addr) START PID[9889](PrusaSlicer)
default 17:40:16.536300-0700    mDNSResponder   [R7544] DNSServiceQueryRecord(1D000, 0, <mask.hash: 'AK30i3nEo+OFQAtrqSvPhg=='>, AAAA) START PID[9889](PrusaSlicer)
default 17:40:16.537105-0700    mDNSResponder   [R7543] DNSServiceQueryRecord(1D000, 0, <mask.hash: '06OmF/Gr7w3oY65CBf3IAA=='>, Addr) STOP PID[9889](PrusaSlicer)
default 17:40:16.537163-0700    mDNSResponder   [R7544] DNSServiceQueryRecord(1D000, 0, <mask.hash: '06OmF/Gr7w3oY65CBf3IAA=='>, AAAA) STOP PID[9889](PrusaSlicer)
default 17:40:16.585259-0700    PrusaSlicer Trust evaluate failure: [leaf AnchorTrusted]