Hi WPMUDev,
I hope your day is going well :slight_smile:
I have some Qs regarding Domain Mapping and working w/ HTTPS.
Here is a beginning scenario to work from, and I am hoping to have y’all confirm that my next iteration is headed in a good direction.
Primary:
Database values:
SITEURL – https
HOME – https
Domain Mapping Network Settings:
Server IP: 185.56.85.36
Admin Mapping: Original
Login Mapping: Original
Cross-Domain: Yes
Verify: No
Force HTTPS Login/Admin: No
Force HTTPS Frontend: No
Subsites:
Database values:
SITEURL – https
HOME – http
Domain Mapping Subsite Settings:
Protocol: http
Fresh Install of WPMS
Primary site database values for SITEURL and HOME have been changed to use HTTPS via Host’s WP Tool for SSL Configuration.
Subsite database value for SITEURL has been changed to use HTTPS via network > sites > edit > settings
Theme: Twenty Fourteen
Plugins: (i=installed, a=active, n=network active)
Domain Mapping – n
WPMUDev Dashboard – n
Jetpack – i
Diagnose – i
Status: Working as expected, almost!
Primary is forced to HTTPS for Frontend.
Primary is forced to HTTPS for Login/Admin.
Subsites are forced to HTTPS only for Login/Admin.
Subsites are NOT forced to HTTP for Frontend, but do default to HTTP
(I have NOT set Subsites’ HOME values to use HTTPS as I know that will later cause issues with DM)
Screenshot 1: Primary Site
Screenshot 2: Subsite
Next Activated DM & WPMUDev Dashboard
Successfully applied scenario settings (see sidebar left) to DM.
Logged out, cleared browser.
Retested URLs:
Primary is forced to HTTPS for Frontend.
Primary is NOT forced to HTTPS Login/Admin.
Subsites are NOT forced to HTTPS for Login/Admin.
Subsites are NOT forced to HTTP for Frontend.
Logged in to https://tivism.com
Mapped URL http://www.tivism.org to https://tivism.com/tivismorg-secure-access
The domain validation wheel just spun, though I have ‘Verify’ set to ‘No’
The domain mapping worked, in that http://www.tivism.org will now resolve.
However all kinds of crazy redirect loops and http/https switches ensue when trying to login and navigate to site dashboard > frontend or to/from other subsites in network.
So, in this situation, I am wondering which way y’all would go:
1) Setup without changing any database values to use HTTPS – let DM handle all of this.
Server IP: 185.56.85.36
Admin Mapping: Original
Login Mapping: Original
Cross-Domain: Yes
Verify: No
Force HTTPS Login/Admin: Yes
Force HTTPS Frontend: Yes
2) Leave database settings in place for SITEURL & HOME as discussed above – bring DM Network Settings inline with the database settings:
Force HTTPS Login/Admin: Yes
Force HTTPS Frontend: Yes
2a) Leave database settings in place for SITEURL & HOME only for Primary, Subsite SITEURL values set to HTTP default – bring DM Network Settings inline with the database settings:
Force HTTPS Login/Admin: Yes
Force HTTPS Frontend: Yes
Thanks for your insights!
Kind Regards, Max
PS. SUPPORT ACCESS is ACTIVE – Please log in and poke around if you’d like to see behaviors! Diagnose Plugin will show you further server info :slight_smile:
[attachments are only viewable by logged-in members] [attachments are only viewable by logged-in members]