/* * 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

Management & Automation Backup Portal

Unitrends Backup Portal Agent installation fails

SUMMARY

Troubleshooting steps to resolve issues where the Unitrends Backup Portal Agent installation fails and produces error.

ISSUE

When installing the Unitrends Backup Portal agent the following errors may be returned:

root: Installer - Executing setup script
root: Installer - New installation, registering
Installation failed
root: Agent - Starting services
root: Agent - Starting Agent
root: Agent - Msp process did not start

curl: (35) SSL connect error
package.tar
setup.sh

package.tar
setup.sh
root: Installer - Executing setup script
root: Installer - New installation, registering
Installation failed
root: Installer - Getting asset tag
root: Installer - Getting reggen file
root: Error - Token is malformed, please generate a new installation

RESOLUTION

Connect to the Unitrends Appliance using an SSH terminal program (e.g. PuTTY) and authenticate using the user 'root'.
Uninstall Unitrends Backup Portal agent by issuing this command: sudo /usr/utmsp/uninstall.sh
Stop the database and restart the Unitrends appliance by following the instructions in the article Shutdown or restart a Recovery Series appliance.
Verify that the Firewall that the Unitrends is behind allows traffic over 443. Traffic from the Unitrends Appliance should not be filtered, as it could be stopped by Layer 3 or Layer 7 filters.
Using the Unitrends Backup Portal, generate new curl script.
Run the script on the Unitrends appliance again and wait 5 to 10 minutes. If this has not resulted in the appliance showing up on the list, execute this command: /usr/utmsp/start.sh

At this point, you should see the appliance displayed in about 10 minutes from executing the command. If you are still not able to see it, contact us so we can engage further to find the right resolution.

CAUSE

The MSP agent uses port 443 for communication. Port 443/HTTPS is the HTTP protocol over TLS/SSL and is used for secure web browser communication. Due to this any type of SSL traffic filter will restrict communication over port 443 and cause issues for systems that utilize port 443.