SSL and Admin Login (config file) - only works with dedicated IP???

Hi,

Having issues with logging into the admin...we have an active SSL certificate (our own, not shared) as well as a dedicated IP address on the domain as well.

Our issue is with logging into the admin - the browser either doesn't connect (really long lag time with IE) or, in the case of Firefox, it runs into a 'Problem Loading Page' error. Here's Firefox's listed error:

=============================================

"The page isn't redirecting properly.

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

* This problem can sometimes be caused by disabling or refusing to accept cookies.

=============================================

Now I have a solution in place for this; however, it's not ideal but would like to know what everyone thinks might be the issue...having difficulties of another nature (different post/thread) which might be of the same issue...

Anyways, here's the configuration file that results in the above error:

// Define the webserver and path parameters
// Main webserver: eg, http://localhost - should not be empty for productive servers
define('HTTP_SERVER', 'http://www.screenprintcatalog.com');
// Secure webserver: eg, https://localhost - should not be empty for productive servers
define('HTTPS_SERVER', 'https://www.screenprintcatalog.com'); // eg, https://localhost
define('HTTP_CATALOG_SERVER', 'http://www.screenprintcatalog.com');
define('HTTPS_CATALOG_SERVER', 'https://www.screenprintcatalog.com');

// secure webserver for catalog module and/or admin areas?
define('ENABLE_SSL_CATALOG', 'false');
define('ENABLE_SSL_ADMIN', 'true');

// NOTE: be sure to leave the trailing '/' at the end of these lines if you make changes!
// * DIR_WS_* = Webserver directories (virtual/URL)
// these paths are relative to top of your webspace ... (ie: under the public_html or httpdocs folder)
define('DIR_WS_ADMIN', '/test/admin/');
define('DIR_WS_CATALOG', '/test/');
define('DIR_WS_HTTPS_ADMIN', '/test/admin/');
define('DIR_WS_HTTPS_CATALOG', '/test/');



And here's what seems to be working right now - substituting in the dedicated IP address seems to help the problem with the Admin login page but ends up flipping back to the usual domain if you browse around the admin...


// Define the webserver and path parameters
// Main webserver: eg, http://localhost - should not be empty for productive servers
define('HTTP_SERVER', 'http://www.screenprintcatalog.com');
// Secure webserver: eg, https://localhost - should not be empty for productive servers
define('HTTPS_SERVER', 'https://205.178.147.44'); // eg, https://localhost
define('HTTP_CATALOG_SERVER', 'http://www.screenprintcatalog.com');
define('HTTPS_CATALOG_SERVER', 'https://205.178.147.44');

// secure webserver for catalog module and/or admin areas?
define('ENABLE_SSL_CATALOG', 'false');
define('ENABLE_SSL_ADMIN', 'true');

// NOTE: be sure to leave the trailing '/' at the end of these lines if you make changes!
// * DIR_WS_* = Webserver directories (virtual/URL)
// these paths are relative to top of your webspace ... (ie: under the public_html or httpdocs folder)
define('DIR_WS_ADMIN', '/test/admin/');
define('DIR_WS_CATALOG', '/test/');
define('DIR_WS_HTTPS_ADMIN', '/test/admin/');
define('DIR_WS_HTTPS_CATALOG', '/test/');


I havn't experienced this kind of issue, but now we're dealing with a new server company - the only light they've provided is "With the SSL Cert, all traffic is now routed through the static IP 205.178.143.9 and then is proxies over to your hosting package." - could this be causing the above issues?

With a quote like that coming from your hosting service, it sounds like you're on a shared machine, which means it's (probably) a shared IP address. Can you confirm?

Hey,

Yeah domain is on a shared server; however, the IP is actually dedicated for the domain. A shared IP is available but of course doesn't work with the dedicated SSL...

Note: My bad listing the IP address at the bottom of the message (wrong email message/context)- the dedicated IP is accurate at 205.178.147.44 as listed in the Config samples I posted...

If you have a dedicated cert for your domain, why are you using the IP for SSL?

https://www.screenprintcatalog.com/c...ain_page=index
works just fine

and if you hit the login link from your page it takes you to a valid https page

that uses the domain name and not the IP

Hi Merlin,

Actually the issue is with the other side of the site - the link you provided was to the Canadian ZenCart (which I physically pointed all the image links to HTTPS as absolute links). Definitely not ideal but this side was the one that was live so had to act quickly...

No the issue is actually with the US ZenCart:
(http://www.screenprintcatalog.com/us/)

The front end has its share of issues (Merlin you were assisting me a few nights ago but the problem resurfaced:
http://www.zen-cart.com/forum/showth...015#post320015

So in essence I have two problems, just trying to keep the threads related to one at a time :D

The issue on this thread really is accessing the admin on the US side:
http://www.screenprintcatalog.com/us/admin

As is, the only way of accessing the admin is keeping the admin's configure.php file to read as:

// Define the webserver and path parameters
// Main webserver: eg, http://localhost - should not be empty for productive servers
define('HTTP_SERVER', 'http://www.screenprintcatalog.com');
// Secure webserver: eg, https://localhost - should not be empty for productive servers
define('HTTPS_SERVER', 'https://205.178.147.44'); // eg, https://localhost
define('HTTP_CATALOG_SERVER', 'http://www.screenprintcatalog.com');
define('HTTPS_CATALOG_SERVER', 'https://205.178.147.44');

If everyone likes I can switch out the dedicated IP to show you what I mean...

I've implemented the following code into the admin's configure.php code - which (should?) work but unfortuantely results in the 'bouncing around' effect.

Can be viewed at:
www.screenprintcatalog.com/us/admin


Revised code implemented into configure.php file (just swamped out the dedicated IP for the domain name - which as far as I know SHOULD work but doesn't)

// Define the webserver and path parameters
// Main webserver: eg, http://localhost - should not be empty for productive servers
define('HTTP_SERVER', 'http://www.screenprintcatalog.com');
// Secure webserver: eg, https://localhost - should not be empty for productive servers
define('HTTPS_SERVER', 'https://www.screenprintcatalog.com'); // eg, https://localhost
define('HTTP_CATALOG_SERVER', 'http://www.screenprintcatalog.com');
define('HTTPS_CATALOG_SERVER', 'https://www.screenprintcatalog.com');

// secure webserver for catalog module and/or admin areas?
define('ENABLE_SSL_CATALOG', 'false');
define('ENABLE_SSL_ADMIN', 'true');

// NOTE: be sure to leave the trailing '/' at the end of these lines if you make changes!
// * DIR_WS_* = Webserver directories (virtual/URL)
// these paths are relative to top of your webspace ... (ie: under the public_html or httpdocs folder)
define('DIR_WS_ADMIN', '/us/admin/');
define('DIR_WS_CATALOG', '/us/');
define('DIR_WS_HTTPS_ADMIN', '/us/admin/');
define('DIR_WS_HTTPS_CATALOG', '/us/');