Resolved Having difficulty installing Wordpress into a directory

[Jack Yan]

Hi there, I’m doing a migration at the moment and I want to set up a Wordpress blog at what will be jackyan.com/blog (i.e. not in the root directory).

When I try to do a custom installation through Plesk (Websites & Domains > jackyan.com > Applications > choose Wordpress > Install (custom) > accept terms), at the top of the page there is this error message: 'Information: Apps cannot be installed on https sites of some of your domains because SSL/TLS support is not activated for these domains. To activate the SSL/TLS support, go to Websites & Domains and click Hosting Settings next to a domain name in the list.'

Here are the three scenarios I have tried:

SSL/TLS is switched on by default and I have left it as is, and I attempt to install to https:// jackyan.com/blog [added space to prevent the forum from changing the link]: Wordpress will not install.

SSL/TLS is switched on and I upload a certificate, and I attempt to install to https:// jackyan.com/blog: Wordpress will not install.

I choose to turn off SSL/TLS and select http:// jackyan.com/blog as the directory to use: Wordpress will not install.

Each time the error message remains.

In the past I have been able to install Wordpress into the main directory in other domains on Plesk without any trouble, but this is a site that requires it in a directory. Can you please tell me what I am doing wrong here?

Our host does not have the Wordpress tool that I have seen mentioned elsewhere.

Any advice is welcome, thank you!

 

[Bitpalast]

To activate the SSL/TLS support, go to Websites & Domains and click Hosting Settings next to a domain name in the list.'

Can you please provide a screenshot that SSL is checked and active and that a valid certificate was installed?

Can you please tell me what I am doing wrong here?

The error message said it all.

 

[Jack Yan]

Here you go, Peter.

 

[Jack Yan]

I did manage to get it going by basically going back to the same page multiple times and using different password combinations. When I contacted you, there were no password warnings but there were on day two. Eventually that error message disappeared without any changes to the SSL or certificate (still in use now).