I updated to v220.127.116.11 of Domain mapping and notice that there is a conflict with iThemes Security 'Hide-backend' feature when Force http/https feature of Domain mapping is used.
Previously with Domain mapping v18.104.22.168 I utilize iThemes Security 'Hide-backend' feature with login & admin SSL enabled via the wp-config file to provide a secure and easy to remember login url (e.g. https://site1.example.com/login)
The Hide-backend adds the following to .httaccess.
# BEGIN Hide Backend # Rules to hide the dashboard RewriteRule ^(/)?login/?$ /wp-login.php [QSA,L]
However as of v22.214.171.124 of Domain mapping I can no longer enable SSL via the wp-config file as this causes too many redirects see: https://premium.wpmudev.org/forums/topic/sub-sites-login-generates-err_too_many_redirects-v4407#post-894455
The problem I'm now experiencing is once Force http/https is enabled the login page on sub-sites are not severed via SSL (e.g. http://site1.example.com/login) and attempting to login generates a 404.
Is the domain mapping plugin hard coded to use or apply SSL to the wp-login.php or wp-admin.php files?
iThemes Security 'Hide-backend' uses Custom Action can domain mapping plugin work with this?
Custom Action: WordPress uses the "action" variable to handle many login and logout functions. By default this plugin can handle the normal ones but some Apps and themes may utilize a custom action (such as logging out of a private post). If you need a custom action please enter it here.