epi052/feroxbuster · error
e
Error message
e
What it means
utils::logged_request wraps a reqwest call made through a FeroxResponse-tracking client. When the client returns Err (connection failure, timeout, TLS error, etc.), the request error is logged, the error counter for the URL is incremented in stats, and the raw error is bailed to the caller.
Solutions
- Inspect the logged 'err: {e:?}' warning for the underlying reqwest cause
- Reduce --threads/-t to lower connection pressure on the target
- Add --rate-limit or delays if the server is rejecting/breaking connections
- Verify proxy settings or remove --proxy if misconfigured
- Use --insecure for self-signed certificate environments
Example fix
// before feroxbuster -u https://target -t 200 // after feroxbuster -u https://target -t 20 --rate-limit 100
Defensive patterns
Strategy: try-catch
Try / catch
// caller of logged_request
match logged_request(&client, &method, &url, &tx_stats, &scans).await {
Err(e) => log::debug!("request to {url} failed, continuing: {e}"),
Ok(resp) => { /* handle */ }
} Prevention
- Tune -t/--rate-limit for fragile targets
- Verify proxy config before long scans
- Monitor stats error counters during the scan
When it happens
Trigger: Any reqwest client error inside logged_request - DNS resolution failure, connection refused/reset, timeouts, TLS handshake failure - during request_link, directory_listing, create_similarity_filter, connectivity, or normal request flow.
Common situations: Target drops connections under load, rate limiting closes sockets, DNS flakiness, TLS issues, or scanning through a misconfigured or overloaded proxy.
Understand the failure class
Background: 'Something went wrong' / 'Request failed (500)' / 'HTTP error! status: 404' — what failed HTTP requests actually mean and how to find the real cause — this error's family across 28 libraries.
Related errors
- {}
- JSON has no tag_name
- Could not connect to any target provided
- [ ] Unable to download wordlist from url
- err.to_string()
AI-assisted analysis of epi052/feroxbuster@1f595dab5c (2026-09-13).
Data as JSON: /api/errors/fe0b6a618582c229.
Report an issue: GitHub.
Appendix: source
Thrown at src/utils.rs:216
let tx_stats = handles.stats.tx.clone();
let response = make_request(client, url, method, data, level, &handles.config, tx_stats).await;
let scans = handles.ferox_scans()?;
match response {
Ok(resp) => {
match resp.status() {
StatusCode::TOO_MANY_REQUESTS | StatusCode::FORBIDDEN => {
scans.increment_status_code(url.as_str(), resp.status());
}
_ => {}
}
Ok(resp)
}
Err(e) => {
log::warn!("err: {e:?}");
scans.increment_error(url.as_str());
bail!(e)
}
}
}
/// Initiate request to the given `Url` using `Client`
pub async fn make_request(
client: &Client,
url: &Url,
method: &str,
mut data: Option<&[u8]>,
output_level: OutputLevel,
config: &Configuration,
tx_stats: UnboundedSender<Command>,
) -> Result<Response> {
log::trace!(
"enter: make_request(Configuration::Client, {url}, {output_level:?}, {tx_stats:?})"
);
let tmp_workaround: Option<&[u8]> = Some(&[0xd_u8, 0xa]); // \r\nView on GitHub (pinned to 1f595dab5c)