Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,370,158
Community Members
 
Community Events
168
Community Groups

How do you get Fisheye to only listen on 1 IP address

I have fisheye/crucible on a windows server that has an IIS web site already on it (an OSQA one like this)

I have got IIS to only listen to 1 IP address.

But Fisheye seems to be stealing the http requests so any request to that server end up at crucible/fisheye.

5 answers

There are 2 IPs on the server. I should be able to assign one to IIS and one to Fisheye.

I don’t see how that is possible if they are running on the same machine?

They need to bind on a port and if it’s already used up by another service or application it will fail to start up.

If they are bound to different port then its a redirection issue on IIS

If there is a redirection setup on IIS check there to see if you can differentiate and redirect based on context or URL/virtualhost settings

I've set IIS to listen to 10.0.0.1 port 80 and I've set fisheye/crucible to 10.0.0.2:80 in the bind section of the config.

But when I go to crucible.x.com I go to the crucible site. And when I go to answers.x.com I also go to the crucible site. DNS is correct.

I've tried setting the bind entry to the ip address and the dns name for crucible and its still not working :(

Try

<web-server context="fisheye">
<http bind="127.0.0.1:8060"/>
</web-server>

Think you can specifiy this on the UI as well and specify proxy settings

I've set IIS to listen to 10.0.0.1 port 80 and I've set fisheye/crucible to 10.0.0.2:80 in the bind section of the config.

But when I go to crucible.x.com I go to the crucible site. And when I go to answers.x.com I also go to the crucible site. DNS is correct.

I've tried setting the bind entry to the ip address and the dns name for crucible and its still not working :(

0 votes

According to Configuring the FishEye Web Server:

Setting HTTP Bind: The hostname the FishEye web server will bind to. This can take the form of a host name and port number, or you can leave the host name blank. If no host name is specified, then FishEye will bind to all available interfaces.

So instead of using ":8060" try "ip.add.dr.ess:8060".
Haven't tried this myself...

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events