<?xml version="1.0"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>MachForm Community Forums Topic: Authroize.net issues with CentOS 6.6</title>
<link>https://www.machform.com/forums/</link>
<description>MachForm Community Forums Topic: Authroize.net issues with CentOS 6.6</description>
<language>en</language>
<pubDate>Sun, 03 May 2026 23:30:18 +0000</pubDate>

<item>
<title>rocketmedia on "Authroize.net issues with CentOS 6.6"</title>
<link>https://www.machform.com/forums/topic/authroizenet-issues-with-centos-66#post-23368</link>
<pubDate>Tue, 02 Jun 2015 05:08:47 +0000</pubDate>
<dc:creator>rocketmedia</dc:creator>
<guid isPermaLink="false">23368@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;Las week I was working through some issues with a new centOS 6.6 server and the newest version of machform.&#60;br /&#62;
No matter what we did we received the error&#60;br /&#62;
&#34;PHP Fatal error:  Uncaught exception 'AuthnetXMLException' with message 'Connection error: Peer certificate cannot be authenticated with known CA certificates (60)' in /var/www/vhosts/testsite.com/httpdocs/form/lib/authnetxml/AuthnetXML.class.php:211&#34; &#60;/p&#62;
&#60;p&#62;To resolve this issue I updated the cert.pem file in the AuthnetXML library with a more current version from mozilla found here. &#60;a href=&#34;http://curl.haxx.se/ca/cacert.pem&#34; rel=&#34;nofollow&#34;&#62;http://curl.haxx.se/ca/cacert.pem&#60;/a&#62; &#60;/p&#62;
&#60;p&#62;I have already setup a pull request on the github repo for the changes to be brought into the library. I suggest you take a look into the issues on the github page &#60;a href=&#34;https://github.com/stymiee/Authorize.Net-XML&#34; rel=&#34;nofollow&#34;&#62;https://github.com/stymiee/Authorize.Net-XML&#60;/a&#62; &#60;/p&#62;
&#60;p&#62;I just wanted to document this issue on the forum in case others run into the same problem.
&#60;/p&#62;</description>
</item>

</channel>
</rss>
