hubcap
Forum Replies Created
-
Forum: Networking WordPress
In reply to: Problem with HTTPS Plugin and Multi-siteLooks 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
Forum: Networking WordPress
In reply to: Problem with HTTPS Plugin and Multi-siteI 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.
Forum: Networking WordPress
In reply to: Problem with HTTPS Plugin and Multi-siteHi,
I have given up on this approach – the main reasons for trying it were three fold:
- we use the same www domain for our content website and our application – HTTP = content, HTTPS = application. So using same domain for content and admin gives us a conflict on https://www.mydomain.com
- we have wildcard cert for *.mydomain.net and therefore same cert could be used for admin on all sub-sites (sub sites will be different main domains)
- using the same main domain for all admin makes for more easy apache virtual host setup on reverse proxy.
So it would be great if this approach works.
However in the interests of time and no solution we have now decied to move our application to “app.mydomain.com” and enabled HTTPS using HTTPS Plugin. We will need to get new certs for all domains we host to support the admin traffic. A work-around at least.
Thanks for the input
Forum: Networking WordPress
In reply to: Problem with HTTPS Plugin and Multi-siteJan, hi
Thanks for replying
Last question first – do you mean to actually access my wordpress? I’m afraid it’s locked away internally so not really readily available.
1. I have a Wildcard cert covering *.mydomain.net
2. I have SSL into Reverse Proxy – seperate vhosts for 80 and 443 and cert on 443 vhost.
3. I take it you mean a WordPress SSL plugin (different from HTTPS Plugin)? – can you point me at that? I wasn’t planning to run SSL on the WordPress server – just into Proxy – HTTPS Plugin has support for proxy setup and (I believe) expects to receive HTTP inbound from proxy, but manages the links on pages to include the HTTPS.
Forum: Networking WordPress
In reply to: Problem with HTTPS Plugin and Multi-site@ipstenu, hi – you may have missed my question above – is it a bug? I’ve posted it on HTTPS Plugin forum to see if I can get a view from developers.
Forum: Networking WordPress
In reply to: Problem with HTTPS Plugin and Multi-siteWell it’s actually a feature of the HTTPS plugin to offer an alternate domain name (SSL Host).
I did have a quick look, but wasn’t keen to add another component to the mix if the two parts (HTTPS Plugin) and (Multisite) were meant to be able to do this.
I do think we might need domain mapping for another requirement – so I might look at adding.
Thanks
Forum: Networking WordPress
In reply to: Problem with HTTPS Plugin and Multi-siteHi – I note from this thread that the developers imply that HTTPS Plugin and Multisite are designed to work. Can I get this looked at as a bug?
Forum: Networking WordPress
In reply to: Problem with HTTPS Plugin and Multi-siteWith Multi-site
With HTTPS off
WordPress sites on (this Worked)
- wp.domain.com
- site1.wp.domain.com
- site2.wp.domain.com
Admin on (this Worked)
- wp.domain.com/wp-admin
- site1.wp.domain.com/wp-admin
- site2.wp.domain.com/wp-admin
i.e. no use of secondary domain root
With HTTPS on
WordPress on (this Worked)
- wp.domain.com
- site1.wp.domain.com
- site2.wp.domain.com
Admin on (This Failed)
- wp.domain.net/wp-admin
- wpsite1.domain.net/wp-admin
- wpsite2.domain.net/wp-admin
So the admin is actually only on a another domain when HTTPS is on (using the setting within HTTPS SSL Host for each site) – which works for single site.
One side point – the reason that the lowest order part of admin domain is different “site1.wp.domain.xx” moves to “wpsite1.domain.xx” is that my wildcard certificate on *.domain.net doesn’t cover sub.sub domains. But I believe this to be not relevant as the main site (wp.domain.net) doesn’t work either.
Hope that’s clearer.
Forum: Networking WordPress
In reply to: Problem with HTTPS Plugin and Multi-siteFor Single-site
With HTTPS off
- WordPress on wp.domain.com
- Admin on wp.domain.com/wp-admin
With HTTPS on
- WordPress on wp.domain.com
- Admin on wp.domain.net/wp-admin – due to SSL Host setting in HTTPS Plugin
Forum: Networking WordPress
In reply to: Problem with HTTPS Plugin and Multi-siteYes, well with HTTPS Off – all pages, including admin, where within wp.domain.com and then with HTTPS on (and SSL domain set within HTTPS config page to wp.admin.net) – that also worked across the two domains.