What to do if centOs stopped establishing an SSL connection?

Question

System administration

I have a server running CentOS release 5.8 (Final).
I noticed that he stopped connecting via SSL, in particular to the site https://w*recrm.com/api. The day before yesterday it worked, but today it stopped.
(Hereinafter, instead of an asterisk *, you must substitute the letter “i”, otherwise the question did not pass spam control)
That is, a simple one wget https://w*recrm.com/apigives an error:

Resolving w*recrm.com... 188.42.181.222
Connecting to w*recrm.com|188.42.181.222|:443... connected.
ERROR: cannot verify w*recrm.com's certificate, issued by `/C=AU/ST=Some-State/O=Internet Widgits Pty Ltd':
  Self-signed certificate encountered.
ERROR: certificate common name `' doesn't match requested host name `w*recrm.com'.
To connect to w*recrm.com insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.

While from other computers, for example from my home, everything works fine.
I suspect that the matter is in some outdated root certificates on my centOs. True or not? If true, how do you update them? Or what to do in such cases?

Answer 1

First of all, it is worth updating CentOS to the latest current version, for you it is 5.11, but in general it was worth leaving the 5th for a long time - it is not supported, and there most likely both wget and curl and everything else that requires the current version of SSL are old, and may do not work with certificates using modern encryption methods.

Answer 2

I tried to log in from different places - the curl is really given a self-signed certificate (unlike the browser). Apparently, this is how the web server is configured on the other side. Try to substitute user-agent with some browser one.

Answer 3

CentOS release 5.8 (Final)

My eyes don't deceive me? EL6 version 6.11 - and sometimes it does not contain the required package due to the fact that it is simply not compiled for it due to its venerable age, and here 5.8 This is like FreeBSD 9.3-STABLE on my home proxy :D
In this case, everything is generally simple - curl receives a test self-signed certificate, which, by the way, honestly and in detail declares :) There is no trust in this certificate, so there is no connection.