Empty host name on IIS site bindings

[Coskun]

Hi everyone,

Plesk, for an unknown reason to me, creates an "empty binding" on one specific website every time I make a "hosting change" on that very website (subscription in Plesk terms). What I mean by a "hosting change" is things like enabling/disabling SSL, adding/removing aliases and anything similar that might require Plesk to re-arrange the bindings for that website.

The issue exists only on one of the many websites I am hosting/configuring via Plesk, the others don't have any similar issues.

The result of the issue is the given website being stopped by IIS since the "empty binding" is already in use by the "Default Web Site".

If I go ahead and delete the empty binding from the given website, I can start the website up again, so I have a workaround but I am still curious, what might cause the issue?

The Plesk version I am having is 12.0.18 Update #38, which I assume is the latest one.

Please see the attached screen shot below.

 

[scsa20]

Just wondering but have you tried running the reconfiguration command?

"%plesk_cli%\repair.exe" --reconfigure-web-site -web-site-name suna.li

(run that command in an elevated command prompt)

 

[Coskun]

I just tried what you said and have got the response below:

This Web site cannot be started.  Another Web site may be using the same port.
In Microsoft.Web.Administration module
Exception type: Microsoft.Web.Administration.ServerManagerException
   at Microsoft.Web.Administration.Site.Start()
   at IISWebSite.startStop(IISWebSite* , Boolean start)
   at IISWebSite.start(IISWebSite* )

(Error code 1)

The command seems to add that mysterious empty binding again. I remove the empty binding manually and voila, the website can be started up again.

 

[Matthew_Thomas]

remove that binding again and run the reconfig this should fix issue for that and any future sites added the blank binding should only be for default site

 

[Coskun]

Hi Matthew,

Thank you for your suggestions. I have already tried that and the issue still remains. It is not a showstopper for me, since I don't play with that website's settings everyday but I am just curious why would that happen.