Virtual Center coexisting with other software on server?

[ErjaAndStal]

Nooo, we can't have that in the 21st century ...

For some reason the developer of this part of Virtual Center decided to listen (bind the used socket) on every available interface and IP on the server where VC is installed. Since it always uses port 80 this makes it impossible to have it coexist with other server software that actually can bind to a specific adress but wants to use that port.

Through an SR I found out that that is just the way it is so here is an attempt to force a change by public ridicule.

How can someone even consider writing a networking server without that feature? Especially since it takes all of five minutes to implement.

[Veers]

Hi,

Samething here with vSphere server 4. Anyone know a workaround?

Thank you!

[schepp]

go to the vcenter settings and change it's ports for http. Tada, port 80 is free again

[Veers]

Humm...I need port 443 more than 80. And if I change this one, I have to enter it when I connect to VC with the client.

Anyone try a reverse proxy or something like that?

[bulletprooffool]

Hmmm . . . Virtualise vCentre onto a new VM :smileyblush: that way it can have all the ports back?

Alternatively, does your other app have the ability to change SSL locations etc?

[Veers]

Yes, I can change the port for my other apps. But I don't want my user to have to enter the port number when they access VC or my other apps.

This is more a "user friendly" thing than a real "technical" problem. 🐵

[bulletprooffool]

I am not sure that you'll need to specify the 443 change, as you are automaticvally redirected to this.

Could you lay a redirect web page on the front of your VC and have that push you to the port you change it to?

[Veers]

If I change the VC listening port, I have to specify when I connect with VCclient (Ex: server1.example.com:444).

I did't try a redirect, this is my next step. I let you now the result!