Powered by SnapDock Rendering

StaxPing — Troubleshooting

← Back to StaxPing Index

Troubleshooting

StaxPing is designed to behave consistently across platforms, but some environments impose restrictions that can affect diagnostics.
This page covers common issues, their causes, and how to resolve or work around them.

Permission Issues

Some systems restrict access to networking features such as ICMP or raw sockets.

Symptoms

  • ICMP ping fails immediately
  • Traceroute shows only fallback messages
  • Capability detection reports missing features

Resolution

  • Ensure StaxPing is installed normally (not run from a restricted directory)
  • On Linux, check whether your user has permission to send ICMP packets
  • Delete the config file and re‑run StaxPing to refresh capability detection

StaxPing will always continue running even if certain capabilities are unavailable.

Missing Capabilities

If StaxPing detects that a module is unsupported, it will skip it and display a fallback message.

Common causes

  • ICMP blocked by OS or security policy
  • Traceroute unsupported on the platform
  • DNS resolver unavailable
  • HTTP requests blocked by firewall

Resolution

  • Verify network permissions
  • Re‑run capability detection by deleting the config file
  • Test the affected module manually (e.g., ping, dig, curl)

Windows ICMP Quirks

Windows handles ICMP differently from Linux.

Symptoms

  • ICMP works only when run from certain terminals
  • Elevated privileges may be required in some environments
  • Latency values may differ from Linux tools

Notes

  • StaxPing uses Windows‑native ICMP APIs
  • Behavior is stable but may differ from Linux raw socket implementations

Windows support will continue to improve as the platform stabilizes.

Linux Raw Socket Requirements

Some Linux distributions restrict raw socket access for non‑root users.

Symptoms

  • ICMP unavailable
  • Traceroute fails immediately
  • Capability detection marks ICMP as unsupported

Resolution

  • Ensure the binary has the correct capabilities (if required by the distro)
  • Run StaxPing normally (not via sudo unless necessary)
  • Delete the config file to refresh capability detection

StaxPing avoids crashing and always reports clear fallback messages.

Network Restrictions

Corporate, school, or public networks may block certain traffic types.

Symptoms

  • DNS resolves but ping fails
  • HTTP requests time out
  • Traceroute stops after the first hop
  • Mixed results across modules

Causes

  • Firewalls blocking ICMP
  • Proxies intercepting HTTP
  • NAT or carrier‑grade routing
  • ISP‑level filtering

Resolution

  • Test from another network
  • Use a VPN if permitted
  • Compare results with built‑in system tools

StaxPing is designed to remain stable even in heavily restricted environments.

DNS Failures

DNS issues are common and often unrelated to StaxPing.

Symptoms

  • “DNS lookup failed”
  • No IPv4/IPv6 records returned
  • Extremely long lookup times

Causes

  • Misconfigured DNS servers
  • Local resolver issues
  • Network‑level filtering
  • IPv6‑only or IPv4‑only environments

Resolution

  • Test with dig or nslookup
  • Try another DNS server
  • Verify network connectivity

If DNS fails, StaxPing skips dependent modules and exits cleanly.

HTTP Timeouts

HTTP checks are lightweight but can fail under certain conditions.

Symptoms

  • “HTTP request failed: timeout reached”
  • Status code unavailable
  • Final URL not shown

Causes

  • Slow or unreachable servers
  • Redirect loops
  • Blocked outbound requests
  • SSL/TLS issues

Resolution

  • Test the URL in a browser
  • Try a different domain
  • Check firewall or proxy settings

StaxPing never downloads large content and avoids long‑running requests.

StaxPing is built to handle failures gracefully.
Even in restricted or unusual environments, the tool provides clear messaging and predictable behavior.