SSL cert and Chrome

QuickBox Support
, ,
#1

Hi,

in the past, to avoid the continuous chrome warning, I had created a self-signed certificate and I installed it in my browser using the appropriate function in the chrome settings. In this way the site was recognized as trustworthy.

I would do the same with QuickBox so that the dashboard and rutorrent will be recognized as trustworthy. So, where do I need to put my self-signed cert?? and then, do I need only to modify “SSLCertificateFile” and “SSLCertificateKeyFile” in “/etc/apache2/sites-enabled” making them point to the folder where my cert resides?

#2

Interesting, self-signed certificates (those not validated by an authority) would still pose prompts on-screen when accessing these self-signed ip/url… unless like you say… you store it in your browsers safe/allowed database. Tends to be a headache.

You can place the self-signed cert wherever you like, just as long as the key/cert/pem etc. etc. have the proper locations when included in your apache default-ssl.conf file.

You may additionally request via PM (to yours truly) that you have a unique subdomain on the QuickBox DNS (eg; YOURSUB.quickbox.io). This will provide you an A record to point your IP towards and then you can make use of a valid Let’s Encrypt certificate.

#3

Thanks,

I’ve created a self-signed cert and installed it in my browser. Now chrome not warn me again and the dashboard and rtorrent are seen as reliable.

Thanks anyway for your proposal!