I found something for forcing users to the HTTPS page when loging in. See this post, Multisite, SSL (wildcard) and forced login, http://wordpress.org/support/topic/multisite-ssl-wildcard-and-forced-login?replies=10
It says you must use FORCE_SSL_ADMIN.
Larry
User is also havign issues logging in with Chrome, but not IE.
No need to make multiple posts 😉 It’s all one and the same.
Did you get this part sorted? If so, have you flushed cookies/cache from your browsers and logged in again?
I don’ think these are the same issues. The trouble here was directed at having the Lock icon appear in the browser when trying to login after setting define(‘FORCE_SSL_LOGIN’, true); I changed this line to define(‘FORCE_SSL_ADMIN’, true); and now users see the Lock icon in the browser.
The other issue was posted under a different heading (which has now been closed) regarding not being able to see the login page when using https with Chrome or Firefox. The error I get from Chrome is:
This webpage is not available
The webpage at https://xblogs.kentlaw.edu/wp-login.php might be temporarily down or it may have moved permanently to a new web address.
Error 324 (net::ERR_EMPTY_RESPONSE): Unknown error.
FireFox tells me:
Data Transfer Interrupted
The connection to xblogs.kentlaw.edu was interrupted while the page was loading.
The browser connected successfully, but the connection was interrupted while transferring information. Please try again.
* Are you unable to browse other sites? Check the computer’s network connection.
* Still having trouble? Consult your network administrator or Internet provider for assistance.
Also, I can navigate to https://xblogs.kentlaw.edu using IE but not Chrome or FireFox
FORCE_SS_LOGIN *only* makes the transaction of sending username/password to the server HTTPS. Take a look at the source code in your browser when you go to the login page with FORCE_SSL_LOGIN on. You’ll notice that in the <form …> tag, the action points to an HTTPS page. The only way currently to have the lock icon appear is to use FORCE_SSL_ADMIN.
The error with Firefox and Chrome sound like they could be related to how your server is set up to handle HTTPS. Do you have a firewall that’s blocking port 443 by chance?
ETA: I just tried loading your page. My Chrome install ran for about a minute trying to find a connection, but eventually timed out. That tells me it is likely a server/firewall issue.
Right you’re getting the error on Chrome AFTER you switched to SSL, so … related. 🙂
Sorry, but not related. I have users that access the login page using Android and IE. Users cannot access the login page using Chrome. If this was a firewall issue then all browsers would be blocked. And I did verify with my network admins that port 443 and 80 are open.
If things work with IE, why don’t they work with Chrome?
