> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/technical/guides/installation/deploy-set-up-a-server-hosted-environment/deploy/running-validation-checks.md).

# Running validation checks

### Run validation checks

"Deploy OpenCRVS" workflow runs validation checks before and after deployment to confirm that the environment is ready and that the deployed services are reachable. Use following stepts to run validation checks manually

1. Navigate to GitHub Actions within `infrastructure` repository
2. Select "10. Validate pre/post deploy" action
3. Select "Target environment" from dropdown menu, all environments created at [Create a GitHub Environment](/technical/guides/installation/deploy-set-up-a-server-hosted-environment/create-a-github-environment.md) step should be listed here.
4. Select "Target stage":
   1. predeploy
   2. postdeploy
5. Enter the **Tag of the core image** currently deployed (or about to be deployed), e.g. `v2.1.0`
6. Click "Run workflow" button

### Deployment validation checks

| Stage                      | When to run                   | What it checks                                                                                                                                                                                |
| -------------------------- | ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Pre-deployment validation  | Before running the deployment | Required datastores are reachable from the deployment environment, and SMTP configuration is present when two-factor authentication is enabled.                                               |
| Post-deployment validation | After deployment completes    | Public service domains resolve in DNS, have valid HTTPS certificates, are covered by the certificate SANs, and respond over HTTPS. SMTP connectivity is also checked when SMTP is configured. |

Following checks are running at pre-deployment:

* Postgres connectivity
* Redis connectivity
* MinIO connectivity
* Elasticsearch connectivity, if configured
* SMTP configuration:
  * Server availability
  * Configuration

Following checks are running at post-deployment:

1. For each public domain, validation runs the following checks in order:
   1. DNS resolution
   2. SSL certificate fetch
   3. SSL certificate SAN coverage
   4. HTTPS availability
   5. Public IP check: a warning (not a failure) is reported when an OpenCRVS domain resolves to a public IP address
2. Events service readiness check
3. Email integration check


---

# 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://documentation.opencrvs.org/technical/guides/installation/deploy-set-up-a-server-hosted-environment/deploy/running-validation-checks.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 `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.