> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/single-server-deployment/post-installation-checklist.md).

# Post-Installation Checklist

This section includes:

* The recommended server post-installation health check
* How to monitor the health of the system
* How to use your own server certificate
* Deployment guidelines, such as AWS EC2, Azure Virtual Machines

## Server Post-Installation Health Check

After you install the Cortex XSOAR server, it is recommended that you verify the installation by checking several systems and running several commands.

If you experience issues with any of these health checks, contact the Cortex XSOAR support team.

**Check the Docker Sub-system**

Run these commands in the playground.

* **`/docker_images`**: Shows either a list of available Docker images or an empty list.
* **`!py script="demisto.results('hello world')"`**: Verifies that `hello world` is returned, not an error.

  If no Docker images were installed, then the **`!py script="demisto.results('hello world')"`** command might take several minutes to execute, and might fail the first time it is run. If the command fails, rerun the command after five minutes.

From the CLI, run the **`sudo docker info`** command to check for warnings or errors. Not relevant for hosted service users.

**Verify Integration Tests**

Create an instance of each of the following integrations and test each of these integrations by clicking the **Test** button in the integration instance.

* urlscan.io
* IPinfo v2
* PhishTank v2
* OpenPhish v2
* Rasterize

Also, run **`!FailedInstances`** in the playground, to test all configured integrations and check outputs to see that there are no errors returned.

**Run Commands in the Playground**

We recommend that you run the following commands in the playground.

| Command Name | Related Integration                                     | Full Command                                                                                                                                                                 | Description                                                                                                                               |
| ------------ | ------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| url          | <p>urlscan.io</p><p>PhishTank v2</p><p>OpenPhish v2</p> | **`!url url=https://google.com`**                                                                                                                                            | <p>Submits a URL to scan.</p><p>Checks URL reputation.</p>                                                                                |
| ip           | IPinfo v2                                               | **`!ip ip=8.8.8.8`**                                                                                                                                                         | Checks the IP reputation (when information is available, returns a JSON with details). Uses all configured Threat Intelligence feeds.     |
| rasterize    | Rasterize                                               | <ul><li><strong><code>!rasterize url=<https://google.com></code></strong></li><li><strong><code>!rasterize-email htmlBody="\<h1>hello world\</h1>"</code></strong></li></ul> | <p>Converts the contents of a URL to an image file or a PDF file.</p><p>Converts the body of an email to an image file or a PDF file.</p> |
| ping         | N/a                                                     | **`!Ping address=8.8.8.8`**                                                                                                                                                  | Verifies accessibility of the host from the internet.                                                                                     |

**Check the Reporting Sub-system**

Run any report and verify that the PDF output resolves correctly.

**Content**

* Verify that you see automation scripts in the **Automations** section.
* Verify that you see playbooks in the **Playbooks** section.
* Verify that you see dashboard widgets in the **My Dashboards** section.
* Verify you can reach the **Marketplace** page and view content packs available for download.
* Download one or more content packs to test that traffic is allowed.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/single-server-deployment/post-installation-checklist.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.