Opened 2 months ago

Closed 3 weeks ago

#14370 closed Bug/Something is broken (fixed)

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 (2)

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

Download all attachments as: .zip

Change History (5)

Changed 2 months ago by

Error log from web configuration interface.

comment:1 Changed 2 months 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 months 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

Changed 3 weeks ago by

comment:3 Changed 3 weeks ago by

  • Resolution set to fixed
  • Status changed from assigned to closed

After some fiddling, I figured this out. Things are running smoothly with https. Removing the "*" is working fine and I can still create new sites. Once created, each new site must be manually added to the domain names in the hosting order. One important thing seems to be removing a blank last line. Unless, I am mistaken if that blank last line persists there is a soft error. If the blank last line is removed, there is no error and things work fine. Figured I'd share that insight.

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.