SVN Not Working

I'm getting this message on
There was an error:
Repo is not accessible. Please check your URL and repo settings.

I'm using a visualSVN server over https on port 8443. I've double checked all the settings but can't get it to work.

I'm wondering if the servers are just overloaded at the moment. Anyone else having trouble or success yet?

Bryan

 

I wonder if it is same issue as me.

Pretty sure it is because they lower case everything, and SVN only works with exact case.

I have https://myiP/Test/trunk and it works checking out. On the unity side it shows https://myiP/test/trunk. Which if I use the lower case does not work.

Hopefully this is a quick fix.

 

Their help section says something about not accepting public SSL certificates. I think that might be it.

 

Gotcha, guess I can test turning off SSL.

 

If anyone from Unity Cloud is listening, you might just need to add this option to the command line:

--trust-server-cert : accept SSL server certificates from unknown certificate authorities without prompting (but only with '--non-interactive')

Source: http://svnbook.red-bean.com/en/1.7/svn.ref.svn.html#svn.ref.svn.sw

 

I'm using the latest version of VisualSVN (without SSL) and it works great.

 

@hypeNate, this is a really awesome tool. Thanks for all your hard work!

 

Great to hear that, i also have the issue with the uppercasing. I'm really eager to test out this service.

 

Thanks, but it's still not working for me. I must be blocked by the SSL requirement. I wouldn't think that would be much of a problem to add support for. Isn't it just built into the SVN client and runs out of the box?

Bryan

 

Thanks! It does appear to be fixed and i am setting up automated builds right now.

 

Support for this would be great.

 

Hi hypeNate. Is the SSL support still in the roadmap?

 

Excellent, the issue I was having has been fixed! Great work, and thanks!

 

It looks like you guys are still working on the SVN+SSH with public keys but I just wanted to put my hand up for this feature. Just got into the beta (awesome thanks!) but all our code is hosted on AWS + EC2 + SVN so we use ssh key pairs to get to everything.

 

Any updates for handling certificates?

 

Any further progress on self signed certificates using SVN? Thanks.

 

Just tried again today and it's still not working for me. Can't get past step 2, where I put in the svn login credentials.

Can't even generate a support ticket because I can't make a project.

 

We use Visual SVN server. I'm not sure we did anything else other than install it on the server and set the port etc.

 

I'm not the one who initially set up our SVN server, but we too use Visual SVN server. I think it's using whatever Visual SVN's default behavior is for certificates.

 

Yes. I am using usr / pw.

 

Hello pals,

I've noticed a minor issue that you might encounter when connecting Unity Cloud Build service to VisualSVN Server over HTTPS when the server has a self-signed certificate. I guess that this should be noted in FAQ somewhere because resolving the issue is very simple. It also makes sense to adjust the error that a user gets in Unity Cloud Build.

Here is the summary of the issue: VisualSVN Server uses secure HTTPS with a self-signed certificate, but the common name specified in the certificate does not match FQDN (Fully Qualified Domain Name) you actually use to access the server. In such case Unity Cloud Build can't connect to VisualSVN Server for security reasons and gives an error. Unfortunately, Unity Cloud Build displays a generic and pretty unclear error in such case, therefore it may be hard to understand what's going on and how to solve this.

For example, the Subversion repository URL you enter in Unity Cloud Build is https://unityvisualsvn.cloudapp.net/svn/MyRepo/, however the self-signed certificate was issued to unityvisualsvn. In such case Unity Cloud build won't let you to access VisualSVN Server repositories with a generic error:

There was an error:
Repo is not accessible. Please check your URL and repo settings.

​

In order to solve this issue you should generate a new certificate via VisualSVN Server Manager console for the FQDN that you use to access VisualSVN Server. In the above example you should generate the self-signed certificate for unityvisualsvn.cloudapp.net. Another solution would be to obtain a valid certificate signed by a certificate authority instead of using a self-signed cert.

​

I guess that you'll encounter the same issue if the server certificate has been expired. Regenerating it should solve the issue as well.

I've also tested other stuff such as different authentication options (Windows / Active Directory and Subversion authentication, https://www.visualsvn.com/support/topic/00039/) and they work well and there should be no issues at all.

The only issue I've noticed is this certificate-related one and I hope that the above summary will help Unity Cloud Build users to connect this service to VisualSVN Server repositories.

 

I use Visual SVN Server with UCB and it works well.

I could not get UCB to work with the self signed cert but someone on another thread here linked a company that provides free certs.

It worked perfectly.

 

This is great to hear! :3 Indeed, installing a valid, signed and trusted certificate is the best solution.

It's OK to use a self-signed cert for testing purposes. Therefore, one might hit the issue I've described when testing VisualSVN Server with Unity Cloud Build using a self-signed certificate issued to a wrong common name. And this might lead to a wrong assumption that UCB does not support HTTPS when connecting to Subversion / VisualSVN Server. IMO, this thread proves the last statement.

Subversion clients allow a user to manually accept certificate with hostname mismatch error and they won't have any issues connecting to VisualSVN Server in such case. But UCB fails with a generic error without giving any clues to the user and without any mention of this in FAQ.

 

I'm not able to use SVN.

My SVN server is hosted on DreamHost, and I double checked the Adress and Login/Password but it still fails with the error : "Repo is not accessible. Please check your URL and repo settings."

Any advice?