Re: PHP 4.0.6 + VeriSign PayFlow Pro libpfpro 304

I'm in a similar situation. I'm running redhat 7.1/php4.1.1/mysql/openssl0.9.5a/apache1.3.20.... upon compiling in the verisign support, the module breaks apache on startup. apache on ./apachectl startssl will not give me the password prompt but just a hung process. so i end up killing off apachectl with a kill -9. any help would be appreciated. -danny "Bob Hayes" <bob@artbeats.com> wrote in message news:B80D93F3.BC96%bob@artbeats.com... > Hi all, > > I know the Payflow Pro thing has been done to death, but I've searched high > and low for the answer to this last problem and I'm stumped. I know it's a > simple thing somewhere, but I'm erroring out with the ssl/cert issue. To > make matters worse, I'm definitely not a Linux expert. > > I'm using RH Linux 7.1 + Apache 1.3.19 (stock RPM, not recompiled) + PHP > 4.0.6 (from Troels Arvin's site at rpms.arvin.dk) with the pfpro option > compiled in, using version L304 of the pfpro SDK. > > My php.ini file has the "extension=pfpro.so" and "extension=libpfpro.so" > lines added. I have the PFPRO_CERT_PATH environmental variable set and > exported to all apps and it shows up with an env command. The test cert that > came with the SDK is in the directory listed for PFPRO_CERT_PATH, along with > a self-signed certificate. > > The perl cgi test script that came with the PF Pro SDK works, but our > transaction.php page which just calls "pfpro_process($parameters, $host)" > does not. I keep getting this error when processing a test transaction: > > > The Response: > Array ( [RESULT] => -8 [RESPMSG] => SSL failed to connect to host ) > The Error: > SSL failed to connect to host > > > I occasionally get this slightly different error: > > The Response: > Array ( [RESULT] => -31 [RESPMSG] => The certificate chain did not validate, > no local certificate found ) > The Error: > The certificate chain did not validate, no local certificate found > > > Any suggestions? I know this is connected to ssl and our cert files in some > way--is it because we don't have a real VeriSign issued certificate on this > machine yet, just the self-signed cert? > > > Regards, > > Bob > > -- > Bob Hayes > Systems Administrator > Artbeats Digital Film Library > www.artbeats.com >