Could not obtain directory: Invalid response.
Details:
Type: urn:ietf:params:acme:error:malformed
Status: 400
Detail: upgrade your ACME client to support TLSv1.2 or better
OS:CentOS6.1
Could not obtain directory: Invalid response.
Details:
Type: urn:ietf:params:acme:error:malformed
Status: 400
Detail: upgrade your ACME client to support TLSv1.2 or better
OS:CentOS6.1
To me, this detail message is pretty clear. Could you perhaps elaborate which issue you're running in to?
Plesk to SSL installation error status.
Plesk update is not possible.
Wow, CentOS 6.1 was released in 2011. It's latest update, CentOS 6.10, was released in 2018, and went EOL in 2020.
So you're asking support for a system that hasn't been updated in 11 years?
Anyway, CentOS 6.1 was shipped with OpenSSL 1.0.0, which does not support TLSv1.2. CentOS 6.5 was rebased to OpenSSL 1.0.1, which does support TLSv1.2, so you could upgrade your OS...
It's a difficult situation to upgrade the OS.
How about the above command?
Then you'll also face difficulties communicating with the Internet of 2022, where TLS 1.0 has been largely deprecated. Let's Encrypt is certainly not on the bleeding edge here.
Btw, CentOS 6.1 => 6.10 is "just" patching (fully ABI compatible), not a major OS upgrade like CentOS 7.x would be.
Your OS would still be EOL, but in a much better shape with 9 years worth of updates applied, and compatible again with Let's Encrypt.
http2 is not related.
What are the steps for patching?
Patching up an ancient OS distro is out of the scope of this Community.
If all else fails (which it likely will), you could try using another ACME client.
Like: acme.sh
Does acme.sh
relies of openssl doesn't it? It may have the same problem.
hmm...
You might be right.
If so, then compiling OpenSSL
may be the fix.
I was able to do so on Ubuntu 14, see: Unable to validate my domain since the last couple of days due to signature algorithm not supported (it was working fine before) - #9 by rg305
So, it might be possible.
Sadly, I don't have a CentOS 6.10 to test that out.
I did not test that, so be careful what I am writing, it may screw up your system. Definetely do a backup before proceeding.
The CentOS 6 distro is already removed from the official mirrors. However, the distro data is still available on vault.centos.org
. You have to modify the repository file of /etc/yum.repos.d/CentOS-Base.repo
to point to the vault, at least for the [base]
, [updates]
and [extras]
repos that are enabled by default. Comment out the mirrorlist=
line, and uncomment the baseurl=
line. Modify the baseurl=
line to get something like:
[base]
baseurl=https://vault.centos.org/6.10/os/$basearch/
[updates]
baseurl=https://vault.centos.org/6.10/updates/$basearch/
[extras]
baseurl=https://vault.centos.org/6.10/extras/$basearch/
Do not attempt to update everything in one shoot.
First do:
yum upgrade 'rpm*' 'yum*'
then the rest:
yum upgrade
Again, it may not work, I did not test it.
It won't work. vault.centos.org
is reachable only through HTTPS, and the minimum supported TLS version is 1.2. You have to upgrade to get TLS 1.2. You have to have TLS 1.2 to upgrade. Typical chicken-egg problem.
I found another vault site that is accessible through HTTP:
http://linuxsoft.cern.ch/centos-vault/6.10
So try something like:
[base]
baseurl=http://linuxsoft.cern.ch/centos-vault/6.10/os/$basearch/
[updates]
baseurl=http://linuxsoft.cern.ch/centos-vault/6.10/updates/$basearch/
[extras]
baseurl=http://linuxsoft.cern.ch/centos-vault/6.10/extras/$basearch/
Use a proxy!
1.vi /etc/yum.repos.d/CentOS-Base.repo
2.# yum clean all
3.# yum update
4.reboot
OK?
Your best bet might be using a client like lego
which is written in Go and doesn’t depend on any OS TLS libraries.
Is it a server move?
Yes. yum clean all
is nice, but I do not think you have anything in the cache.
Please do the yum update
in two steps. reboot
is needed, for sure.
On the meantime I was thinking to do this more safely, but a lot of work. Try to do this by minor release. First from 6.1 to 6.2, then 6.2 to 6.3 and so on.
Thankyou,
1.# yum update
2.reboot
3.# yum update
4.reboot
OK??
Yes, going by minor release is safer:
1. vi /etc/yum.repos.d/CentOS-Base.repo (/6.2/)
2. yum clean all
3a. yum update 'rpm*' 'yum*'
3b. yum update
4. reboot
5. vi /etc/yum.repos.d/CentOS-Base.repo (/6.3/)
6. yum clean all
7a. yum update 'rpm*' 'yum*'
7b. yum update
8. reboot
...