Issue Plesk and Lets encrypt issues

[360webfirm]

hello,

I have installed lets encrypt plugin and I am using for my main and wildcard sub domains. My issue is that when going to www.subdomain.mainsite.com, I get a CERTIFICATE error.

I have spent days searching the web and frankly I am exhausted trying to sort this out.

my sites work like this.

https://mainsite.com, www.mainsite.com, mainsite.com - All go to https which I want.

mainsite.com and https://subdomain.mainsite.com work great.

This is my issue - when typing in www.subdomain.mainsite.com, this gets a certificate error. Some people woudl actually still use the www and if they do, I loose a client. I cant even check website speed test because GTMetrix cannot read website due to SSL

I tried to create an SSL using several sub domains and I cannot even verify it because PLESK has issues with .well-known folder. Seriusly, I am so tired of this..

Anyone can assist it would be very appreciated... Either to get www.sub.domain.com to work with SSL or somehow redirect the www.sub.domain.com to https:// version..

 

[learning_curve]

@360webfirm Have you created the www as an additional sub-domain?
Here are two old, non-Plesk but relevant posts: Try THIS one and also THIS one
There are lots of other, newer relevant posts too, but these might explain it quite quickly for you

 

[360webfirm]

you mean when I craete it here - SSL For Free - Free SSL Certificates in Minutes ?

How would I enter this

 

[learning_curve]

No.... before that i.e. DNS
If you carefully read both of the posts via the two links posted, then look again at the question we asked, you'll understand why.

 

[360webfirm]

I have tried to create a cname and have read through, its simply not working.

 

[360webfirm]

The links you sent me do not apply to Wildcard sub domains and also I am using SSL with lets encrypt.

Everything works great, except for the second level sub domain www which cause issues.

 

[learning_curve]

A www-sub-domain url is dependent (amongst other things) on the correct DNS being in place before you reach the SSL certificate issue / question... That's why those links (which relate to www.subdomain DNS) were posted, because the DNS for subdomain.mainsite.com and https://subdomain.mainsite.com and www.subdomain.mainsite.com is not the same... which is why we asked the question. We can ask the same question, but in an easier way:

If you enter your url: www.subdomain.mainsite.com is this url correctly resolved but with an SSL related error like this sample Firefox pic?? >>

Or, if you enter your url: www.subdomain.mainsite.com is that url itself not resolved / not found?