wadimw

Hi,

@webdevshyam this is not exactly the case for me. Indeed, my .htaccess does redirect to https://www.domain.com version immediately (tompost rule in file) but when I access website via https://domain.com the dafault server certificate is being supplied before the redirect can take place, which results in ERR_CERT_COMMON_NAME_INVALID.

@gowebsmarty is there any way to override detection and force creation for both www and non-www versions?

For anyone with similar problem, I just restored the page broken by Elementor to previous version.

Thanks, the restored option sure did help. You may be interested in fact, that before update I went ahead and created a certificate just for non-www address (as Your plugin stated) but my server actually identified it as www-only certificate so the detection may be somewhat bugged.

I have the same problem. My domain reklmay-arek.pl has an A record pointing to server’s IP and a www.reklamy-arek.pl CNAME record pointing to reklamy-arek.pl. WordPress is set to https://www.reklamy-arek.pl and inputting both into browser works fine, but it seems the plugin offers me renewal only for non-www address. How could I convince it to create a both-addresses cert?

• This reply was modified 4 years, 1 month ago by wadimw.