Upgrade attempt fails because appliance cannot download update packages - Connect IT Community

/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Upgrade attempt fails because appliance cannot download update packages - Connect IT Community | Kaseya

SUMMARY

Upgrade attempt fails because appliance cannot download update packages

ISSUE

In some instances, upgrade attempts might fail because your appliance (physical or virtual) cannot download update packages from the Unitrends repository.

RESOLUTION

Ensure port 21 (FTP), 80 (HTTP), and 443 HTTPS) are ALL accessible outgoing through your firewall for the Unitrends Appliance. With release 10.4 and higher, ALL THREE protocols are required. Options to limit to one port or protocol no longer apply.

If you would like to restrict this communication to specific trusted URLs, please see our KB What Firewall Ports should be allowed from the Unitrends appliance through my firewall?

CAUSE

The upgrade fails because a firewall or network restriction is preventing the appliance from reaching the Unitrends website on required ports or protocols.

Unitrends appliances use multiple sites and several ports to complete update operations which must be open between the appliance and the internet through your firewall.

NOTES

Additional information below is LEGACY and applies only to appliances running releases prior to 10.x.

You can resolve this issue by downloading the packages using a different transfer protocol. If the appliance is attempting to download the packages from the HTTP site, download from the FTP site instead, or vice versa.

Warning: This procedure is for advanced users online.

On appliances running 9.1 or newer:

From the command line, run "dpu repo proto ftp" or "dpu repo proto http" to change protocols.

On appliances running 9.0-15 or older:

Use an SSH client such as PuTTY to access the Unitrends system at the command line level.
Note: Ensure you have the OS password to access the Unitrends system’s command line. The OS password may differ from the password used to access the User Interface.
Enter the following command: vi /etc/yum.repos.d/Unitrends-RecoveryOS.repo
Press the Insert key.
Look for the following lines:

include=ftp://updateftp.unitrends.com/pub/Unitrends-RecoveryOS-5-x86_64.repo

include=http://updateftp.unitrends.com/pub/Unitrends-RecoveryOS-5-x86_64.repo

You see a # symbol in front of the line for the transfer protocol the appliance is currently using. To change the transfer protocol, delete the # symbol from the current line and add one to the line for the other transfer protocol.

Note: There must be a # symbol in front of one of these lines. If neither line has a # symbol, all update attempts will fail.

Press the ESC key.
Run wq to save the new setting.
Run yum clean all
Return to the Administrator Interface, and upgrade the system by selecting the Options menu (Gears icon at top right) > Check for Updates.

If neither HTTP or FTP protocols allow for a successful upgrade, then you may be on a closed network and will need to contact Unitrends Support to acquire physical update media.