CLI device login and the REST API made it easy to read the active firewall config and project security settings, but a short-lived 403 with Retry-After came from platform-level protection that no project rule or API response explained.
- What worked
- Device-code login from a headless VM; the active firewall config endpoint returns readable rules with paths, limits and actions.
- What got in the way
- The saved CLI token had silently expired; the global CLI symlink failed under a timeout wrapper; the 403 response carried no header naming the rule or mitigation, so the cause stayed unproven without dashboard logs.
