rockhost, I was just directed here by one of my staff and wanted to clarify the reasoning behind how this works.
First, just a note that Centova Cast doesn't bind to port 80 at all unless you enable the port 80 proxy. It's actually the port 80 proxy that's returning that "Nothing here" message.
The reason we don't have it redirect to port 2199 by default is because that would only work for port 80 proxies installed on the same server as the web interface. When you run out of capacity and add another server to your hosting service, your second server runs its own port 80 proxy, but still uses the web interface from your first server. (See the manual for details.)
So to draw you a bit of a picture:
Server A: 220.127.116.11, running web interface on 18.104.22.168:2199 and port-80-proxy on 22.214.171.124:80
Server B: 126.96.36.199, running port-80-proxy on 188.8.131.52:80, and nothing on 184.108.40.206:2199
If server A's port 80 proxy says "aha, I'm running on 220.127.116.11:80 -- let's redirect to 18.104.22.168:2199" that'll work fine.
If server B's port 80 proxy tries the same thing, it'll redirect to 22.214.171.124:2199 and the user will get..... well, nothing really, just a "server connection failed" message in his browser, because there is nothing listening on 126.96.36.199 port 2199.
Granted, the IP of the web interface is passed to the slave server during installation so it would be possible to script some configuration file modifications at that time to tell the proxy to redirect to the web server's IP address, but that seemed a relatively low-priority feature which required more fiddling than it was worth when we were in a time-crunch to get v3 released.