_Si_ wrote:Hopefully this is just me getting myself tangled in knots. Our current server setup is: apache running on 80 for http, 443 for ssl. Then sfs2x running 8080 for http and 9933 for socket. Which I presume is standard for single server installs?
Yes, those are the out-of-the-box settings.
A lot of our clients are on closed intranets where they remap their http port to be something other than 80 or 8080. I believe it's to do with content control or something, I just know it's pretty much common practice.
This I don't understand. I don't know about these re-mappings, but let me give you an example. If you want to access Google's homepage you will need to "talk" to Google's server on port 80. That's the default for HTTP. And it cannot be "remmapped". Google's website will always be reachable on the default HTTP port (i.e. 80)
The same applies for the BlueBox, if you run it on port 8080 (or any other port) that number is what all of your clients will need to use
We've had it tested by a client who has 8080 closed and the connection fails.
Of course, if the firewall in front of the client doesn't allow port 8080 there's no way around it. He won't connect. Period.
BUT... The solution is to use port 80 for the BlueBox. As I mentioned, port 80 is highly unlikely to be filtered otherwise nobody would be able to access any website at all.
Of course, you said you are already running Apache on 80/443 so this is a problem at the moment. In any case this easily solvable by adding another network card to the server. If the server is virtual (VPS, Cloud...) it takes a few seconds, otherwise you will need to spend those 15 bucks and install it on the machine (or have it installed for you).
This way you will have a new IP address on which you will be able to bind port 80 (BlueBox) and 443 (SFS socket).
Hope it's clear now
