> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-mp-guide/v19-en-us/get-started-with-ras-management-portal/log-in-to-ras-management-portal.md).

# Log in to RAS Management Portal

To open RAS Management Portal on the machine where you've installed the RAS Web Administration Service, navigate to **Apps** > **Parallels** and click **Parallels RAS Management Portal**.

To log in to RAS Management Portal from a remote computer, enter the following URL in a web browser:

`https://<server-address>:20443`

The \<server-address> is the FQDN or IP address of the server where the RAS Web Administration Service is installed. By default, port 20443 is used for HTTPS connections. You can change the port number if needed as described in [**Configure RAS Web Administration Service**](/landing/ras-mp-guide/v19-en-us/get-started-with-ras-management-portal/configure-ras-web-administration-service.md)**.**

On the **Welcome** page, enter your RAS administrator username and password and click **Sign in**.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/ras-mp-guide/v19-en-us/get-started-with-ras-management-portal/log-in-to-ras-management-portal.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.