SSL Certificate only work in Back office, not in Front office

[seanr22a]

I need help to figure out why SSL Certificate isn't working in Front office.

 

Cerificate is a DigiCert Extended Validation (EV) SSL Certificate. It works when in Back office as you can see here - it is green and locked.

 

 

 

 

 

But in Front office it looks like this:

 

 

I think I've turned everything on in Back office to use SSL. It looks like this now:

 

 

Anyone seen this problem before ?

 

Is there anything I can do myself (I'm not a developer) ?

 

 

Customers are very security aware and of course they spot this flaw

 

 

I was using the Media Server function before switching to SSL mode to speed up the website using cookieless static content but it don't work when using SSL. The whole site gets text based ... not a single picture or graphics anywhere.

 

Is there any workaround for that ?

 

 

 

Edited January 18, 2022 by seanr22a (see edit history)

[seanr22a]

 

 

Thanks ! I would never have found that myself. I changed the code, cleared the cache and to be sure turned Force Compilation on. But still the same

[seanr22a]

Problem solved

 

I had more links in my site that had references to http instead of https.

 

I found an excellent tip at stackoverflow.com (user Professor Falken) about how to locate links breaking your certificate.

 

From stackoverflow.com:

the firebug Net tab will show this and any other problems. Follow these steps:

 

Install Firebug add-on into firefox if you don't already have it, and restart FF when prompted.

 

Open Firebug (F12 or the little insect menu to the right of your search box).

 

In firebug, choose the "Net" tab. Hit "Enable" (text link) to turn it on

 

Refresh your problem page without using the cache by hitting Ctrl-Shift-R (or Command-shift-R in OSX). You will see the "Net" tab in firefox fill up with a list of each HTTP request made.

 

Once the page is done loading, hover your mouse over the left colum of each HTTP request shown in the net tab. A tooltip will appear showing you the actual link used. it will be easy to spot any that are http instead of https.

 

If any of your links resulted in an HTTP redirect, you will see "301 Moved Permanently" in the HTTP status column, and another HTTP request will be just below for the new location. If the problem was due to an external redirect, that's where the evidence will be - the new location's request will be HTTP.

 

If your problem is due to redirections from an external site, you will see "301 Moved permanently" status codes for the requests that point them to their new location.

 

Expand any of those 301 relocations with the plus sign at the left, and review the response headers to see what is going on. the Location: header will tell you the new location the external server is requesting browsers use.

Edited March 24, 2016 by seanr22a (see edit history)