Like others, I have not been able to process payments since early this morning.

My host (hostmysite.com) claims everything is in order on their end after running a test on ssllabs:
https://www.ssllabs.com/ssltest/analyze.html?d=pwcgraphics.com

They state that it is a problem with my code.
They also sent me an update with this message, but I'm not sure what to make of it:

Per chat conversation, I checked & inform you that our web server support TLS 1.2.
See https://www.ssllabs.com/ssltest/analyze.html?d=pwcgraphics.com for reference.
You need to update your code to use TLS 1.2. Kindly contact your site developer with below details.
====================================================================
.NET 4.6 and above you don't need to do any additional work to support TLS 1.2. It is supported by default.
.NET 4.5 TLS 1.2 is supported, but it's not the default protocol.

A code change is needed in the application's start event.
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12

.NET 4.0 TLS 1.2 is not supported, but if you have .NET 4.5 (or above) installed on the server, then you can force TLS 1.2
even if the application doesn't support it. However, it requires a different code change in the application's start event.

ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072;


As of right now, I am down in my busiest time of the year. I also have a tick in with paypal to see if they can offer any insight.
Any help would greatly be appreciated and I would also be willing to pay for help with this.
Thank you!

This is the message that I received back from PAYPAL:

I am sorry to hear of the troubles with processing payments.
I am not familiar with the site you provided, but if it provides current stats under TLSv1.0 or TLSv1.1 then your system has not been fully updated to be compliant to TLSv1.2.
I have reviewed our reports and show that you are still running TLSv1 for the api-3t.paypal.com end point using the following API operations - MM API Activity, DoExpressCheckoutPayment, GetExpressCheckoutDetails, and SetExpressCheckout. Please update your system to continue processing payments.

Can someone tell me if this is something that needs to be changed with the coding on my site or if this is an issue with my host?

Thanks!

Hi

One possibility is that as you have tls1.0 and tls1.1 available either of those may be defaulting rather than the required tls1.2. Perhaps your host or PayPal could comment on that.

Andy

Please feel free to review / rate our software

Thanks for the reply. My host stated that I need to update my code to force TLS 1.2

Here is the chat:

Nisarg Parikh: .NET 4.0 TLS 1.2 is not supported, but if you have .NET 4.5 (or above) installed on the server, then you can force TLS 1.2 even if the application doesn't support it. However, it requires a different code change in the application's start event.
ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072;
Mike Stowe: I'm not sure what that means.
Nisarg Parikh: Contact your site developer about it
Nisarg Parikh: See https://www.ssllabs.com/ssltest/analyze.html?d=pwcgraphics.com as well
Mike Stowe: I do not have a site developer.
Nisarg Parikh: You can see TLS 1.2 is enabled in above link on web server
Nisarg Parikh: Then contact someone who has idea about it or hire a developer.

Is there a way to force the shopping cart to use TLS 1.2 like my hosting support said (noted in prev post)?
Or is their claim false and I should coming up with a different attempt to solve this?
Thanks!

Something doesn't add up.
I use the same software you use and I use paypal. Both paypal and paypal payments pro.
The only thing different in our setup is the host.
Servelink does not have this problem with any of it's users, at least not that I have seen any posts on the forum.

I have talked to 2 different tech support people from my hosting company. Both said that they had other users with this problem & I need to update my code.
I am running shopping cart version 6.8.5. Is this version up to date concerning this issue?
Is there anything I need to do with my site to be compatible with TLS 1.2 or is it strictly on the hosting end?

Was I supposed to change anything in the payments section of my admin page - like the api account name or anything like that?

I'm just trying to cover all my bases.

How hard was it to switch everything over to servelink?

ServeLink will migrate your site at no charge (disclaimer - last I knew) But I am 99% sure that still holds true.

Marshall
CENLYT Productions - ms designs
Affordable Web Design
Custom Ecommerce Designs
Responsive Websites
Cenlyt.com

https://www.ecommercetemplates.com/support/topic.asp?TOPIC_ID=110267

user screek just moved and Servelink had it done in about 6 hours according to the post in that thread.

My host said that my site was running on NET 2.0. they just changed it to NET 4.0 and it still isn't working.

Is it possible that this could have anything to do with the fact that I am using a temporary, free SSL from Comodo.com?

When paypal started rolling out the updates, I was using a shared SSL and the site stopped working so I tried the free 90 day SSL from Comodo so I could test to see if that was the problem before buying a yearly one. I was under the impression that the free one was the same as the paid, but just expired in 90 days.

This is the latest message on my host's support ticket:

Hello Mike,

We already inform you that web server support TLS 1.2 & its already enabled as well. See https://www.ssllabs.com/ssltest/analyze.html?d=pwcgraphics.com again.
However if your site build on .net platform then have to update code to use TLS 1.2 as by default it will communicate on TLS 1.0 as its enabled on web server as well.

Kindly provide all details which we provide till now in this incident to you to your shopping cart or paypal to further fix this issue.

Let us know if you have any further query.

*** Here's your answer ***

I know it's 6+ months since this was posted but for others who might come across it, I'm a software developer and just encountered the same issue at "hostmysite.com". I incorporated a check into my site to see what's going on because "hostmysite.com" is very unresponsive to my questions. After they initially told me that TLS 1.2 is installed, my own tests shows that only V4.0 of the .NET framework is installed on my server. V4.5 or greater is required however to use TLS 1.2. I conducted this test using MSFT's own code (see here at this writing: [url]https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed[/url]). I incorporated this into a test page on my site and it's showing that V4.5 of .NET is *not* installed. V4.0 *is* installed which is almost 9 years old now. It doesn't support TLS 1.2 and numerous sites on the web confirm it (including MSFT's own response here: https://social.msdn.microsoft.com/Forums/en-US/eee96d65-08b3-4c28-8c19-fe246824a637/is-it-possible-to-use-tls-12-in-net-framework-40?forum=wcf). At this point I've received no reply from "hostmysite.com" after several attempts to contact them. I'll be looking for a new host very shortly.