Cannot access recently imported SVN repository - 403 forbidden

Craig R Morton
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 1, 2012

We have an issue where we are unable to access a recently imported SVN repository.

There was an issue right at the very end of the import process where, when it was inspecting the directory structure, it timed out.

Is there a way to determine if the SVN repo exists? It spent quite a while importing around 36,000 revisions so I hope there is something there.

When using both TortoiseSVN and SVN at the command line I get the following error:

Server sent unexpected return value (403 Forbidden) in response to OPTIONS request for 'https://XXXjira.atlassian.net/svn'

We have the following repo structure:

/

/1984

/shop

/shop/branches

/shop/tags

/shop/trunk

Do we have to configure our users to access SVN? I cannot see anywhere to do this. Or do we have an issue with structure? The user I am logging in as has admin privileges.

Any help appreciated.

2 answers

1 accepted

2 votes
Answer accepted
Matthew Hunter
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 13, 2012

Hi Craig,

You can configure your SVN repository access at the FishEye administration page at:

https://XXXXXX.atlassian.net/secure/admin/RepositoryProjectList.jspa

By default no one has access to the root directory of subversion, so you'd need to do an ls over /svn/1984 for example. You can give permission to the root directory on the above page if you'd like though. Check out the following documentation for more information:

http://confluence.atlassian.com/display/AOD/Configuring+repository+permissions+for+a+project

Cheers,

Matt

1 vote
Ilerian Co. Ltd.
Contributor
August 20, 2012

Do you use mod_evasive on the apache web server that your subversion exist?

I had the same problem; It was giving 403 error when fisheye tries to connect subversion with to much request which is caused by mod_evasive.

Use DOSWhitelist statement for mod_evasive like the following lines:

 DOSWhitelist   127.0.0.1
 DOSWhitelist   192.168.0.*



Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events