GoBuster can't handle errors during startup "PreRun"

[RoganDawes]

I'm targeting a site that doesn't have an index page for /, and if the page doesn't exist, it actually just closes the connection. (If it helps, the target site seems to be behind an F5 BigIP.) As a result, gobuster never even starts, reporting:

Error: error on running gobuster: unable to connect to https://example.com/: Get https://example.com/: read tcp x.x.x.x:60936->y.y.y.y:443: read: connection reset by peer

Would it be reasonable to have an option "Treat connectivity errors as 404", or similar?

[minispooner2]

+1. "reset by peer" stops all subsequent testing, despite there being legit pages. i'd bet the web server i'm testing is configured to send RST on certain pages, but give Response for legit pages.