If you install Plesk for Windows and enable the openssl extension for any PHP version, the default path will be c:\usr\local\ssl\openssl.cnf, which is non-existent.
So by default, openssl will never work without the following manual steps on the host:
- mkdir c:\usr\local\ssl\
- Copy C:\Program Files (x86)\Plesk\admin\conf\openssl.cnf to c:\usr\local\ssl\
- Set Read Permissions / ACL on c:\usr\local\ssl\openssl.cnf
This way the end user is not able to customize the file though, as it will be global for all websites. If you could set it to e.g. {WEBSPACEROOT}, the end user would have the option to supply his own openssl.cnf (or have it put there automatically by the webhoster) and customize settings.
If not, at least have the c:\usr\local\ssl\openssl.cnf created by the setup routine, so openssl works out of the box, with no manual steps necessary.
If you install Plesk for Windows and enable the openssl extension for any PHP version, the default path will be c:\usr\local\ssl\openssl.cnf, which is non-existent.
So by default, openssl will never work without the following manual steps on the host:
- mkdir c:\usr\local\ssl\
- Copy C:\Program Files (x86)\Plesk\admin\conf\openssl.cnf to c:\usr\local\ssl\
- Set Read Permissions / ACL on c:\usr\local\ssl\openssl.cnf
This way the end user is not able to customize the file though, as it will be global for all websites. If you could set it to e.g. {WEBSPACEROOT}, the end user would have the option to supply his own openssl.cnf (or have it put there automatically by the webhoster) and customize settings.
If not, at least have the c:\usr\local\ssl\openssl.cnf created by the setup routine, so openssl works out of the box, with no manual steps necessary.