Sorry I don't have an answer for you, but I'm going to watch this thread like a hawk because I have a somewhat similar issue.
We have IIS and Tomcat running on the same physical machine. IIS hosts some website (not Clearspace) and Tomcat hosts Clearspace. Both IIS and Tomcat have been assigned their own IP addresses. In IIS you can configure this in IIS manager and in Tomcat I believe you do this in server.xml.
"In theory", this configuration allows you to have both IIS and Tomcat live on the same machine using port 80, because they each are running on their own dedicated IP addresses.
Unfortunately for us, IIS continues to work fine. But when we try to hit Tomcat (ie. Clearspace), we're constantly getting HTTP 400 (Invalid Hostname) errors.
I know it's not the same issue that you're seeing, but I'm still interested in your issue. If anyone has any ideas/suggestions for either of us, that would be great
Ye, IIS having easy to add host headers, is wonderful.
However I love working on Linux and after getting Openfire to run on one IP.
I am determined to do the same for Clearspace.
Either by vhost or dedicated ip.
One other thing, has anyone attemped to rewrite the URL?
Would love some info on that as well.
Just to close the loop on my part of the thread for anyone interested. We wanted to run Clearspace with Tomcat use port 80 on one IP address on the server and have some other website with IIS use port 80 on another IP address on that same server. We were getting Error 400 (Invalid Hostname) messages when connecting to Clearspace and couldn't figure out why.
And this is where it gets <sarcasm>awesome</sarcasm>. As odd as it may seem, when IIS starts, it binds to all IP addresses on the server, not just the IP addresses that are assigned to web sites that IIS is configured to serve. More specifically, the service does not bind every IP Address in the system explicitly, but binds to a generic address 0.0.0.0. So when you tell it to only listen to a specific IP address it still binds to every IP Address and every NIC in your system.
You can tell that this is happening by entering the following command at the DOS prompt:
Have a look at the output. You will see that a lot of the services are connected to 0.0.0.0. Among those services may be SMTP (25), POP3, NNTP, HTTP (80) and HTTPS (443) when they are installed.
To make it stop doing this, you have to disable socket pooling. Depending on the version of IIS you're running, the steps vary to a degree. But there's more information on this in the MS KB here:
Now, sorry to interrupt waCraig! Let's get back to solving your issue!
Any ideas clearspace team?
All I managed to do was get it to run on port 80, and make the other site run on port 8008, as I require clearspace to be on port 8080, Url rewriting might be a better option.
Have you looked into Apache proxy servers to try to accomplish this? I'm not sure the exact way to configure this, but I believe this could be a solution to what you are trying to do.
At the moment, all is working beautifully, besides the fact that I had to change Openfire to run on port 8008. Perhaps Apache proxy is a solution, I will look into that. ta
(clearspace root folder)/server/webapps/ to "ROOT"
I didnt notice any files in there necessary for Clearspace to run. But just in case, Backup the current ROOT folder.
To clear up this open question.
I just had to add the attribute - address="(ip of server)"
address="(ip of server)"
enableLookups="false" redirectPort="443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />
It now runs on just one ip and not the whole interface.
I have used Apache's proxy mod to do similar things in the past.
(where webserver would be your web server and appserver is hosting the tomcat instance with your clearspace / openfire app).
From memory, the module's required are as follows:
In other applications I have seen mod_jk / isapi redirectors employed to allow a web server (or web servers) to handle the static content leaving tomcat to provide the generated content.
For jivebase_url (or the jiveURL variable) there appears to be an interface to change the jiveURL variable in the (Clearspace admin) management -> settings, which presumably modifies the entry in the jiveproperty table. (i.e. to http://webserver/clearspacex for the example above.)
I'm not sure if this solution is endorsed by Jive, but I believe it to work.