Hi, I'm trying to run Fisheye behind a proxy. So far, I've managed to get Jira and Stash to work behind the proxy, but not Fisheye.
Here's my config file in Nginx:
server { listen 80; server_name dev.int.com; access_log off; location / { proxy_pass http://IP:8080; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-for $remote_addr; port_in_redirect off; proxy_redirect http://IP:8080/jira /; proxy_connect_timeout 300; } location ~ ^/stash { proxy_pass http://IP:7990; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-for $remote_addr; port_in_redirect off; proxy_redirect http://IP:7990/ /stash; proxy_connect_timeout 300; } location ~ ^/crucible { proxy_pass http://IP:8060; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-for $remote_addr; port_in_redirect off; proxy_redirect http://IP:8060/ /crucible; proxy_connect_timeout 300; } error_page 500 502 503 504 /50x.html; location = /50x.html { root /usr/local/nginx/html; } }
and in Fisheye:
<web-server site-url="http://dev.int.com/crucible" context="/crucible"> <http bind="http://dev.int.com/" proxy-port="80" proxy-scheme="http" proxy-host="dev.int.com/crucible"/> </web-server>
Hi Shamil.
Looking at the FishEye/Crucible config and based on the NGINX proxy config I can see a few problems with the config.xml:
* <http
bind
=
"http://dev.int.com/"> - here it should contain the port where FishEye/Crucible runs -
<http
bind
=
":8060">
* <proxy-host
=
"dev.int.com/crucible"
/> - here the value should be only the name of the proxy host -
<
proxy-host
=
"dev.int.com"
/>
The rest of the configuration does seems ok.
Cculd you please do the modifications above and restart FishEye/Crucible? After that please let me know if the problem was solved.
Cheers,
Douglas Fabretti
Atlassian Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You may also want to add "proxy_buffering off;" to your location as it will force nginx to send reponses syncronously. This will give a more reponsive feel as the user will not have to wait for the page to completely load into the buffer before nginx sends the data to the user.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.