Enterprise Manager works with http, but not with https

KB ID: 1168
Product: Veeam Backup & Replication
Version: All
Published: 2011-08-22
Last Modified: 2022-05-06
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

  • Enterprise Manager webpage inaccessible via HTTP and HTTPS

    or
  • The Enterprise Manager is accessible via HTTP, but not via HTTPS.

Solution

Enterprise Manager webpage inaccessible via HTTP and HTTPS

Check the following on the Machine where the browser is running:

  • Clear the browser's cache and cookies, or try accessing the Enterprise Manager page using the browser's Private/Incognito mode.
  • Test if the machine can reach the Enterprise Manager web ports. The default ports are 9080 and 9443.

 

Check the following on the Enterprise Manager server itself

  • Make sure that the Veeam Backup Enterprise Manager service is running.
Veeam Backup Enterprise Manager Service
  • Open Internet Information Services (IIS) Manager and make sure that the "VeeamBackup" site is in a started state.
Site Running
  • In the Internet Information Services (IIS) Manager console under Application Pools, check that the VeeamBackup application pool exists and has at least one linked application.
Application Pools
  • Within Internet Information Services (IIS) Manager, make sure that Anonymous Authentication is enabled for the VeeamBackup site.
Anonymous Auth

Enterprise Manager webpage accessible via HTTP, but not HTTPS

Create a new Self-Signed Certificate for the HTTPS connection:

  1. Open Internet Information Services (IIS) Manager
  2. In the left-side panel, select the root entry (the one with the hostname of the server) 
  3. In the middle panel, within the IIS section, double-click on the entry named Server Certificates
  4. In the Server Certificates section, on the right-side in the the Actions panel, click Create Self-Signed Certificate...
  5. Specify a name for the new certificate and Click OK
  6. In the left-side panel, expand the Sites node and right-click on the VeeamBackup entry, within the context menu click "Edit Bindings..."
  7. In the Site Bindings list, select the https entry and click Edit.
  8. At the bottom of the Edit Site Binding window, click the drop-down menu labeled SSL certificate and select the recently created Self-Signed Certificate, then click OK and close on the next window.
  9. Restart the VeeamBackup site
    1. In the left-side panel, select the Sites node.
    2. In the Sites section, click on the VeeamBackup entry.
    3. On the right-side Actions panel, under Manage Website, click Restart.
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.