"The certificate chain did not validate ..."

[jcengagency]

My client has a ShopSite 10 installation (on a FreeBSD VPS). At some point in the last few days, something has happened that prevents customers from updating their credit card information. When they try to do so, they get this error:

"The certificate chain did not validate, no local certificate found, Cert Path = /www/verisign/payflowpro/freebsd/certs, Working Directory = /redacted/working/directory/path"

Oddly enough, processing of orders, etc. all happens fine ... the problem is just with updating an existing credit card.

The cert path in the error message exists on the server, it's owned by the www user, and the www user has the correct permissions to access the single file in it, which has what appears to be a random name, and its contents appear to be a certificate of some sort.

Any ideas? I've been working with his hosting company's support (they installed ShopSite) for over a day now without any success, so I'm just trying other avenues to fix this issue ...

---

EDIT - He's using PayFlow Pro as his payment processor, if that's not clear from the error message ... if there's other information that might be helpful let me know.

[loren_d_c]

So where exactly in ShopSite is the shopper 'updating an existing credit card'? I am not aware of this functionality in ShopSite unless it is in ShopSite's Customer Registration feature where a logged-in shopper can see payment types they have used previously (if the merchant has enabled the saving of payment information). However, as far as I know, this function does not interact with Payflow Pro (or any other payment gateway) in any way, and ShopSite would never use a cert at any path such as "/www/verisign/payflowpro/freebsd/certs", so it sounds to me like it is some other application that they are using when they get this particular error, not ShopSite.

-Loren

[jcengagency]

Loren,

Whoops ... I'm sorry, I meant to update this topic. Yes, you are right ... I finally determined that there was some additional non-ShopSite code that had been integrated into the client's e-commerce setup, and that's where the error was happening. So .. it wasn't ShopSite at all. I apologize for not updating this earlier ...

Best,
Jeremy