I am getting the following error when I click Refresh Browscap Data:
Couldn't check version: Error opening socket ssl://www.browscap.org:443

The server is on php 5.6. I've tried the module cURL HTTP Request but that also gives an error:
Couldn't check version: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error

openssl is enabled - OpenSSL/0.9.8b

Is there anything else to check on the server as to why it can't get the browscap data?

Any suggestions would be appreciated.

Terry

Comments

tcnolan7 created an issue. See original summary.

luti’s picture

luti commented

It is thanks to https://www.drupal.org/node/2573711.

I guess it is in fact related to: https://www.drupal.org/node/1879970
(tried to apply those patches, but didn't help...)

I've simply reverted the patch - changed both "https:" into "http:" in "import.inc" file. Seems to work now (browscap was successfuly updated).

tcnolan7’s picture

tcnolan7 commented

Thank you. That's helpful.

aohrvetpv’s picture

aohrvetpv commented

To those still experiencing this problem: Could you please share your OS and version, PHP version, and OpenSSL version? That way I can try to set up a machine to reproduce the problem.

danchadwick’s picture

danchadwick commented

I have this issue:
Ubuntu 10.04
PHP 5.3.2
OpenSSL OpenSSL/0.9.8k

Couldn't check version: Error opening socket ssl://www.browscap.org:443

aohrvetpv’s picture

aohrvetpv commented

DanChadwick, thanks for sharing your version information. Will try to reproduce the problem sometime soon. But it should be noted that Ubuntu 10.04 is over seven years old and no longer supported as of April 2015--it's possible this problem would be resolved just by upgrading the system to a newer OS version.

astonvictor’s picture

astonvictor commented
Status: Active » Closed (outdated)

D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.