Mzack9999

@daffainfo @Techbrunch I'm able to execute nuclei correctly on windows. Could you confirm if this issue is still reproducible and if you can perform a full scan against `scanme.sh` (either...

I'm closing the issue as it seems not reproducible anymore - please let us know if you still face the problem, and we will reopen it.

Depends on https://github.com/projectdiscovery/nuclei/issues/3046 @ehsandeep if the host is skipped due to reaching the maximum number of failed attempts, we wouldn't even try to connect to it. The error message is...

@jturner I'm closing the PR due to lack of activity - Please let us know if there is anything we can do. Thanks!

The feature request is problematic as the timeout is one important error that it's necessary to track to drop unresponsive hosts. Instead, we need to ignore the error cache and...

- Blocked by https://github.com/projectdiscovery/nuclei/issues/2341 - Most likely not feasible on first request as the ip info is not available at pre-processing time

@brenocss, that is an excellent point. Still, this happens only in the case of `scan-all-ips`, as we use a custom ip to connect to.

@hktalent It seems like that `https://github.com/hktalent/scan4all/nuclei_Yaml` doesn't exist anymore. Is this issue still reproducible? Can you provide me a link to where the nuclei runner is being used?

This will be reworked as part of https://github.com/projectdiscovery/nuclei/issues/3077

Closing as this seems expected behavior - The issue will be reopened if further investigations/explanations are needed.