Under Community Review

Have the content manager installer support host headers

In the Content Manager installation process, there is a point at which you are offered the opportunity to select port numbers and host headers for the content manager explorer and the topology manager. Unfortunately, the installer refuses to progress unless you ensure everything is running on a distinct port, while host headers ought to be enough.

Error message during SDL Web 9.0 installation stating 'The specified configuration conflicts with another application or Web site configured on this machine. Select a different IP address, port number or host header.' with Port Number: 80 and Host Header: cm.local.

So far, the only approach that has succeeded for me is to accept the quirks of the installer and afterwards fix things up manually. The number of locations where you have to fix something seems to grow with each release, so it's probably about time to just have the installer do the right thing.

Dominic Cronin
Parents Comment Children
No Data