Added SSL and nowhave Broken images on SSL pages

[run2web]

I have been scouring the forums for an answer for hours. I haven't found anything to answer my question so I hope that I am not asking something that already has an answer.

 

We added an SSL to our site. Now on all of the secure pages the images are not showing up. Here is my configure.php file. Maybe someone can find my problem.

 

define('HTTP_SERVER', 'http://website.com'); // eg, http://localhost - should not be empty for productive servers
 define('HTTPS_SERVER', 'https://website.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.website.com');
 define('HTTPS_COOKIE_DOMAIN', 'website.com');
 define('HTTP_COOKIE_PATH', '/cart/');
 define('HTTPS_COOKIE_PATH', '/cart/');
 define('DIR_WS_HTTP_CATALOG', '/cart/');
 define('DIR_WS_HTTPS_CATALOG', '/cart/');
 define('DIR_WS_IMAGES', 'images/');
 define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');
 define('DIR_WS_INCLUDES', 'includes/');
 define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');
 define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');
 define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');
 define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');
 define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');

 

I tried adding a "/" in front of the images call but that didn't work. I also tried removing the "/" from in front of cart but that also didn't work. Once I figure out this one I can probably fix the admin/configure as well.

 

Any ideas?

 

Thank you,

 

Michelle

[AlanR]

It's difficult to help without an actual link.

[run2web]

It's difficult to help without an actual link.

 

 

webpage

 

When you go to My Account you will see what I am talking about.

[AlanR]

Are you on a server with a second directory for secure pages?

 

Look for a folder named https_docs or secure or something similar.

[AlanR]

Your certificate is issued to www.richmond-pets.com so the configure.php file should be

 

define('HTTPS_SERVER', 'https://www.richmond-pets.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.richmond-pets.com');

define('HTTPS_COOKIE_DOMAIN', 'www.richmond-pets.com');

 

But that may not be the only problem.

[run2web]

Your certificate is issued to www.richmond-pets.com so the configure.php file should be

 

define('HTTPS_SERVER', 'https://www.richmond-pets.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.richmond-pets.com');

define('HTTPS_COOKIE_DOMAIN', 'www.richmond-pets.com');

 

But that may not be the only problem.

 

I made the changes you suggested and that didn't fix the problem yet.

 

Look for a folder named https_docs or secure or something similar.

 

I also looked at the remote host and there is nothing there named https_docs or similar.

 

I shouldn't have to change the admin/configure.php file as well until I figure out the problem, right?

[AlanR]

I shouldn't have to change the admin/configure.php file as well until I figure out the problem, right?

That's better.

 

Check for hotlinking protection. Sometimes people have it set up and they forget or don't realize it.

 

You may be blocking requests from the https url and you may need to add https://www.richmond-pets.com to the list of permitted requestors.

 

And no, you should just work on the catalog for now. Admin later after you get this figured out.

[run2web]

That's better.

 

Check for hotlinking protection. Sometimes people have it set up and they forget or don't realize it.

 

You may be blocking requests from the https url and you may need to add https://www.richmond-pets.com to the list of permitted requestors.

 

And no, you should just work on the catalog for now. Admin later after you get this figured out.

 

ok, the hotlinking sounds like it could be the issue but I can't find it? I thought it was under images or tools. Where is it? I know it was here some where and I remember setting it so that hotlinking was not allowed.

[AlanR]

Where is it? I know it was here some where and I remember setting it so that hotlinking was not allowed.

I dunno :huh:

 

It depends on your server system. I do it via .htaccess files if I do it at all.

[run2web]

I dunno :huh:

 

It depends on your server system. I do it via .htaccess files if I do it at all.

Thanks, I will look at that now.

[run2web]

Just in case anyone else runs into this problem, the fix that worked in this case was to use http:// for the secure as well as the non secure in the following line

 

define('HTTPS_SERVER', 'http://www.website.com'); // eg, https://localhost - should not be empty for productive servers

:rolleyes:

[AlanR]

Just in case anyone else runs into this problem, the fix that worked in this case was to use http:// for the secure as well as the non secure in the following line

 

define('HTTPS_SERVER', 'http://www.website.com'); // eg, https://localhost - should not be empty for productive servers

:rolleyes:

ummm...

 

 

no.

 

 

If that's what you want you just wasted the money you spent on the ssl certificate and you're not achieving any extra security at all. It's just like running an out of the box setup with no ssl.

[Funkybunny]

Hotlink protection will be on your server shell/CP not anywhere within Osc.

[turkbros]

Hotlink protection will be on your server shell/CP not anywhere within Osc.

 

 

i see that u still having problems on your page..try using

 

define('HTTPS_COOKIE_DOMAIN', 'https://www.website.com');

 

instead of using define('HTTPS_COOKIE_DOMAIN', 'website.com');

[turkbros]

define('HTTP_SERVER', 'http://www.website.com'); // eg, http://localhost - should not be empty for productive servers

define('HTTPS_SERVER', 'https://www.website.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.website.com');

define('HTTPS_COOKIE_DOMAIN', 'https://www.website.com');

 

 

try above..ingore my first msg...

 

sorry admins i couldnt edit my msg ..it gave out an error.

[AlanR]

Hotlink protection will be on your server shell/CP not anywhere within Osc.

I guess I should have made my response more clear. The hotlinking prevention is definitely a server Control Panel feature, not part of osC.

 

The chances are extremely good that it's the problem since Michelle has already mentioned that she'd activated it. So the only problem for her is to try to remember how she did it.

 

It's not an unusual problem, people here have been caught out by it before.

[run2web]

Thanks AlanR and everyone for your help. I fixed the problem by modifying my .htaccess file in my public_html folder. I did find the hotlink option in the CP as well.

 

Thanks again! :thumbsup: