sudo apt-get install socat or sudo yum install socat
acme.sh didn’t include nc either; it’s just a text file. It’s just nc is a little more likely to be installed, but unfortunately the way nc works isn’t compatible with upcoming changes to way validation works so it had to be changed.
This is now resolved and when I get a moment I will post what my hosting company did to resolve this.
They installed the socat and provided the install instructions.
To get socat installed the following worked for me, this was implemented by my hosting company webfaction.com
$ mkdir -p ~/src
$ cd ~/src
$ wget http://www.dest-unreach.org/socat/download/socat-1.7.3.2.tar.gz
$ tar xfz socat-1.7.3.2.tar.gz
$ rm socat-1.7.3.2.tar.gz
$ cd socat-1.7.3.2
$ ./configure --prefix=$HOME
$ make
$ make install
$ export PATH=$HOME/bin:$PATH
This fixed the certificate issue:
./acme.sh --issue -d le.doman.com -d le.www.domain.com -w /home/accountname/landing/le_challenge