After installing the module and setting up a flickr block I am getting the following error:

Could not connect to Flickr, Error: Unable to find the socket transport "ssl" - did you forget to enable it when you configured PHP?

I realize this is a server issue, not something wrong with the module, but I'm having trouble figuring this out for an CentOS release 5.11/Apache server since I keep finding Windows based solutions. Can anyone provide suggestions?

CommentFileSizeAuthor
#15 better_fallback_to_cURL-2395635-15.patch3.09 KBlolandese

Comments

ladybug_3777’s picture

ladybug_3777 commented
Issue summary: View changes
ladybug_3777’s picture

ladybug_3777 commented
Issue summary: View changes
lolandese’s picture

lolandese commented
Version: 7.x-1.6 » 7.x-1.x-dev

Try the latest dev version. This should be solved recently in #2295241: Unable to contact flickr and retrieve the pictures (try to use cURL when drupal_http_request returns a 403, forbidden).

Select the checkbox 'Use 'cURL' instead of 'stream_socket_client (drupal_http_request)' (Otherwise cURL will be only used as fallback when the usual method returns a 403 (forbidden)).

Feedback on it is very welcome.

ladybug_3777’s picture

ladybug_3777 commented

Great! I will give your suggestion a try and report back. Thanks!

ladybug_3777’s picture

ladybug_3777 commented

Installed dev, selected the checkbox and everything is working as expected again! Thank you for your help lolandese!

ladybug_3777’s picture

ladybug_3777 commented
Status: Active » Closed (duplicate)
lolandese’s picture

lolandese commented

Hi Jennifer,

We would like to know a couple of additional things:

  • What host you're on? The mentioned issue happened on a free host. It is interesting to know if also other hosts don't allow outgoing connections over 'stream_socket_client'. Realize that drupal_http_request can probably not be used on your host and is the only connection method currently supported in Drupal core. You can use the chr module if you also run into problems with other modules that use outgoing connections.
  • If you unselect the checkbox, does the automatic fallback kicks in (with error 403 (forbidden) or 408 (Request Timeout))? Does it give another error code in a message anywhere (check also your error log and watchdog messages)? We could potentially use this error code as a trigger to extend our fallback behaviour.

Thanks.

Some more background info: http://pingv.com/blog/better-getter
The library itself is unrelated.

lolandese’s picture

lolandese commented
Status: Closed (duplicate) » Postponed (maintainer needs more info)
ladybug_3777’s picture

ladybug_3777 commented

I will provide you with more information likely on Monday. I work on the Windows machines here (which did not have this issue) and my coworker is in charge of the CentOS box. He's out today but I will have him check these items for you when he returns. I do know that after installing the dev version he forgot to check the checkbox and the original error listed in my first post was still being displayed. After checking the box it went away. Our host is not a free one, we actually work for a big name client that deals with large security threats on a daily basis so they have things locked down quite a bit which may explain why we had an issue. I'll check back in with you next week, and thanks again for being so prompt and so helpful!

dhewitt’s picture

dhewitt commented

The unix flavor is CentOS release 5.11 in this case. Not sure if that helps.

lolandese’s picture

lolandese commented

Not sure if the reported error message corresponds to an HTTP status code that we could use to trigger cURL as a connection method as is currently done with a 403 or 408.

Alternatively we could maybe fallback to cURL in any case that the 'open socket' method fails, independent from any returned error code? Meanwhile patches as such are welcome.

I' m glad that the checkbox to force use cURL solved your problem for now.

lolandese’s picture

lolandese commented
Title: Apache Issue - Unable to find the socket transport "ssl" » Apache Issue - Fallback to cURL in ANY case that the 'open socket' method fails, independent from any returned error code
Category: Support request » Feature request
lolandese’s picture

lolandese commented
Parent issue: » #2421343: What 'active' issues go in the next stable release?
lolandese’s picture

lolandese commented
Status: Postponed (maintainer needs more info) » Active
lolandese’s picture

lolandese commented
Status: Active » Needs review
StatusFileSize
new better_fallback_to_cURL-2395635-15.patch3.09 KB

Attached patch contains:

  • Extended fallback behaviour independent from the returned error code.
  • Built-in checks if the functions 'stream_socket_client' or 'curl_version' are available before calling the functions that use these connection methods.
  • Messaging and logging of request when not foreseen cURL fallback took place.
  • Messaging and logging of when no connection method was available.

  • lolandese committed 99e30da on 7.x-1.x 
    Issue #2395635 by lolandese: Apache Issue - Fallback to cURL in ANY case...
lolandese’s picture

lolandese commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.