Title: No https on subdomains
Last modified: January 5, 2022

---

# No https on subdomains

 *  Resolved [napsterion6](https://wordpress.org/support/users/napsterion6/)
 * (@napsterion6)
 * [4 years, 5 months ago](https://wordpress.org/support/topic/no-https-on-subdomains/)
 * Dear author,
 * I used your plugin to configure SSL Certificate on my website but from some time
   all my subdomains which doesn’t have SSL certificate are open with https with
   error (NET::ERR_CERT_COMMON_NAME_INVALID) – for example (ce4big.lifescience.pl
   or amici.lifescience.pl) always after opened main site first.
 * Can you help me with this?
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fno-https-on-subdomains%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Author [Mark](https://wordpress.org/support/users/markwolters/)
 * (@markwolters)
 * [4 years, 5 months ago](https://wordpress.org/support/topic/no-https-on-subdomains/#post-15220505)
 * Hi [@napsterion6](https://wordpress.org/support/users/napsterion6/),
 * to secure a subdomain you need to either generate a new certificate for each 
   subdomain or use a wildcard SSL certificate. A wildcard SSL certificate will 
   automatically secure the main domain and all subdomains. A wildcard SSL certificate
   can be generated by using the Let’s Encrypt DNS verification method.
 *  Thread Starter [napsterion6](https://wordpress.org/support/users/napsterion6/)
 * (@napsterion6)
 * [4 years, 5 months ago](https://wordpress.org/support/topic/no-https-on-subdomains/#post-15220514)
 * Dear [@markwolters](https://wordpress.org/support/users/markwolters/)
 * Yes but i don’t want to secure that subdomains. I wondering why browser try to
   open them with https even they are not secured.
 *  Plugin Author [Mark](https://wordpress.org/support/users/markwolters/)
 * (@markwolters)
 * [4 years, 5 months ago](https://wordpress.org/support/topic/no-https-on-subdomains/#post-15220525)
 * Hi [@napsterion6](https://wordpress.org/support/users/napsterion6/),
 * your site sets an HTTP Strict Transport Security header which will also force
   subdomains over SSL. Removing this header should make the subdomains available
   over [http://](https://wordpress.org/support/topic/no-https-on-subdomains/?output_format=md).
 *  Plugin Author [Mark](https://wordpress.org/support/users/markwolters/)
 * (@markwolters)
 * [4 years, 4 months ago](https://wordpress.org/support/topic/no-https-on-subdomains/#post-15263033)
 * Hi [@napsterion6](https://wordpress.org/support/users/napsterion6/),
 * did the above suggestion resolve your issue?

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘No https on subdomains’ is closed to new replies.

 * ![](https://ps.w.org/really-simple-ssl/assets/icon-256x256.png?rev=2839720)
 * [Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)](https://wordpress.org/plugins/really-simple-ssl/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/really-simple-ssl/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/really-simple-ssl/)
 * [Active Topics](https://wordpress.org/support/plugin/really-simple-ssl/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/really-simple-ssl/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/really-simple-ssl/reviews/)

## Tags

 * [SSL](https://wordpress.org/support/topic-tag/ssl/)

 * 4 replies
 * 2 participants
 * Last reply from: [Mark](https://wordpress.org/support/users/markwolters/)
 * Last activity: [4 years, 4 months ago](https://wordpress.org/support/topic/no-https-on-subdomains/#post-15263033)
 * Status: resolved