Hot answers tagged

2

You have a few issues here: Your Root CA Certificate has a pathlen in its basicConstraints - not needed and not used, but it shouldn't cause problems. You have a certificate policy on your Root CA Certificate - this would be better applied by your Root CA to the subordinate CAs. If you wanted to change policy at a latter date, or add another policy, you'd ...


1

Neither one is specifically configured to handle ssl requests. In this case neither one should be listen at the port 443 at all, i.e. the browser should not be even able to connect to this port. Since you get responses or error messages the browser is obviously able to connect to this port so something is obviously setup to deal with this port. But it ...


1

Most websites using a CDN make use of a subdomain (e.g. cdn.yourwebsite.com) in order to deliver static assets from. This means that in order to deliver CDN assets over SSL you will need a certificate for the "cdn" subdomain. If you already have an SSL certificate installed on your origin, its likely that it is valid for yourwebsite.com and ...


1

Yes. This page, which was prominent in Google when I typed in your thread title, tells you how. However, this doesn't sound like a good idea. You may be better off getting better blocking software that lets you block by protocol as well as domain name. This is in a code block, sorry, formatting it properly takes ages. Look at the linked page for ...


1

If your clients are not updated browsers (or are not browsers at all), it is not sure that Letsencrypt's root certificate is configured on their side since it is pretty recent. On that issue, there is not much you can do from your side; the clients have to do their job and ensure that the root certificate used by Letsencrypt is configured. I tried ...


1

Do you have routing and remote access service installed? If yes, try to disable it (RRAS uses SSTP by default and it listens for 443 port and lsas.exe process which is using port in your situation is used for IPSEC also).


1

Recently, LetsEncrypt has announced the availability of their command line tools to generate valid certificates. No validation emails, no complicated configuration editing, no expired certificates breaking your website. And of course, because Let’s Encrypt provides certificates for free, no need to arrange payment. For those wondering if those ...


1

I solved this by splitting out all of my vhosts to individual .conf files for each one. I.e example.net.conf, game.example.net.conf and forum.example.net.conf and then running the below command through Let's Encrypt: letsencrypt-auto --apache --expand -d example.net -d www.example.net -d game.example.net -d forum.example.net I then reinstalled this on my ...



Only top voted, non community-wiki answers of a minimum length are eligible