# SCM-Manager hosting via nginx proxy broken after 3.0.0 upgrade **URL:** \ **Category:** SCM-Manager Bug Reports\ **Created:** [January 30, 2024, 2:37pm UTC](https://community.cloudogu.com/t/scm-manager-hosting-via-nginx-proxy-broken-after-3-0-0-upgrade/1280 "2024-01-30T14:37:25Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![ckeydel](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/ckeydel/32/1564_2.png) [@ckeydel](https://community.cloudogu.com/u/ckeydel)\ **Post date:** [January 30, 2024, 2:37pm UTC](https://community.cloudogu.com/t/scm-manager-hosting-via-nginx-proxy-broken-after-3-0-0-upgrade/1280/1 "2024-01-30T14:37:25Z")
We have been using SCM-Manager for years as part of a Ubuntu/Plesk server. Plesk manages the subdomain (scm.our-domain.tld) and the SSL certificate so that we can access the server as [https://scm.our-domain.tld/scm](https://scm.our-domain.tld/scm) The way we make this work is, in Plesk, giving additional nginx directives for /scm as follows: ```auto location /scm { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Host $http_host; proxy_pass http://localhost:32180; } ``` As you can see, we expect SCM-Manager to serve without SSL at port 32180 and after the upgrade, I have modified config.yml accordingly. When I open this port in the firewall and access [http://scm.our-domain.tld:32180/scm](http://scm.our-domain.tld:32180/scm), everything works as expected. But accessing the https link no longer works. Instead, I see SCM-Manager “loading plugin information” with the three spinning circles like this: ![image](https://europe1.discourse-cdn.com/flex013/uploads/cloudogu2/original/2X/4/48446103c7f9936c9a652ac3d833381c51f5953b.png) Again, this has worked for years without any issues and only broke after last night’s auto-update to version 3. ---
**Author:** ![luislza](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/luislza/32/1434_2.png) [@luislza](https://community.cloudogu.com/u/luislza)\ **Post date:** [January 30, 2024, 6:57pm UTC](https://community.cloudogu.com/t/scm-manager-hosting-via-nginx-proxy-broken-after-3-0-0-upgrade/1280/2 "2024-01-30T18:57:35Z")
Hi, We’re seeing the same issue on our instance but with Apache - also https → http on internal port. The symptoms are the same - hanging on “loading plugin information”. Kind regards Luis ---
**Author:** ![lxh0508](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/lxh0508/32/1334_2.png) [@lxh0508](https://community.cloudogu.com/u/lxh0508)\ **Post date:** [February 1, 2024, 1:58am UTC](https://community.cloudogu.com/t/scm-manager-hosting-via-nginx-proxy-broken-after-3-0-0-upgrade/1280/3 "2024-02-01T01:58:44Z")
Same issue on my instance. Is it a bug? ---
**Author:** ![ckeydel](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/ckeydel/32/1564_2.png) [@ckeydel](https://community.cloudogu.com/u/ckeydel)\ **Post date:** [February 1, 2024, 6:01am UTC](https://community.cloudogu.com/t/scm-manager-hosting-via-nginx-proxy-broken-after-3-0-0-upgrade/1280/4 "2024-02-01T06:01:30Z")
In software development terms, this is called a regression. I just reported it also in GitHub here: > > > \## Issue description > > When SCM-Manager runs serving http without SSL behind a …https proxy such as Apache or nginx, the loading of the web page doesn't complete. Instead, it shows three spinning circles with the text "loading plugin information". > > \### Bug Report > > \#### Describe how to reproduce the bug > > Running SCM-Manager in default configuration. A https proxy is set up to serve it to the Internet. > > \#### Describe your SCM-Manager setup > > SCM-Manager running fine serving port 32180. Ubuntu 22.4 LTS server with Plesk, using nginx to host SCM-Manager as a proxy. Nginx proxy set up as follows: > > \`\`\` > location /scm { > proxy\_set\_header X-Real-IP $remote\_addr; > proxy\_set\_header X-Forwarded-For $proxy\_add\_x\_forwarded\_for; > proxy\_set\_header X-Forwarded-Proto $scheme; > proxy\_set\_header Host $http\_host; > proxy\_pass http://localhost:32180; > } > \`\`\` > > Version 3.0.0 of SCM-Manager, upgraded from the last 2.x version through apt. > > \#### Which operating system, browser and versions do you use? > > Any. > > \#### Log of the bug > > \#### Further information like screenshots > > See also the community bug report at > https://community.cloudogu.com/t/scm-manager-hosting-via-nginx-proxy-broken-after-3-0-0-upgrade ---
**Author:** ![dervomsee](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/dervomsee/32/1198_2.png) [@dervomsee](https://community.cloudogu.com/u/dervomsee)\ **Post date:** [February 1, 2024, 7:56am UTC](https://community.cloudogu.com/t/scm-manager-hosting-via-nginx-proxy-broken-after-3-0-0-upgrade/1280/5 "2024-02-01T07:56:04Z")
Have you tried to the the config variable `forwardHeadersEnabled` to true? I had the same issue and `forwardHeadersEnabled: true` solved it. > ---
**Author:** ![ckeydel](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/ckeydel/32/1564_2.png) [@ckeydel](https://community.cloudogu.com/u/ckeydel)\ **Post date:** [February 1, 2024, 8:25am UTC](https://community.cloudogu.com/t/scm-manager-hosting-via-nginx-proxy-broken-after-3-0-0-upgrade/1280/6 "2024-02-01T08:25:55Z")
Yes, that fixed it. Thanks! ---
**Author:** ![luislza](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/luislza/32/1434_2.png) [@luislza](https://community.cloudogu.com/u/luislza)\ **Post date:** [February 1, 2024, 12:23pm UTC](https://community.cloudogu.com/t/scm-manager-hosting-via-nginx-proxy-broken-after-3-0-0-upgrade/1280/7 "2024-02-01T12:23:03Z")
Works for us too. Thank you for pointing it out!