Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm using Visual SVN on a server.

Fresh install. Create a new repository. Try to connect using a client

it comes up with "Repository moved permanently to 'https://x.x.x.x:6443/'; please relocate"

I got a feeling it has to do with the IP address that clients use to connect is not the same as the one the server is running on? not sure.

share|improve this question
add comment

5 Answers

up vote 6 down vote accepted

This message means that you are using invalid repository URL. VisualSVN Server repository url looks like http://servername/svn/repos/path. I recommend you to use Copy URL command in VisualSVN Server Manager to get right URL.

share|improve this answer
2  
I had solved the problem already, but effectively this is the right answer for my problem... it was my bad.... I just had /svn and was missing repository name. Obscure error message for "Wrong URL Noddy" –  Keith Nicholas Nov 3 '09 at 23:29
    
+1 I didnt know that. thanks. –  Critical Skill Nov 4 '09 at 3:53
add comment

See if this helps you in resolving this problem.

http://subversion.tigris.org/faq.html#http-301-error

share|improve this answer
add comment

try using svn switch to switch it to the IP address.

share|improve this answer
    
thats for switching the working copy? there is no working copy yet as the error comes up when trying to connect to the server. Or browsing the server. You can however go in via the web interface and see the repository –  Keith Nicholas Nov 2 '09 at 22:54
    
Ah, my bad, for some reason I read the question as saying that it was an existing repo on a reinstall, and so I thought the client already had a connection. –  Jim Deville Nov 2 '09 at 23:12
add comment

FYI: I got this error when I had defined an alias to allow for listing of repositories:


Alias /svn "/var/svn/repos"

<Location /svn/>
  SVNParentPath /var/svn/repos
  SNVListParentPath on
  ....
</Location>

Without the Alias, I would get "Not Found" when browsing to /svn, whereas /svn/ would work.

So it seems a fix for one bug caused another one!

This problem is discussed in the link Critical Skill posted.

share|improve this answer
add comment

I had the same problem. Try changing the SVNParentPath to SVNPath in your httpd.conf file. This is my configuration:

<Location /svn>
   DAV svn
   SVNPath C:\svn_repository\proj1
</Location>

and works fine.

I'm checking the differences between SVNPath and SVNParentPath.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.