I accidentally stumbled upon a workaround.
It does not fix the problem in question, but it does allow me to use my repo again.

If I use the file:// connectivity approach, I can connect to the repo.
I did try this a few times, but every time my url was built wrong.

file://my/path/to/repo/myproject/
where I was supposed to use this instead
file:///my/path/to/repo/myproject/

I guess this makes sense now. (needing an extra / to show the absolute path)
But honestly, your comment could be improved, a very obvious typo trap, that could have been handled with an example…

Hope this helps someone out there.

Hey Christopher,

When accessing through file:/// url:
three slashes are mandatory for file URLs when omitting the hostname. Alternatively, file://localhost/my/path should also work.

For https access:

I’ve recently added a SSL validation workaround for acccessing SVN repositories where the certificate isn’t trusted. Can you test whether this fixes your issue?
https://community.openproject.org/work_packages/4197

To use it, add trustedssl: true to your subversion: configuration (please ensure you’re running the most recent released version, 5.0.16 before trying this):

  scm:
    subversion:
      trustedssl: true

You can also verify that you’re hit by this problem if manually using svn info <https://URL> requires you to temporarily / permanently accept the certificate.

Best,
Oliver

Hey Oliver.

Thank you for your reply, the improvements was very much welcome. So thank you.

Regarding using localhost in the url, it didn’t do the trick for me.
(still getting the http error 500)

Moving on I did a manual upgrade to version 5.0.16
for testing your https access validation workaround.
(Manual install actually forced me to do a full reinstall using the better part of a day here, sigh )

After getting everything up and running again, I tried adding the trustedssl: true
apparently it didn’t change anything in my scenario, I didn’t expect that either, since the certificate is signed.
I like the fact that it is possible now, so thanks for that anyway.

The svn info cmd did not ask for anything. (so I guess it accepts the certificate)

Thanks for your help.

Hi Christopher,

thanks for the follow up. Do you get any output of the form SVN access error: <...> in your production log?

A side question: Why did you choose a manual installation over the packaged one?

Best,
Oliver

Yes, I do have something in my production log.
And surprisingly it seems to show that I actually have a SSL certificate issue (some info is removed)

ws: 14.6ms | ActiveRecord: 2.5ms)
I, [2016-03-19T22:21:24.442168 #9953]  INFO -- : Started GET "/projects/......../repository" for 2.111.195.142 at 2016-03-19 22:21:24 +0100
I, [2016-03-19T22:21:24.443241 #9953]  INFO -- : Processing by RepositoriesController#show as HTML
I, [2016-03-19T22:21:24.443272 #9953]  INFO -- :   Parameters: {"project_id"=>"..........r"}
E, [2016-03-19T22:21:24.459479 #9953] ERROR -- : SVN access error: svn: E230001: Unable to connect to a repository at URL 'https://url'

E, [2016-03-19T22:21:24.459528 #9953] ERROR -- : SVN access error: svn: E230001: Server SSL certificate verification failed: issuer is not trusted

I, [2016-03-19T22:21:24.460419 #9953]  INFO -- :   Rendered common/_error_base.html.erb (0.1ms)
I, [2016-03-19T22:21:24.460535 #9953]  INFO -- :   Rendered common/error.html.erb within layouts/base (0.3ms)
I, [2016-03-19T22:21:24.462297 #9953]  INFO -- :   Rendered common/_favicons.html.erb (0.3ms)
I, [2016-03-19T22:21:24.473436 #9953]  INFO -- :   Rendered search/_mini_form.html.erb (0.3ms)
I, [2016-03-19T22:21:24.475017 #9953]  INFO -- :   Rendered layouts/_action_menu.html.erb (0.0ms)
I, [2016-03-19T22:21:24.475389 #9953]  INFO -- : Completed 500 Internal Server Error in 32ms (Views: 14.0ms | ActiveRecord: 2.4ms)

Please guide me in how to proceed from here, I would love to get into the bottom of this.

The reason for the manual install is because the packaged install is lacking the PostgreSQL adapter
With a background as DBA, I find MySQL so limited, that I simply refuse to use it.
I guess the short answer is “personal reasons”

Ps.
This is the production specific configuration, from my configuration.yml

production:
  rails_cache_store: :memcache
  scm:
    subversion:
      trustedssl: true
      client_command: /usr/bin/svn

Hey Christopher,

the following line is what got me to add that workaround from https://community.openproject.org/work_packages/4197/activity

E, [2016-03-19T22:21:24.459528 #9953] ERROR -- : SVN access error: svn: E230001: Server SSL certificate verification failed: issuer is not trusted

Did you restart the server after you added the SSL configuration option?

Best,
Oliver

Hi Oliver

Yeah, I did the

touch tmp/restart

But to make sure, I just did a full restart of apache,
and you know what? now it works.

The oldest most used trick in the book, a freaking restart.
Well. Thanks a bunch, feels good to know the issue is solved, and that I might have helped in the process finding it.

Best regards.
Christopher.