Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Fisheye proxy settings on Windows. JIRA looks good, Fisheye is jumbled.


We have installed JIRA and Fisheye on a remote server running Windows Server 2008 r2. Both Jira 7.10.0 and Fisheye 4.5.3 are installed as Windows services. While remote desktop connected to the server we can browse to localhost:8080 for Jira and localhost:8060 for Fisheye. Both work properly. We've setup DNS entries to access the sites via and

Traffic comes in on 443 and is translated to 4343 to the load balancer (jetNEXUS) where we have SSL offload and then layer 7 route to the destination app server on port 8080 (Jira) or 8060 (Fisheye). We're using Windows 2008R2\IIS7.5 for Fisheye and the jetNEXUS are self-contained CentOS-based appliances.

Accessing works correctly.

Accessing loads but the pages are broken. This happens with all browsers. Using development tools to view network traffic all resources load with status 200. Using development tools to view page source for Fisheye I see 5 nested doctype statements. For example:

code... no end of head tag
code ..... etc.

In server.xml for Jira we have this section:

<Connector port="8080" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"

maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"

acceptCount="100" disableUploadTimeout="true" bindOnInit="false" secure="true" scheme="https"

proxyName="" proxyPort="443"/>

For Fisheye we've tried several combinations of proxy settings including:
http bind = :8060
Proxy Scheme = not set
Proxy Host = not set
Proxy port = not set
Site URL =


http bind = :8060
Proxy Scheme = https
Proxy Host =
Proxy port = 443
Site URL =

We've also tried JVM input arguments:

JVM input arguments -Dfisheye.library.path= -Dfisheye.inst=C:\Atlassian\Data\fecru -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.endorsed.dirs=C:\Atlassian\fecru-4.5.3\lib\endorsed -Xmx1024m


JVM input arguments -Dfisheye.library.path= -Dfisheye.inst=C:\Atlassian\Data\fecru -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.endorsed.dirs=C:\Atlassian\fecru-4.5.3\lib\endorsed -Xmx1024m -Dhttp.proxyPort=8060 -Dhttps.proxyPort=8060 -Dhttp.nonProxyHosts=localhost

We're not able to get Fisheye to load properly via remote URL.

What are we missing?



0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

228 views 14 14
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you