> [!CAUTION]
> **Caution:** This documentation covers Edge for Private Cloud 4.50.00, which is no longer supported. Google does not provide security patches, bug fixes, or technical support for this version. The current supported version is 4.54.00. See the [Edge for Private Cloud documentation](https://docs.apigee.com/private-cloud/latest/overview) for the current version, or [All versions](https://docs.apigee.com/private-cloud/versions) to compare releases.
If you encounter an error during an update to Edge 4.50.00, you can roll back the
component that caused the error and then try the update again.
You can roll back Edge 4.50.00 to the following Feature Release versions:
- Version 4.19.06
- Version 4.19.01
- Version 4.18.05
> [!CAUTION]
> **CAUTION** : When an update is part of a multi-step process in which you first upgrade to one version and then to version 4.50.00, be sure to rigorously test your installation on *each version* before continuing.
>
> If you discover an issue later, you can roll back to the previous version only.
There are two scenarios where you might want to perform a rollback:
1. [Roll back to a previous Feature Release](https://docs.apigee.com/private-cloud/v4.50.00/rollback-45000#feature-release). For example from 4.50.00 to 4.18.05.
2. [Roll back to a previous *update version* in the same
release](https://docs.apigee.com/private-cloud/v4.50.00/rollback-45000#update-version). For example, from 4.19.01.02 to 4.19.01.01.
For more information, see [Apigee Edge release
process](https://docs.apigee.com/release/apigee-edge-release-process).
> [!NOTE]
> **NOTE:** The Edge [all-in-one](https://docs.apigee.com/private-cloud/v4.50.00/installation-topologies#allinoneinstallation) and [2-node](https://docs.apigee.com/private-cloud/v4.50.00/installation-topologies#standaloneinstallation2host) topologies are designed for a "getting started" or prototyping environment, not for production. Therefore, there is no rollback procedure for the all-in-one and 2-node topologies.
>
> In the situation where the update of these topologies fails, try the update procedure again.
> If the update continues to fail after multiple attempts, then the easiest option is to do a
> fresh install of 4.50.00.
## Who can perform a rollback
The user performing a rollback should be the same as the user who originally updated Edge, or a
user running as root.
By default, Edge components run as the user "apigee". In some cases, you might be running Edge
components as different users. For example, if the Router has to access privileged ports, such as
those below 1000, then you have to run the Router as root or as a user with access to those
ports. Or, you might run one component as one user, and another component as another user.
## Components with common code
The following Edge components share common code. Therefore, to roll back any one of
these components on a node, you must roll back all of these components that are on that node.
- `edge-management-server` (Management Server)
- `edge-message-processor` (Message Processor)
- `edge-router` (Router)
- `edge-postgres-server` (Postgres Server)
- `edge-qpid-server` (Qpid Server)
For example, if you have the Management Server, Router, and Message Processor installed on
the node, to roll back any one of them you must roll back all three.
## Roll back to a previous Feature Release
To roll back to a previous Feature Release, do the following on each node that hosts the
component:
1. Download the `bootstrap.sh` file for the version to which you want to roll
back:
- To roll back to 4.19.06, download `bootstrap_4.19.06.sh`:
```
curl https://software.apigee.com/bootstrap_4.19.06.sh -o /tmp/bootstrap_4.19.06.sh
```
- To roll back to 4.19.01, download `bootstrap_4.19.01.sh`:
```
curl https://software.apigee.com/bootstrap_4.19.01.sh -o /tmp/bootstrap_4.19.01.sh
```
- To roll back to 4.18.05, download `bootstrap_4.18.05.sh`:
```
curl https://software.apigee.com/bootstrap_4.18.05.sh -o /tmp/bootstrap_4.18.05.sh
```
2. Stop the component to roll back:
1. To roll back any of the [components with common code](https://docs.apigee.com/private-cloud/v4.50.00/rollback-45000#commoncode) on the node, you must stop them all, as the following example shows:
/opt/apigee/apigee-service/bin/apigee-service edge-management-server stop
/opt/apigee/apigee-service/bin/apigee-service edge-router stop
/opt/apigee/apigee-service/bin/apigee-service edge-message-processor stop
/opt/apigee/apigee-service/bin/apigee-service edge-qpid-server stop
/opt/apigee/apigee-service/bin/apigee-service edge-postgres-server stop
2. To roll back any *other* component on the node, stop just that component:
-
```
/opt/apigee/apigee-service/bin/apigee-service component stop
```
3. If you are rolling back Monetization, uninstall it from all Management Server and Message Processor nodes:
```
/opt/apigee/apigee-service/bin/apigee-service edge-mint-gateway uninstall
```
4. Uninstall the component to roll back on the node:
1. To roll back any of the [components with common code](https://docs.apigee.com/private-cloud/v4.50.00/rollback-45000#commoncode) on the node, you must uninstall them all by uninstalling the `edge-gateway` component group, as the following example shows:
```
/opt/apigee/apigee-service/bin/apigee-service edge-gateway uninstall
```
2. To roll back any other component on the node, uninstall just that component, as the following example shows:
```
/opt/apigee/apigee-service/bin/apigee-service component uninstall
```
Where component is the component name.
3. To roll back Edge Router, you must delete the contents of the `/opt/nginx/conf.d` file in addition to uninstalling the `edge-gateway` component group:
cd /opt/nginx/conf.d
rm -rf *
5. Uninstall the 4.50.00 version of `apigee-setup`:
```
/opt/apigee/apigee-service/bin/apigee-service apigee-setup uninstall
```
6. Install the 4.19.01 or 4.18.05 version of the `apigee-service` utility and its dependencies. The following example installs the 4.18.05 version of the `apigee-service`:
```
sudo bash /tmp/bootstrap_4.18.05.sh apigeeuser=uName apigeepassword=pWord
```
Where uName and pWord are the username and password you received
from Apigee. If you omit pWord, you will be prompted to enter it.
If you get an error, be sure you downloaded the `bootstrap.sh` file in step
1.
7. Install `apigee-setup`:
```
/opt/apigee/apigee-service/bin/apigee-service apigee-setup install
```
8. Install the older version of the component:
```
/opt/apigee/apigee-setup/bin/setup.sh -p component -f configFile
```
Where component is the component to install and configFile is your
configuration file for the older version.
9. If you are rolling back Qpid, flush iptables:
```
sudo iptables -F
```
10. Repeat this process for each node that hosts the component you are rolling back.
## Roll back to a previous update version
To roll back a component to a specific version of a release, do the following on each node
that hosts the component:
1. Download the specific component version:
```
/opt/apigee/apigee-service/bin/apigee-service component_version install
```
Where component_version is the component and update version to install. For
example:
```
/opt/apigee/apigee-service/bin/apigee-service edge-ui-4.18.05-0.0.3749 install
```
If you are using the Apigee online repo, you can determine the available component
versions by using the following command:
```
yum --showduplicates list comp
```
For example:
```
yum --showduplicates list edge-ui
```
2. Use `apigee-setup` to install the component:
```
/opt/apigee/apigee-setup/bin/setup.sh -p comp -f configFile
```
For example:
```
/opt/apigee/apigee-setup/bin/setup.sh -p ui -f configFile
```
Note that you specify only the component name when you install it, not the version.
3. Repeat this process for each node that hosts the component you are rolling back.