[FEATURE REQUEST] Add a more detail description on the error message when FeroxBuster cannot connect to the target

[HenriBom]

Encountered issue

Recently I had a problem using feroxbuster through a proxy.
I had the following error :

Could not connect to https://<urls>, skipping...

Since I was using a ssh tunnel, I thought it was related at the way I had set up my proxy, but it worked through Dirsearch.
Since I was focused on the error described by the error (the fact that it couldn't reach the host), it took me a while to understand that the problem was elsewhere. After investigation I noticed that the error came from the fact that the certificate was not secured and so I just had to add the -k flag.

Suggested solution

As the error message can be misleading I was suggesting a more appropriate message when it comes to certificate issues in order to help understand it.