> For the complete documentation index, see [llms.txt](https://docs.akamas.io/akamas-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akamas.io/akamas-docs/3.6/installing/verify-the-akamas-server.md). # Verify the installation Run the following command to verify the correct startup and initialization of Akamas: ```bash akamas status ``` When all services have been started, this command will return an "OK" message. Please note that it might take a few minutes for Akamas to start all services. To check the UI is also properly working please access the following URL: ``` http:// ``` You will see the Akamas login form:

Please notice that it is impossible to log into Akamas before a license has been installed. Read here [how to Install an Akamas license](/akamas-docs/3.6/installing/install-the-akamas-license.md). --- # 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.akamas.io/akamas-docs/3.6/installing/verify-the-akamas-server.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.