> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/operations/deployment/deployment-guide/how-to-update-an-environment-from-one-domain-to-another.md).
# How to Update an Environment from One Domain to Another
This document describes how to Update an Environment from One Domain to Another
### Steps to Follow
1. Create an SSL certificate for the new domain and update it in the Nginx server. Also, ensure DNS mapping is completed for the new domain.
2. Create a new Gateway for the new domain in the existing environment, and delete the old one.
3. Go to **Apps**, then **Edit** and **Upgrade** the application where you need to update the new domain.
4. Update the new domain name wherever required by removing all references to the old domain name.
5. Update the client names according to the new domain.
6. Ensure the correct **Client ID** and **Client Secret** are configured while upgrading.
7. Click **Next** and proceed to upgrade the application.
8. After the upgrade, verify all **Virtual Services** to ensure the new domain name is updated correctly.
9. Manually update the domain configuration in **Odoo UI** wherever old URLs were configured.
The below screenshot is for reference, showing how the domain name was changed from **nissa** env to **zanzibar** env**.**
####
---
# 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.openg2p.org/operations/deployment/deployment-guide/how-to-update-an-environment-from-one-domain-to-another.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.
