Opened 2 weeks ago

Last modified 2 weeks ago

#14370 assigned Bug/Something is broken

Error when trying to configure website to https

Reported by: Owned by:
Priority: Medium Component: Tech
Keywords: Cc:
Sensitive: no


To change our website from http to https I followed the instructions at

When I went to the site, it would not load under either http or https. I checked the web configuration panel and spotted an error. When I switched back to http the site loaded fine. So that the site isn't down, for the moment I'm keeping it at http. However, it seems clearly advisable to have it run as https. The error message is attached as a graphic. Any help on this would be very much appreciated.

The site is a wordpress network with wildcard subdomains. I don't know if perhaps that is part of the issue.

Attachments (1)

Capture2.JPG (48.9 KB) - added by 2 weeks ago.
Error log from web configuration interface.

Download all attachments as: .zip

Change History (3)

Changed 2 weeks ago by

Error log from web configuration interface.

comment:1 Changed 2 weeks ago by

  • Owner set to
  • Status changed from new to assigned

Hi, I thik the problem is the wildcard verison of your domain in the web configuration domain list. "*" Out automated certificate generation won't be bale to create a cert for the wilcard. You can remove that and add any specific subdomains of you plan on using before setting the web configuration to https.

comment:2 Changed 2 weeks ago by

Ok, following your guidance, I removed "*" and added in the two subdomains as follows:


I left the web configuration setting as http and checked each site, it worked fine. Then I changed the web configuration setting to https and neither subdomain site worked. I left the aforementioned list of subdomains, included the wildcard as before, and set it back to http for the time being. Not knowing any better, I'm sort of concerned that removing "*" will cause problems with the wildcard subdomain wordpress network. Perhaps to make this work, configuration of the WP network needs to be changed, and I can certainly look into that. I found a similar ticket from a couple of months indicating that, consistent with your suggestion, I'll need to manually add each subdomain. That is no problem provided I can still occasionally create project sites using the wordpress superadmin interface. Having added the subdomains, I'm not clear why changing the setting to https didn't work properly. I'd still like to make this change to https and would appreciate any further guidance you might have.

Thank you very much, n

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.