You will need to have the website working on http first before continuing with this troubleshooter. Now let's assume the website is accessible over http and we get the above error when trying to browse over https.
The problem is seen because the SSL handshake failed and hence the error message was seen. There could be many reasons. We will follow a step-by-step approach to solve this problem. Check if the server certificate has the private key corresponding to it. Refer the below picture:. If private key is missing, then you need to get a certificate containing the private key, which is essentially a. PFX file. There is a command that we could try to run in order to associate the private key with the certificate:.
Note: 1a 1f 94 8b 21 a2 99 36 77 a8 8e b2 3f 42 8c 7e 47 e3 d1 33 is the thumbprint of the certificate. Open the certificate and click on the details tab. Scroll down to find the thumbprint section. Select the thumbprint section and click on the text below. Below is a snapshot for your reference:. Note: This command doesn't succeed always.
If this fails, then you need to get a certificate containing the private key from the CA. The file extension for a certificate containing private key is.
We went pass the first hurdle and now we have a server certificate containing the private key installed on the website. However, we still get the same error as above. The website is still not accessible over https. Download X Install the tool and run it on the server. You have a private key that corresponds to this certificate but CryptAcquireCertificatePrivateKey failed. So let's try the below steps one by one:. All the private keys are stored within the machinekeys folder, so we need to ensure that we have necessary permissions.
If the permissions are in place and if the issue is still not fixed. Then it must be a problem with the certificate. It may have been corrupted You may see an error code of 0xa in the SChannel event log. We will test if the website works with a test certificate.
Take a back-up of the existing certificate and then replace it with a self-signed certificate. Privacy policy. Web PI installs the latest versions of available Web Platform offerings with just a few simple clicks. To install IIS manually, use the following steps:.
In Server Manager , select Dashboard , and click Add roles and features. On the Select Destination Server page, select Select a server from the server pool , select your server, and click Next. On the Select Features page, note the preselected features that are installed by default, and then select CGI. On the Select Role Services page, note the preselected role services that are installed by default, and then click Next.
On the Confirm Installation Selections page, confirm your selections, and then click Install. On the Installation Progress page, confirm that your installation of the Web Server IIS role and required role services completed successfully, and then click Close. In the Windows Features dialog box, click Internet Information Services , note the preselected features that are installed by default, and then select CGI.
Web PI will add several items to the install list three in my case ; then click on the big Install button at the bottom. Next, you will need to accept the license terms of the different components. If any components fail to install, you might have to install them manually.
Be sure to download a non-thread safe version. Removing these checks improves performance. Finally, go to your PHP folder e. Then you will see it in IIS Manager:. When you open it, you will immediately see a warning about your php.
PHP allows extensions to be installed and enabled. In my default installation, I already had 40 extensions installed. You can also install them through the PHP Manager. Likewise, you can enable and disable extension by editing the php. It includes caching mechanisms like user data cache, session cache, file system cache, and relative path cache.
Be sure to download from the development folder , because the other files are for the Web PI version of WinCache. In the WinCache forums , you can read that support for 7. Create a new file in your favorite text editor and add only the following line:. This is where IIS will be hosting your websites. Keep in mind that putting a phpinfo. It exposes too much information about your server that hackers could use to attack you. It has also stood the test of time very well. It has a vast and vibrant community and includes some tried and tested products such as WordPress and Drupal.
In the example above, we added our tiny one-file PHP website to the wwwroot folder.
0コメント