SSL and dedicated IP address issues

[DrByte]

It would be easier to help you if you posted your actual URL.

Test: Instead of going to mysite.com/cart try going to mysite.com ... in both http and https ... what happens?

[Stevie-B]

Thanks DrByte,

I just didn't want the site to get crawled yet because there is literally nothing on it but the fresh install so far.

Anyway I tested it and the SSL version comes up with the untrusted page and the unsecured comes up as expected.

Your response leads me to believe it is on the hosts end and I have a support ticket in at the host.

[lat9]

You've got your HTTP server settings set to use https (only your HTTPS_SERVER settings should include the https prefix):

define('HTTP_SERVER', 'https://mysite.com'); /* There's one in both the store and admin versions */
define('HTTP_CATALOG_SERVER', 'https://mysite.com');

Change the three HTTP server settings to 'http://mysite.com'.

[DrByte]

You've got your HTTP server settings set to use https (only your HTTPS_SERVER settings should include the https prefix):

define('HTTP_SERVER', 'https://mysite.com'); /* There's one in both the store and admin versions */
define('HTTP_CATALOG_SERVER', 'https://mysite.com');

Change the three HTTP server settings to 'http://mysite.com'.

With respect, lat9 is incorrect.
In the case of an SSL-enabled site, it is perfectly appropriate (and encouraged) for the *admin* HTTP_SERVER setting to have an https address in it. Look at the comments in the code just above those settings, for explanation.
It's also explained in the FAQ article on setting up SSL.

But, that's a completely different topic than the issue at hand in this thread, and should be discussed elsewhere if there's any need to discuss it more.

[lat9]

Oops! Sorry about the misinformation regarding the admin configure.php settings.