# Svn repository relocated after scm upgrade from 1.6 to 2.3

**URL:** <https://community.cloudogu.com/t/svn-repository-relocated-after-scm-upgrade-from-1-6-to-2-3/527>\
**Category:** SCM-Manager (General)\
**Created:** [February 13, 2022, 8:32am UTC](https://community.cloudogu.com/t/svn-repository-relocated-after-scm-upgrade-from-1-6-to-2-3/527 "2022-02-13T08:32:52Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![shai](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/shai/32/301_2.png) [@shai](https://community.cloudogu.com/u/shai)\
**Post date:** [February 13, 2022, 8:32am UTC](https://community.cloudogu.com/t/svn-repository-relocated-after-scm-upgrade-from-1-6-to-2-3/527/1 "2022-02-13T08:32:52Z")

</div>

I’ve upgraded scm to 2.3 from 1.6.  
My setup is running behind nginx proxy which handles https calls and proxies them into localhost:8080.

I’ve installed the new version, ran it and went through the migration wizard. After that the manager was stuck on ‘loading plugins information’. After some investigating I saw that the plugins call was made to [http://myDomain:443/scm/](http://myDomain:443/scm/)… instead of https. The only way I was able to solve this is by adding the following line to nginx:  
**add\_header ‘Content-Security-Policy’ ‘upgrade-insecure-requests’;**  
This solved my web ui issues but working with svn is still a problem.  
Scm insists that the repository has been relocated to [http://myDomain:443/scm/](http://myDomain:443/scm/)…  
for some reason ‘scm’ is insisting on working with http and not https. When I look at the repository settings through the web ui it tells me that to check out the command is:  
‘svn checkout [http://myDOmain:443/scm](http://myDOmain:443/scm)…’  
Any ideas on how to solve this problem?

---

<div class="post-metadata">

**Author:** ![pfeuffer](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/pfeuffer/32/72_2.png) [@pfeuffer](https://community.cloudogu.com/u/pfeuffer)\
**Post date:** [February 14, 2022, 8:53am UTC](https://community.cloudogu.com/t/svn-repository-relocated-after-scm-upgrade-from-1-6-to-2-3/527/2 "2022-02-14T08:53:03Z")

</div>

Hi, my first approach here would be to configure your base url in “Administration” → “Settings” → “General” to your correct `https://myDomain/scm/...` url with “https”.

---

<div class="post-metadata">

**Author:** ![shai](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/shai/32/301_2.png) [@shai](https://community.cloudogu.com/u/shai)\
**Post date:** [February 14, 2022, 11:01am UTC](https://community.cloudogu.com/t/svn-repository-relocated-after-scm-upgrade-from-1-6-to-2-3/527/3 "2022-02-14T11:01:40Z")

</div>

I’ve done that, should of mentioned it. It doesn’t help

---

<div class="post-metadata">

**Author:** ![shai](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/shai/32/301_2.png) [@shai](https://community.cloudogu.com/u/shai)\
**Post date:** [February 14, 2022, 1:57pm UTC](https://community.cloudogu.com/t/svn-repository-relocated-after-scm-upgrade-from-1-6-to-2-3/527/4 "2022-02-14T13:57:56Z")

</div>

I now see that I’ve been looking at it in a wrong way. I thought my problem was that for some reason the server does not understand ‘https’ on these non browser calls. However I now see that I didn’t notice that the problem is that my repo location actually changed during the upgrade. In version 1.6 my repo path was  
/scm/svn/…  
now it moved to /scm/repo/svn/…  
Is there a way to move it to the correct location?

---

<div class="post-metadata">

**Author:** ![pfeuffer](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/pfeuffer/32/72_2.png) [@pfeuffer](https://community.cloudogu.com/u/pfeuffer)\
**Post date:** [February 15, 2022, 2:26pm UTC](https://community.cloudogu.com/t/svn-repository-relocated-after-scm-upgrade-from-1-6-to-2-3/527/5 "2022-02-15T14:26:02Z")

</div>

Sorry, for Git and HG we managed to create redirects with the “legacy plugin”, so that old repositories will still work after migration without changing the configuration. SVN though does not accept these redirects and only shows a message that the repository has moved (I don’t know, whether the can be configured otherwise).

The URLs cannot be changed in SCM-Manager.

---

<div class="post-metadata">

**Author:** ![shai](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/shai/32/301_2.png) [@shai](https://community.cloudogu.com/u/shai)\
**Post date:** [February 15, 2022, 2:39pm UTC](https://community.cloudogu.com/t/svn-repository-relocated-after-scm-upgrade-from-1-6-to-2-3/527/6 "2022-02-15T14:39:23Z")

</div>

Thanks,

Since it is not an https problem I can easily relocated the local copy to the new location. No Worries.

---

<div class="post-metadata">

**Author:** ![felix.ebert](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/felix.ebert/32/1554_2.png) [@felix.ebert](https://community.cloudogu.com/u/felix.ebert)\
**Post date:** [July 22, 2022, 9:34am UTC](https://community.cloudogu.com/t/svn-repository-relocated-after-scm-upgrade-from-1-6-to-2-3/527/7 "2022-07-22T09:34:19Z")

</div>

I have closed this thread since there was no activity in the last 30 days.
