Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Apache 404 Error while accessing a TFS-git repository

Hi Team:

I recently was adding a TFS-git repository (located overseas) into FeCru. Connection was correct, reindexing was done without any issue. However, user access to the content of that repository through Fisheye, and Apache 404 error is thrown. Looked at the FeCru log, nothing. Looking at Apache log there is an error that mention the following

[Tue May 20 16:42:43 2014] [error] [client] File does not exist: /var/www/html/crucible, referer:

I want to know that is going on?


1 answer

1 accepted

0 votes
Answer accepted
Tom Davies Atlassian Team May 21, 2014

It looks as though your Apache configuration isn't correct -- please try accessing FeCru directly, rather than via Apache. If that works, have a look at see whether your Apache config is as suggested.

Hi Tom

To be honest, the that error was caused by a Load Balancer (SSL offloader) instead of Apache, which is not linked to Crucible

Very funny from Apache and from Fisheye as well.

I included another TFS-git repository (from the same server) into Fisheye through the https (Load Balancer) and user was able to access to the second repository, but still, for the first repository the user still get the 404 Apache error


Tom Davies Atlassian Team Jun 02, 2014

Can you access the first repository if you go to FishEye directly instead of through your load balancer?

What's an example of a working URL and a non-working URL?

Hi Tom:

I was able to access to the first repository if I go to Fisheye directly.

In concerns of (non) working URLs, there is an example.

(Non Working) http://user1@as-tfs2013-val:8081/tfs/defaultcollection/_git/NonWorkingRepo/

(Working) http://user1@as-tfs2013-val:8081/tfs/defaultcollection/_git/WorkingRepo/

Suggest an answer

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

Step up your DevOps game webinar Q&A series - Questions answered!

  On October 21st, 2020 we hosted a webinar titled,   Step Up You DevOps Game with 4 Key Integrations for Jira and Bitbucket. We had a great showing and high engagement, but that meant th...

106 views 0 1
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