Unable to generate HTTPS codebases even after enabling all the respective settings
search cancel

Unable to generate HTTPS codebases even after enabling all the respective settings

book

Article ID: 171291

calendar_today

Updated On: 04-28-2025

Products

IT Management Suite

Issue/Introduction

The Package Service is installed on the SMP.  It seemed to be running correctly but it was not publishing HTTPS codebases. The respective HTTPS codebases settings have been enabled as per the following article:

"Package Server is not publishing HTTPS codebases"

Note: This can also occur on another Site Server and not just for the SMP Server itself running the Package Service.

Environment

ITMS 8.x

Cause

When running both the SMP and Site Server on the same host you can't override the certificate used on the Site Server. This issue is that you'd have two web servers binding to port 443 using two different certificates. This is why it failed.

In the case of a separate Site Server, this issue can be caused by an outdated Site Server certificate or a different Server CA certificate used in the past for the Site Server.

Resolution

To correct the issue, turn off the Custom web communication settings for the Site Server hosted on the same server as the SMP Server. By doing so the Site server can leverage the same certificate used to communicate to the SMP server over HTTPS.

On the SMP Console, under Settings>Notification Server>Site Server Settings, find the affected Package Server under "Site Servers" and click on "Change custom settings" for the "Certificates Rollout" section (depending on the SMP version, it may be called "Web Configuration" section) and turn it OFF.
 
 
Refresh configuration on the SMP Server agent (or Site Server) and it should get a new configuration telling it to use a new certificate using the primary "Server CA" certificate.