Customers and Admin have to log in twice?

[happydance]

:-" Can't figure this one out! My customers and my admin side both have to log in twice for them to actually log in. Any idea why this would happen? I'm assuming it is duplicate coding somewhere but I cannot find it. Help please. :'(

[ddp]

:-" Can't figure this one out! My customers and my admin side both have to log in twice for them to actually log in. Any idea why this would happen? I'm assuming it is duplicate coding somewhere but I cannot find it. Help please. :'(

 

Without any more details my guess is that this might have something to do with your ssl certificate.

 

How bout posting a link to your site so we can see it.

[Geotex]

Not always a solution to the problem, but I've seen it clear up this problem:

 

If you are using a shared ssl, or your ssl is on a different server (depending on your hosting provider setup), In your admin/configuration/sessions, make sure you have recreate session set to true.

[happydance]

Without any more details my guess is that this might have something to do with your ssl certificate.

 

How bout posting a link to your site so we can see it.

 

Sure. The site is www.myhappydance.com. It is a dedicated ssl.

[happydance]

Ok. Here's what we figured out. When we log in using myhappydance.com (no www.) it goes straight through with the first sign in. But when we add the www it signs in, forwards to the non-www and then makes you sign in again. Strange. I guess it is because our ssl certificate doesn't have the www...

[ddp]

Ok. Here's what we figured out. When we log in using myhappydance.com (no www.) it goes straight through with the first sign in. But when we add the www it signs in, forwards to the non-www and then makes you sign in again. Strange. I guess it is because our ssl certificate doesn't have the www...

 

You call the urls that are being accessed from your two configure.php files.

As soon as you hit a link on your site the url is directed by the settings in your (path to catalog)/includes/configure.php file.

Normally you would want your certificate to be issued for https://www.myhappydance.com

The problem is with your certificate or something interfering with it functioning correctly.

If you look at the padlock when you are accessing any secure pages there is line through the padlock.

This means the connection is only partially encrypted. This could cause problems as you have been experiencing.

 

I would try editing your (path to catalog)/includes/configure.php file to this to make sure everything is working ok without the certificate.

 define('HTTP_SERVER', 'http://www.happydance.com'); // eg,  http://localhost - should not be empty for productive servers
define('HTTPS_SERVER', ''); // eg, https://localhost - should not be  empty for productive servers
define('ENABLE_SSL', false); // secure webserver for checkout procedure?
define('HTTP_COOKIE_DOMAIN', '.www.happydance.com');
define('HTTPS_COOKIE_DOMAIN', '.www.happydance.com');

Then if that goes well try:

 define('HTTP_SERVER', 'http://www.happydance.com'); // eg,  http://localhost - should not be empty for productive servers
define('HTTPS_SERVER', 'https://happydance.com'); // eg,  https://localhost - should not be empty for productive servers
define('ENABLE_SSL', true); // secure webserver for checkout procedure?
define('HTTP_COOKIE_DOMAIN', '.www.happydance.com');
define('HTTPS_COOKIE_DOMAIN', '.www.happydance.com');

[ddp]

another way to test this would be to set it like this:

define('HTTP_SERVER', 'http://happydance.com'); // eg,  http://localhost - should not be empty for productive servers
define('HTTPS_SERVER', 'https://happydance.com'); // eg,  https://localhost - should not be empty for productive servers
define('ENABLE_SSL', true); // secure webserver for checkout procedure?
define('HTTP_COOKIE_DOMAIN', '.happydance.com');
define('HTTPS_COOKIE_DOMAIN', '.happydance.com');