Sign in with the CLI, even without a browser on the server
Start the sign-in on a server and approve it on your computer or phone.
You need
The pipeit CLI (Linux, macOS, Windows), signed in, and the rights each command needs.
Replace the capitalized example values such as TARGET-DEVICE, SENDER-ID and TRANSFER-ID with your own. Paths in the examples contain no real data.
pipeit version
pipeit doctor
pipeit auth login --name server-b --headless
pipeit auth status
pipeit devices listOpen the URL that is printed on your computer or phone. Sign in to pipeit and check the device name, the fingerprint and the comparison code before you confirm. No browser has to run on the server itself. Without --headless the interactive login needs a terminal. Do not copy the login URL and code into long-lived CI logs.
The default approval covers reading devices and reading, sending and receiving transfers. Other functions can need additional, explicitly confirmed rights. Saved credentials do not mean the permission is still valid on the server. Revoked access cannot be reactivated by refreshing again and again.
Related guides
- Command line and servers
Set up Linux as a permanent receiver
Let a server accept files from one named sender into a private inbox.
- Apps and browser
Manage sign-in methods, sessions and access
Link another sign-in method, revoke access you no longer need and know what deleting an account means.
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.