Records Center - Send to Connection - Verification Failed: URL is a not a valid routing destination - Using SSL

Found some similar questions on here about this, but none of them addressed my specific problem.  

I have a single site collection and have added a Records Center.  Went into Central Admin to create a Send to Connection to enable the ability for folks to send documents to the Records Center easily.  Copied in the web service url from the RC content organizer settings.  Went to Add Connection and received "Verification Failed: URL is a not a valid routing destination".  Checked the logs and found event 8311 in reference to an SSL certificate that is no longer in use and has been deleted from IIS.  I opened the certs snap-in on the server, browse through, and I don't see any reference to this old certificate.  Thought it might be in Personal (because that's where the other SSL s are) or SharePoint.  Not there.  Oddly when I browse to the main site collection within the server that this cert was being used, it is using that certificate even though I've removed it from IIS (by the way,the browser tells me it's mismatched because it is not the same fqdn as the site collection..not sure how that happened).  With that.. my theory is that SharePoint is still picking up this certificate somewhere and I have to maybe run a script or powershell command to wipe it from the system. Or find another way to properly remove this cert and all remnants of it..

Here's some things I've done while researching this:

-I have this same configuration on my dev environment (no ssl) and it works fine.

-Added the cert to Manage Trust in Central Admin anyway to test.

-I can get to.. https://sitecollection.com/_vti_bin/OfficialFile.asmx in the browser.

-Content organizer feature is of course enabled in the Records Center.

Edit: Interesting.  I just discovered that I'm getting the same SSL error referencing the old cert in the ULS logs when I attempt to create a new data source on a Report Library "The request failed with HTTP status 401: Unauthorized."