Check the direct route and set the fallback
Probe a direct route, choose a route per transfer and control the account-wide fallback.
You need
The pipeit CLI (Linux, macOS, Windows), signed in, and the rights each command needs.
pipeit routes check --target TARGET-DEVICE
pipeit routes getThe probe checks authorized endpoints within limits. A successful probe is not a receipt and not a speed estimate for the whole file.
To explicitly request forwarding when sending, set --route relay. For a direct attempt use --route direct. In the CLI this flag alone does not forbid the server-route fallback. The account setting that applies to new transfers is decisive too. With the explicitly granted right routes:manage and the version you read before, you can change it:
pipeit routes set --fallback deny --expected-version VERSIONThis setting applies to new transfers of all your devices. Use allow to permit it again. Existing jobs keep their bound policy. On a version conflict, read again and decide deliberately; do not overwrite blindly. Obtain additional rights only through the normal authorization flow.
Related guides
- Apps and browser
Check the connection and look back at it later
See which route is checked before sending and which one was actually used afterwards.
Direct, server route and routed networks: which way works?
What “direct” really means, when pipeit routes through its servers and what you can check.
Solve transfer problems
Check the specific problem instead of starting over: a quick decision list and the common symptoms with their next step.
Still stuck?
Check the troubleshooting guide first. If that does not help, tell us what happened.