This problem arises due to an incompatibility between wget and the SSL certificate of the page, although previously we could have accessed the file or download through a web browser without problems. I don't know the details of the problem, but here is a solution.
To do this, we just have to use --no-check-certificate in the wget options.
Common usage with the new parameter:
wget --no-check-certificate https://www.example.com/file.zipIf we use wget together with other parameters, we only join them to obtain the desired result.
wget -U agent-string --no-check-certificate https://www.example.com/file.zipThe only thing that changes is that it does not check the validity of the domain's SSL certificate, so it is only recommended in cases where we completely trust what we are downloading. If we have doubts, many download sites offer checksums that we can use to verify that our file is legitimate.
We could also ignore the certificate when using pages with certificates signed by ourselves, since we can be sure that the connection will be secure but not verified, and it is not the same as ignoring the certificate of a third-party website where we do not know if the certificate was compromised.
