This article applies to version 6.
Web restores initiated from an on-premises authority server for an archive stored in the Code42 cloud require SSL for all connections. Web restores fail if SSL is not configured. Specifically, instead of a window showing a list of the backed up files, the operating system progress indicator stops responding and may appear stuck.
Code42 environments with an on-premises authority server also using Code42 cloud storage that do not have a browser connection established on TCP 4285 (HTTPS).
Sign in to the administration console with HTTPS on port 4285 (not port 4280):
- Correct example: https://localhost:4285/console/login.html
- Incorrect example: http://localhost:4280/console/login.html
If your web restore is failing even though you have HTTPS configured correctly, see our web restore troubleshooting tips.
Under the hood
HTTPS is required to connect to storage hosted by Code42. When a POST HTTP request is made to the provider authority server on HTTP, it must attempt a redirect. Since POST doesn't support redirection, the session cannot redirect and the web restore stalls.