This guide covers how to update your Cloudmersive Reverse Proxy Server when it is deployed as a container in Azure App Service.

Prerequisites

• An existing Cloudmersive Reverse Proxy Server deployed as a container in Azure App Service
• Access to the Azure Portal with Azure Cloud Shell available
• The original container registry (e.g., CloudmersiveContainerRegistry) used during initial deployment
• Your Azure Subscription ID
• Your Cloudmersive Private Cloud Access Key (available from the Cloudmersive Portal under your node's Getting Started page)

Update Steps

Step 1 - Import the Updated Container Image

1. Open the Azure Portal and launch Cloud Shell.

2. Download and extract the latest App Service Installer package. The download command is available in the Cloudmersive Portal under your node's Getting Started page (select the Container deployment type).

3. Enter the extracted directory.

4. Run the container registry install script with your Access Key, container registry name, subscription ID, and the target version. The exact command with the latest version number is available in the Management > Updates section of your node's Getting Started page in the Cloudmersive Portal.

   The command follows this general form:

   ./InstallCloudmersiveContainerRegistry.ps1 -AccessKey <YOUR_ACCESS_KEY> -AcrName <YOUR_ACR_NAME> -SubscriptionId <YOUR_SUBSCRIPTION_ID> -v <VERSION>
   

   This process can take up to 15 minutes. Once complete, close the Azure Cloud Shell.

Step 2 - Update the Container Image Tag in Azure App Service

1. In the Azure Portal, navigate to your Reverse Proxy Azure App Service resource.
2. Click on Deployment Center.
3. Update the Image Tag to the new version tag. The exact tag value is provided in the Management > Updates section of your node's Getting Started page in the Cloudmersive Portal.
4. Click Save.
5. The Azure App Service will pull the updated container image and restart. This may take a few minutes.

Step 3 - Verify the Update

1. Navigate to the Overview page of your Azure App Service resource.
2. Click Browse to open your site.
3. Confirm that the Cloudmersive Reverse Proxy Server is running and your configured sites are accessible.
4. Optionally, check the Status tab in the Cloudmersive Portal to verify the node is reporting the updated version.

Tips

• High Availability: To maintain uptime during updates, deploy multiple nodes behind a load balancer and update them one at a time.
• Healthchecks: If you have configured an Azure App Service health check, Azure will automatically verify the new container is healthy before routing traffic to it.
• Rollback: If an update causes issues, you can revert by changing the Image Tag in Deployment Center back to the previous version tag.