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

Apache 404 Error while accessing a TFS-git repository

Darly Senecal-Baptiste
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 20, 2014

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 10.15.254.233] File does not exist: /var/www/html/crucible, referer: https://crucibledev.ert.com/crucible/browse

I want to know that is going on?

Thanks

1 answer

1 accepted

0 votes
Answer accepted
Tom Davies
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
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 https://confluence.atlassian.com/display/FISHEYE/Integrating+with+other+web+serversand see whether your Apache config is as suggested.

Darly Senecal-Baptiste
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 21, 2014

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

Darly Senecal-Baptiste
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 2, 2014

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

Thanks

Tom Davies
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 2, 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?

Darly Senecal-Baptiste
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 5, 2014

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
TAGS
AUG Leaders

Atlassian Community Events