-
Hi, Apologies if this has already been covered somewhere. I followed the Part-DB installation guide for Debian 11 (Bullseye) instructions after I failed to get the Docker container working when installing through Portainer (500 Error). So my install is working, very cool, using http://192.168.1.1 but as I started to set it up I could see that an HTTPS setup is pretty much mandatory, DigiKey and the Scanner are the first two things I tried and neither work without HTTPS. I went through the instructions and I didn't see anything talking about how to enable HTTPS? This is a personal home setup on my NUC Proxmox server. I'm happy in Linux, Docker not so much, so what are hobbyists doing to get part-db using https so digikey works? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
If you have installed Part-DB directly, then you can follow any tutorial for setup TLS in apache (or nginx, depending). That is nothing special for Part-DB, thats bascially just normal webserver config: Something like this: https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-ubuntu If you are using docker, you should put it behind a reverse proxy, which handels the HTTPs connection. |
Beta Was this translation helpful? Give feedback.
-
Thanks, I followed this and have https now, the scanner works: I'm still wrestling with digikey, I get this error: HTTP/1.1 401 Unauthorized returned for "https://api.digikey.com/Search/v3/Products/Keyword" I have the digikey side setup, on there I made the Callback URL: https://10.10.1.21/ Maybe the Digikey API need a internet routable/resolvable site with a properly signed SSL FQDN, absolutely no idea. |
Beta Was this translation helpful? Give feedback.
-
FIXED: Actually, at https://developer.digikey.com/ edit the Digikey app you created there and switch "Product Information V4" to None and "Product Information V3 (Deprecated)" to "Product Information" and save it, that worked for me. |
Beta Was this translation helpful? Give feedback.
If you have installed Part-DB directly, then you can follow any tutorial for setup TLS in apache (or nginx, depending). That is nothing special for Part-DB, thats bascially just normal webserver config:
Something like this: https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-ubuntu
If you are using docker, you should put it behind a reverse proxy, which handels the HTTPs connection.