Setup a New Self-Signed SSL Certificate on OctoPrint (“Enable HTTPS”)

I am still using my own trusted root certificate authority that I've manually imported into windows with a Dynamic DNS service.

late to the party here and sadly not very savvy on the pi. still here i am, muddling my way through all this techno, hopeful for a positive outcome. i do love this little hobby of mine, even when it gets me in high waters of what the ???

trying to find my 'newly created certs' and get past the NET::ERR_CERT_AUTHORITY_INVALID

is this post a reference on defaulting these settings? or a post denoting how to genderate an SSL certificate?

the command you are quoting is one for copying a file from the pi to your local machine. If you are on a windows machine I would recommend using winscp or filezilla ftp client to remotely connect to the pi and transfer the file over to import into your local device to get around that error message.

You can use FileZilla in place of SCP

Hi,

I know this is an old post, and hopefully someone can help.

I have followed the instructions and got https working, and it get to the login page but cant log in. I can log in on http, just not on https.

Not sure where I have gone wrong, have check the setup several times.

Cheers

Thank you for writing this guide! It has helped me set up SSL on a few of my OctoPi installations.

I use PrusaSlicer on MacOS and Windows machines to slice files and upload Gcode to my OctoPi servers. On MacOS, PrusaSlicer seems to be using an outdated mechanism to validate SSL certificates and I kept running into SSL errors when I tried to configure my printers in PrusaSlicer on my MacBook Pro.

The temporary fix was to copy the contents of my local certificate from my octopi install over to my macbook and append /etc/ssl/cert.pem with the the contents of this file. After restarting PrusaSlicer on my MacBook, I was able to successfully test the connection and the "upload/upload and print" options worked as expected.

Could you add this note to your original post? In the meantime, I have posted a similar note to this PrusaSlicer github issue:

Thank you!