You're viewing **Apigee Edge** documentation.  
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info

On Tuesday, May 30, 2017, we released a new version of Apigee Edge for Private Cloud.

> [!NOTE]
> **Note:** **Questions or issues?** Contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support.md.txt).
>
> **Release notifications** : See [Get Apigee Edge release notifications](https://docs.apigee.com/release/get-release-notifications.md.txt).
>
> [Release notes home page](https://docs.apigee.com/release/notes/apigee-release-notes.md.txt)

## Update procedure

To update your installation, perform the following procedure on the Edge nodes:

1. On all Edge nodes:

   1. Clean Yum repos:  
      \> sudo yum clean all
   2. Update the Edge 4.17.01 bootstrap_4.17.01.sh file in /tmp/bootstrap_4.17.01.sh:  
      \> curl https://software.apigee.com/bootstrap_4.17.01.sh -o /tmp/bootstrap_4.17.01.sh
   3. Install the Edge 4.17.01 apigee-service utility and dependencies:   
      \> sudo bash /tmp/bootstrap_4.17.01.sh apigeeuser=***uName*** apigeepassword=***pWord***   

      where ***uName:pWord*** are the username and password you received from Apigee. If you omit ***pWord***, you will be prompted to enter it.
   4. Update the apigee-setup utility:  
      \> /opt/apigee/apigee-service/bin/apigee-service apigee-setup update
   5. Update edge-gateway:  
      \>/opt/apigee/apigee-setup/bin/update.sh -c edge -f ***configFile***   
      where ***configFile*** specifies the config file you used to install Edge.
2. On all Edge UI nodes, update edge-ui:  

   \>/opt/apigee/apigee-setup/bin/update.sh -c ui -f ***configFile***

## Bugs fixed

The following bugs are fixed in this release.

> [!NOTE]
> **Note:** The build number in the table specifies the earliest version of the component that contains the fix. Use that build number to determine if you already have the fix installed, or if you need to perform an update. The apigee-service utility displays the build number of the currently installed component:
>
> ```
> /opt/apigee/apigee-service/bin/apigee-service comp version
> ```
>
> where ***comp*** is the name of the component without the build number
> extension. For example:
>
> ```
> /opt/apigee/apigee-service/bin/apigee-service apigee-setup version
> ```
>
> or get the build number of all components:
>
> ```
> /opt/apigee/apigee-service/bin/apigee-all version
> ```

| Issue ID | Description | Build number |
|---|---|---|
| APIRT-3832 | **Message Processor not populating the server name field in a TLS request when using proxy server for connection to backend service** An Nginx startup error occurred if IPv6 was enabled on Nginx on a system that did not have IPv6 enabled. | edge-gateway-4.17.01-0.0.1166 |
| APIRT-3590 | **Message Processor uses wrong HTTP auth header when tunneling** When a Message Processor uses tunneling with the HTTP CONNECT method, it now sends the correct header: "Proxy-Authorization: Basic ***value***". | edge-gateway-4.17.01-0.0.1166 |
| EDGEUI-1032 | **Link in email to set a password directs you to the login page** When a new user clicks the link in an email to set a password, the link now directs them to the set password page and not the login page. | edge-ui-4.17.01-0.0.3848 |