ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Package Server is configured to publish HTTP(s) codebases, but could not access it's own Web site

book

Article ID: 171071

calendar_today

Updated On:

Products

Management Platform (Formerly known as Notification Server)

Issue/Introduction

  • Package server resides on the default Internet Site with Cloud Enabled Management (CEM) active
  • CEM clients are able to download their packages from the package server without issue
  • Connectiontest.html to the package server is successful
  • IIS root page loads via https from the package server
  • Following the tech articles listed under the Related Articles section below has not resolved the issue

 

Package Server could not access own Web Site using HTTPS CEM, although it is configured to serve it. The HTTPS CEM requests from clients cannot be served. See logs for detailed failure reason. (health state: 0x00000330).

Environment

8.0 HF6, CEM

Resolution

In this case, at the NS console location:

Site Management | Internet Sites | Default Internet Site | Site Servers | <SiteServerName>  under the custom settings section, both:

  • Publish HTTP codebase and
  • Publish HTTPS codebase (provided an SSL certificate is installed) were selected. 

Deselecting Publish HTTP codebase, resolved the issue

Powered by Wolken Software