Package Server is not serving HTTPS codebases after changing computer hostname
search cancel

Package Server is not serving HTTPS codebases after changing computer hostname

book

Article ID: 173628

calendar_today

Updated On:

Products

IT Management Suite

Issue/Introduction

  • After changing the hostname of the site server with package services, it stopped serving HTTP(S) codebases
  • Package Server is configured to publish HTTP(s) codebases, but could not access it's own Web site.

Environment

  • ITMS 8.X

Cause

  • When checking the SSL bindings for the Default Web Site, noticed the certificate used to bind the port 443 still has the old hostname listed. This caused a mismatch between the certificate's issued to name and the computer's actual FQDN.

Resolution

  • This can be corrected by forcing the NS to reconfigure the site binding for the site server:
    • Go to Settings > Notification Server > Site Server Settings
    • Expand the Site Server, then select Certificates Rollout > Override the Global Settings by custom settings.
    • Enable Install intranet certificate check box, verify existing port used to bind HTTPS traffic and enable the Force overwrite HTTPS binding option
    • Verify the FQDN in the Hosts field then enable this policy and save changes

Powered by Wolken Software