> For the complete documentation index, see [llms.txt](https://docs.9proxy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.9proxy.com/getting-started/residential-proxy-by-ips/for-linux/sign-in-to-9proxy-account.md). # Sign In to 9Proxy Account Follow these steps to sign in and manage your 9Proxy account on Linux. ## 1. Start 9Proxy Before logging in, ensure that **9Proxy** is running. If it's not already started, run: ``` systemctl start 9proxyd ``` **Optional**: If you want 9Proxy to start automatically on boot, run: ``` systemctl enable 9proxyd ``` ## 2. Sign In to Your Account ### 2.1. Option 1: Standard Sign In via Interface Run the following command to open the login interface, where you can enter your **Username** and **Password**: ``` 9proxy auth -s ``` Once prompted, enter your credentials and select "**Login**" to sign in.

### 2.2. Option 2: Sign In Directly via Command Line You can also sign in using your credentials directly in the terminal: ``` 9proxy auth -u [username] -p [password] ``` * \[username] → with your 9Proxy account username * \[password] → with your 9Proxy account password ## 3. Sign Out (If Needed) To sign out and sign in with another account, use the following command: ``` 9proxy auth -l ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.9proxy.com/getting-started/residential-proxy-by-ips/for-linux/sign-in-to-9proxy-account.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.