Stuck with ‘Cannot find the DirectAdmin binary: Extraction failed’ error while installing DirectAdmin? We can help you.

Here at Bobcares, we often handle requests from our customers to fix similar DirectAdmin errors.

Today we will see how our support engineers fix Cannot find the DirectAdmin binary. Extraction failed error for our customers as a part of our Server Management Services.

What is ‘Cannot find the DirectAdmin binary: Extraction failed’ error?

Typically, error looks as shown below:

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Cannot find the DirectAdmin binary. Extraction failed
it could be for a various number of reasons.

It could be for a various number of reasons.

How to resolve “Cannot find the DirectAdmin binary. Extraction failed’?

Let us see the methods used by our Support Techs to resolve error.

1.wget --bind-address=1.2.3.4 http://www.directadmin.com/index.html
wget http://www.directadmin.com/index.html

Where 1.2.3.4 is the IP address in your license file. If you get the same error with the –bind-address option, then that IP is not present or valid in your network device.

The 2nd wget command should work from within a LAN. If both fail, then it’s some other issue (firewall, network, routing, etc.).

You can run command:

ip a

To see what IPs are present in your network device. Make sure the IP in your license is present somewhere in the output.

The IP in your license file must be present and working in the network device.

2. During the installation of DA, if the following error occurs:

Connecting to www.directadmin.com|216.144.255.179|:443… failed: Connection timed out.

It means that the connection to our server cannot be established.

If you’ve successfully downloaded the setup.sh script from www.directadmin.com, then it would imply that our firewall is not blocking you (if we block an IP, we block the IP on all ports).

Then, to test this:

wget -O /dev/null http://www.directadmin.com/index.html
wget -O /dev/null https://www.directadmin.com/index.html

If both ports are blocked, try this test using other websites, e.g.,

wget -O /dev/null http://www.apple.com/index.html
wget -O /dev/null https://www.apple.com/index.html

If you cannot connect outbound to any server on port 443, then it’s likely a firewall on your end.

We recommend installing CSF which will open the required outgoing ports.

It’s also possible it’s block at your datacenter, in which case you’d need to contact them to get it unblocked.

However, if it’s blocked at your datacenter, then there would be a reason for that and you’d need to convince them that whatever reason it was blocked in the first place no longer applies.

Then, you might just be part of an entire IP range block.

Sometimes a datacenter will block outbound port 443. We have a work-around to allow the getLicense script to download the license using port 80.

To enable this mode, type:

echo 1 > /root/.insecure_download

And run the getLicense.sh script again.

Finally, the last possibility is that you’re running on a LAN instead of the required external IP. Use the LAN installation guide.

[Need further assistance with DirectAdmin error? We can help you]

Conclusion

In short, today we saw the fix provided for the ‘Cannot find the DirectAdmin binary: Extraction failed’ error.