# Upgrade page links to https://admin/upgrade **URL:** https://meta.discourse.org/t/upgrade-page-links-to-https-admin-upgrade/38552 **Category:** Bug **Created:** [January 27, 2016, 5:21am UTC](https://meta.discourse.org/t/upgrade-page-links-to-https-admin-upgrade/38552 "2016-01-27T05:21:04Z") **Posts on this page:** 4 **Page:** 1
### Author: ![Blaisorblade](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/blaisorblade/32/107357_2.png) [@Blaisorblade](https://meta.discourse.org/u/Blaisorblade) #### Post date: [January 27, 2016, 5:21am UTC](https://meta.discourse.org/t/upgrade-page-links-to-https-admin-upgrade/38552/1 "2016-01-27T05:21:04Z")
Short version: on Discourse 1.4.3, the upgrade link now leads literally to the broken `https://admin/upgrade` (and I don’t have `admin` as a hostname), both with the previous and the current docker\_manager (if that makes a difference). This worked before, so it’s confusing. Thankfully, it’s a minor issue because I can’t still use the correct URL `https://FQDN/admin/upgrade`. My Discourse is behind reverse proxy, but I don’t see config changes there that are _obviously_ at fault. Latest change I did was to the container `.yml` config, adding `tiny` as init process to workaround the bug in the AUFS kernel module. ### What I did: I’m running Discourse 1.4, and upgraded until 1.4.3. When trying to upgrade to 1.4.4, the upgrade link is to `https://admin/upgrade` instead of `https://FQDN/admin/upgrade`— not good. But the latter page still “works” — upgrading Discourse is disabled, so I tried upgrading Docker manager hoping it’d help. This seems intended and normal, though the GUI does not show this dependency perfectly so I didn’t know this would help — [indeed, people do get stuck](https://meta.discourse.org/t/unable-to-upgrade-discourse/25728). But this is a minor (and orthogonal) usability issue, so I’ll shut up After that, the upgrade link still leads to [https://admin/upgrade](https://admin/upgrade), but the correct URL works fine and allows me to complete the upgrade. ---
### Author: ![fearlessfrog](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fearlessfrog/32/119653_2.png) [@fearlessfrog](https://meta.discourse.org/u/fearlessfrog) #### Post date: [February 9, 2016, 4:42pm UTC](https://meta.discourse.org/t/upgrade-page-links-to-https-admin-upgrade/38552/2 "2016-02-09T16:42:11Z")
Same issue for v1.4.4 upgrade. Broken link as shown by this beautiful red arrow: ![](https://global.discourse-cdn.com/meta/original/3X/2/e/2eaf17256dea8a7653f941962a2ea0f74d6cce9e.png) Manually typing the full address works ok. ---
### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam) #### Post date: [April 1, 2016, 5:51am UTC](https://meta.discourse.org/t/upgrade-page-links-to-https-admin-upgrade/38552/3 "2016-04-01T05:51:45Z")
I am not seeing this happen on latest so as much as this sucks I got to close this, only way to fix it is upgrade your instance and we can not do that without you doing a manual upgrade ```plaintext cd /var/discourse ./launcher rebuild app ``` ---
### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam) #### Post date: [April 1, 2016, 5:51am UTC](https://meta.discourse.org/t/upgrade-page-links-to-https-admin-upgrade/38552/4 "2016-04-01T05:51:49Z")