Problem with HTTPS Plugin and Multi-site

  • Resolved hubcap

    (@hubcap)


    11 years, 9 months ago

    I new to WordPress and doing a new build and having a problem adding HTTPS Plugin (v3.3.6) onto a multi-site environment.

    I’m looking to get my sites served via HTTP and all admin/login functions over HTTPS.

    My issue is that as soon as I enable the HTTPS plugin then all my admin functions start giving me a “Registration has been disabled” page – with a url http://wp.domain.com/wp-signup.php?new=wpsite1.domain.net

    I have WordPress on LAMP behind a separate Apache Reverse Proxy.

    First off I managed to get the HTTPS Plugin working on a single site install with admin on HTTPS. For this I used a seperate domain.

      Wordpress on wp.domain.com
      Admin on wp.domain.net

    On reverse proxy I have two virtual hosts – 1 for each of these – with SSL cert on *.domain.net.

    When I tried to add multi-site on the top of this I got into problems, so going back to a clean install, I am now trying the approach of getting multi-site working first before adding HTTPS ontop.

    I’ve followed this and got two sub sites working successfully with admin on HTTP.

      wp.domain.com
      site1.wp.domain.com
      site2.wp.domain.com

    The HTTPS configuration I am applying is:

    Site + SSL Host
    wp.domain.com + wp.domain.net
    site1.wp.domain.com + wpsite1.domain.net
    site2.wp.domain.com + wpsite2.domain.net

    The domains are included as ServerAliases in Proxy appropriate virtual host.

    and for each of these set:

      Force SSL Admin = On
      Force SSL Exclusively = On (but also tried with off)
      Proxy  = Yes

    Straight after “Save Changes” I can no longer get into any admin screen.

    Hovering over “Site Admin” on a HTTP site (e.g. site1.wp.domain.com) shows me that the target it wants to send me to is “https://wpsite1.domain.net/wp-admin.

    The request hits my WordPress server, log shows:

    That’s a 302 redirect and then a 404 not found

    And on my browser I just get the “Registration has been disabled” error (as above).

    Any assistance gratefully appreciated.

Viewing 4 replies - 16 through 19 (of 19 total)
1 2
  • jkhongusc

    (@jkhongusc)

    11 years, 9 months ago

    I do not understand your reasoning for trying to run WP multisite on a separate domain for the admin. WP does not support that use-case.

    Here is our configuration. It is similar to your situation:
    http://www.domain.com is our public static html server
    installed WP multisite subdomain on wp.domain.com
    wildcard cert for WP on *.domain.com
    WP site names: site1.domain.com,site2.domain.com, etc
    We force https for admin
    Site are optional http or https

    Thread Starter hubcap

    (@hubcap)

    11 years, 9 months ago

    I take it you don’t have a non-WordPress site already using your https://www.domain.com – which is/was our case and was part of the driver.

    We also (and I didn’t state this) need to host another domain (as a sub site) e.g. http://www.anothercompany.co.uk. The Admin part on https will require another certificate.

    So my hope (which I now realise through trial and error and this thread isn’t supported) was that I could move all the admin on to another common domain (since only our staff will see it) – one where we already have a wildcard cert.

    jkhongusc

    (@jkhongusc)

    11 years, 9 months ago

    Sorry I wasnt clear, yes our http://www.domain.com is on another non-WP server. That is why we installed WP on wp.domain.com, but we still have WP subdomains on *.domain.com (this is not typical for most users). If you use the Domain Mapping plugin you could easily map multiple subdomains on the same WP system (if you really want to).

    I just wanted to state what is possible with WP esp since your situation seems very similar to ours.

    Thread Starter hubcap

    (@hubcap)

    11 years, 9 months ago

    Looks close to what we’re trying to do – other than what I was originally (at time of OP) being asked to do was host http://www.domain.com on WP while https://www.domain.com was being used on another non-WP server.

    I could base WP on wp.domain.com, but I still need to make one sub site “www.domain.com” so I get the conflict on admin using HTTPS for that site.

    I’m happy(ish) with what I’ve got working. Thanks

Viewing 4 replies - 16 through 19 (of 19 total)
1 2

The topic ‘Problem with HTTPS Plugin and Multi-site’ is closed to new replies.