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
Community Members
Community Events
Community Groups

Access Fish Eye & setup URL

Hello I recently configured my jira to a url (proxy/IIS):

Since then, the commits within jira say: "You don't have access to view all related commits. Please contact your administrator."

Also, when i try to access my fish eye, my credentials do not work anymore. I tried to reset the admin password but i still cant get in.

Need help ASAP! 


1 answer

0 votes
Andy Heinzer Atlassian Team Oct 25, 2017

Hi Christos,

When you tried the steps to reset the admin password, after you updated the config.xml did you restart Fisheye in order for these changes to take effect?   If you did not restart Fisheye yet, then that could explain why this is not working yet.   However if you did this, then you should be able to click the Administration link in the footer in order to enter this "admin" password.

If you have done those steps and this still is not working, then we would want to gather your config.xml in order better understand your configuration.   

Please try these steps once more, if this is still not working please let me know by replying here, and in turn I can create a support request on your behalf where we can then gather this file from your privately.


Hi Andy -

Thanks for the reply. Using the Administration link below i was able to login. However, I still can't login with my regular username and password.

Also, as I said to the post I changed my jira url and now I do not have access to the svn commits within jira.

I supposed the next step is to update the Configuration Application Links within jira, and update the proxy for fisheye, but I'm confused to why i dont have access to fisheye anymore....

Just to summarize the issues I'm having:

- Can't login to fish eye with my regular credentials (using crawd for authentication - same creds with jira)

- Want to change my fisheye url with iis proxy

- Commits within jira are not visible anymore

Any ideas?

I think I messed up fisheye and now it is not loading at all.

I have update the settings here:

with the new url and now the site is not comming up.

How can I revert the values from the fisheye server?


I also saw that probably my  regular credentials to fisheye were not working because in the config.xml it was pointing to the old jira url

Btw, I thought this was support? I'm trying to ask a question to the support (which I'm paying) and i always get direct to the community... confused.

Sorry for the multiple replies.... I was able to fix the issue of the fisheye loading by recovering the config.xml - i'm back to these issues:

Just to summarize the issues I'm having:

- Can't login to fish eye with my regular credentials (using crawd for authentication - same creds with jira)

- Want to change my fisheye url with iis proxy

- Commits within jira are not visible anymore

Andy Heinzer Atlassian Team Oct 27, 2017

Hi Christos,
There was a change made back in July of this year in regards to how Atlassian provides support for Starter licenses. explains this change in more detail.  Moving forward, support for starter licenses is provided here, directly in the community site.   Support for other commercial licenses is still provided by Atlassian Support.   When you first create a support ticket on you have to enter a SEN number (support entitlement number).  This form is then directing your request to one location or the other depending on the SEN you enter here.

Login issue:
For the login issue here with Fisheye, I understand you are wanting to use Crowd to manage the login credentials for Fisheye.  Was this setup and working previously already?  Or has this just stopped working since the introduction of the reverse proxy?  Basically, I would want to take a step back to understand those parts first and then use Integrating Crowd with Atlassian FishEye as a guide to make sure that you can use Crowd for this.

This guide will provide the steps you need to take in both applications in order to configure this.

Proxy setup:
As for setting up Fisheye to work with an IIS reverse proxy, we have another guide on the steps needed to complete this.   Please see Proxying Atlassian server applications with Microsoft Internet Information Services (IIS)

Application link update:
Once Fisheye is setup behind this proxy, you will likely need to edit the application link settings in both Jira and Fishey, in order to make this link work.  There are two different approaches you can use for this.  One is to update the URLs in the application link to reflect the updated public URLs.   If this isn't working then we have an alternative method you can use to bypass the proxy in order to create applications links.

Please try to follow these steps and let me know if you run into any problems trying to follow these guides.


Suggest an answer

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

Online AMA this week: Your project management questions answered by Jira Design Lead James Rotanson

We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...

179 views 1 6
Read article

Atlassian Community Events