Search the Community
Showing results for tags 'tls'.
Found 3 results
-
WHMCS and Symantec would like to invite you to this exclusive 60-minute live webinar: PROFIT BY SELLING SSL & TLS 1st November 9am PDT | 11am CDT | 4pm GMT Join WHMCS and Symantec's Trust Strategist Jeff Barto as he covers everything you need to profit from selling SSL / TLS, from the very basics of technology, onward to demonstrating a compelling customer need, and upward to improving the bottom line by offering SSL / TLS Certificates within your portfolio. During this session, you will learn: - What SSL / TLS are and how they work - Different options for SSL Certificates plus use cases for each - The timely need for security with your customers’ websites - How to maximize profit and be successful with SSL / TLS ABOUT JEFF BARTO Jeff is a trust strategist and website security advocate. He’s passionate about establishing and projecting fundamental trust on the internet. Jeff leverages the synergy of his decades of experience in technology marketing and IT/security at BBDO, infoUSA, Applied Materials, Symantec, HP, and Norton. Having spoken in keynotes and panels at ISSA and InfraGard events, World Hosting Days, the Online Trust Alliance’s trust summit, and a host of e-Commerce focused events such as Internet Retailer, Online Retailer, and shop.org, Jeff delivers an impassioned and motivating perspective for maximizing the business value – and rewards – of trust, confidence and security..png.ca0830b11355f5cb4cc983a4bc911e4d.png)
-
Hey there, After applying the necessary changes to the Plesk configuration for PCI compliance that essentially disable SSLv3 and TLSv1 (leaving only TLSv1.1 and TLSv1.2 as an option), WHMCS is no longer able to communicate with Plesk. It provides this error when attempting to do so: Is there something being passed to curl that is requiring SSLv3 or TLSv1.0 only? We're using openssl-1.0.1e-42.el6.x86_64 on CentOS 6.7, which most definitely supports the latest TLS protocol versions. Plesk: 12.0.18 Update #69 WHMCS: 6.1.1
-
Happy New Year To Everyone! ***Updated*** ...never mind we found the problem and it had nothing to do with the v5.3.11 Patch. We found that some how the CSF SMTP Port Block had been updated to include the SMTP port we were using. We corrected that and now we are back in business. Sorry, for the false alarm...
.png.ca0830b11355f5cb4cc983a4bc911e4d.png)
