Subsites are being created in HTTP

I created my multisite over HTTP. Then I added wildcard SSL on my server, and changed the main site URL to HTTPS. But still, when I create a new subsite, it's created in HTTP, not in HTTPS.

How can I set it so new subsites will be created over HTTPS when the sites are created?

  • James Morris

    Hello Mark,

    I hope you are well today.

    This question has been asked a few times here. I believe the following explanation by my colleague Dimitris should get you fixed right up. :wink:

    https://premium.wpmudev.org/forums/topic/how-to-change-the-http-to-https-in-multisite

    Let us know if you have any further questions. We'll be happy to help! :slight_smile:

    Best regards,

    James Morris

  • Mark

    There's one issue that the find & replace script mentioned... it couldn't replace the affiliate tables because it said it didn't have a unique key.

    The table "*DB*_#_affiliatedata" has no primary key. Changes will have to be made manually.

    I received that message several times for different subsites. I haven't started using that affiliates plugin, though, so would it be enough to simply delete the plugin and then reinstall it later? Would that delete those tables and then likely change then to https:// when I re-install the plugin?

  • Mark

    Okay, so I went through the whole process outlined above, and when I create new sites, they are still being created in http://

    The side effect is that the login page loads an insecure form, even if I go into the site settings and change the site to https:// manually after installation. It will try to force a redirect to https:// because of some other rules in effect, but the form is calling the http:// version of the site. I can't go in and hardcode that call to fix it because that changes all my subsites.

    Any ideas?

  • Kasia Swiderska

    Hello Mark,

    I'm sorry for the delay on our end - can you tell me if you still have this issue on your site? If yes Could you please send in the following via our secure contact form https://premium.wpmudev.org/contact/ :

    - Mark to my attention, the subject line should contain only: ATTN: Kasia Swiderska
    - Do not include anything else in the subject line, doing so may delay our response due to how email filtering works.
    - Link back to this thread
    - Include WordPress network admin access details (login address, username & password)
    - Include FTP log-in details (hostname, username & password)
    - PhpMyAdmin access
    - Include any relevant URLs for your site

    IMPORTANT: Please make sure you select "I have a different question" for your topic, so it doesn't go back to the forums - this and the subject line ensure that it gets assigned to me.

    Please confirm here that you send those credentials

    kind regards,
    Kasia

    • Mark

      Hello, Kasia!

      Thank you for coming back to this thread. I was actually working on some related issues with some WPMUdev support reps via live chat and they were able to help me resolve the issue. Here's the update:

      I migrated all my sites to another network I had set up previously. (The old network was done without SSL. I built a new network to install SSL from the start, but I installed SSL after I installed wordpress.)

      After speaking with some support reps, we determined that the site needed to be installed with ssl already in place, so after migrating all the sites in the network, I created a new database, renamed the public_html folder and reinstalled a fresh version of wordpress into a new public_html folder. I brought a couple of my files into the new installation, like the php.ini files in the root folder and in the wp-admin folder.

      That gave me a fresh install, which I accessed via https:// every step of the way. Once I did the initial wordpress setup, I verified that the single site was created in https://, and it was.

      After adding the line to wp-config to allow multisite, I went through the multisite activation, all through https://.

      I verified that the main site was still showing https:// in the Home and Site URL fields, and it was.

      I added a new site, and it installed the site in http.

      So I hopped on live chat again, and that rep asked me to try installing a site with the "Really Simple SSL" plugin activated.

      That worked.

      I'm not sure why wordpress is refusing to create sites in https:// without a plugin installed. If I can get it to force SSL on site creation without a plugin, that would be great. I haven't tried using domain mapping yet for that purpose, although I will have domain mapping activated when I start migrating sites back into this network.

      The new network is live at https://dgtl.church now.

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.