search for: verify_peer_nam

..., 'verify_peer' => true, 'verify_depth' => 3, // 'cafile' => '/dont/need/to/set/this/option', ), ); and this one: $config['imap_conn_options'] = array( 'ssl' => array( 'verify_peer' => false, 'verify_peer_name' => false, ), ); and this one too: $config['imap_conn_options'] = array( 'ssl' => array( 'verify_peer' => true, 'verify_depth' => 3, 'cafile' => '/path/to/my/self/signed/certificate.pem', ), );...

...nect timeout using streams. Example using https, but should be easily adaptable to non-s http.: $pbxsh_bin = @file_get_contents("https://blah.blah.blah", FALSE, @stream_context_create(array('https' => array('timeout' => 5, "verify_peer"=>false, "verify_peer_name"=>false)))); On 09/14/2018 01:40 PM, Carlos Chavez wrote: > On 9/13/2018 8:04 PM, Patrick Wakano wrote: > >> Hello list, >> Hope you all doing  well! >> >> Recently, I had an issue with a FastAGI PHP script, which under some >> specific situation woul...

...ple using https, but should be easily adaptable to non-s http.: >> >> $pbxsh_bin = @file_get_contents("https://blah.blah.blah", FALSE, >> @stream_context_create(array('https' => array('timeout' => 5, >> "verify_peer"=>false, "verify_peer_name"=>false)))); >> >> On 09/14/2018 01:40 PM, Carlos Chavez wrote: >> > On 9/13/2018 8:04 PM, Patrick Wakano wrote: >> > >> >> Hello list, >> >> Hope you all doing well! >> >> >> >> Recently, I had an issue with a...

I think that you are right when you say that the problem may be the certificate recognition. As for Roundcube, I've inserted the uncommented php code that you provided in /usr/share/roundcube/main.inc.php.dist, which is the Raspbian file for /config/defaults.inc.php. Unfortunately Roundcube doesn't login and replies with the message "connection to storage server failed". And

Hello list, Hope you all doing well! Recently, I had an issue with a FastAGI PHP script, which under some specific situation would run into an infinity loop, consuming all CPU resources. This also was preventing Asterisk to terminated the call properly because it was waiting for the AGI to return... The application uses AGIspeedy to process the AGI calls, not sure if this can be affecting this