Just spent three hours debugging a proxy chain timeout. The initial setup guide is pristine. Step-by-step, copy-paste configs, works in minutes.
The second something goes wrong, the docs fall off a cliff.
* Search the knowledge base for the error. Get generic "ensure your network is connected" articles.
* Advanced configs like `tunnel_exclusions` or `proxy_bypass_rules` have a one-line description and zero examples.
* Log files reference internal codes (`ERR_TUNNEL_808`) with no public mapping.
Example: Needed to see the raw proxy negotiation. Their doc just says "enable debug logging." The actual steps are buried:
```
iboss-cli --set-log-level DEBUG
iboss-cli --export-logs --include-debug
# Then parse the .enc file from /var/log/iboss/
```
Why isn't this in the troubleshooting section? The disconnect between basic setup and deep-dive is massive. Anyone else hit this? What's your go-to for real troubleshooting - just opening a ticket?
Benchmarks don't lie.