# Cannot access through reverse proxy after upgrading

**URL:** <https://community.cloudogu.com/t/cannot-access-through-reverse-proxy-after-upgrading/1425>\
**Category:** SCM-Manager (General)\
**Created:** [January 12, 2025, 2:33am UTC](https://community.cloudogu.com/t/cannot-access-through-reverse-proxy-after-upgrading/1425 "2025-01-12T02:33:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jpow1987](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/jpow1987/32/1552_2.png) [@jpow1987](https://community.cloudogu.com/u/jpow1987)\
**Post date:** [January 12, 2025, 2:33am UTC](https://community.cloudogu.com/t/cannot-access-through-reverse-proxy-after-upgrading/1425/1 "2025-01-12T02:33:28Z")

</div>

I updated to the latest version, and the reverse proxy no longer works. I noticed that when navigating to the site, the http changes and throws an :8443 after the address. Nginx configuration didn’t change between the old and the new update.

---

<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:** [January 13, 2025, 7:28am UTC](https://community.cloudogu.com/t/cannot-access-through-reverse-proxy-after-upgrading/1425/2 "2025-01-13T07:28:11Z")

</div>

Hi @jpow1987 ,

welcome here. To be honest, this is a bit vague. What was your version before the update? If it was a 2.x, did you take a look at the [migration docs](https://scm-manager.org/docs/3.6.x/en/administration/scm-server)? The docs regarding [reverse proxies](https://scm-manager.org/docs/3.6.x/en/administration/reverse-proxies/) might be helpful, too.

If SCM-Manager changes the url, you probably have set a base URL and enabled “Force Base URL”. If this does not help you, we’d need some more information about your configuration like your `config.yml`, the nginx set-up and the global configuration in SCM-Manager.