"What’s new" section on Self-managed installations generate incorrect url when use external_url parameter
Summary
When I click on the button "Help -> What's new" the section goes blank trying to load but does not show any information.
Steps to reproduce
Click on the button "Help -> What's new".
Example Project
It is not a question associated with a project but with the self-managed installation. We have the instance installed under the URL: <local_domain>/gitlab (configures in gitlab.rb with 'external_url' parameter) and if I enable browser debugging when clicking the "What's new" link, I see that it tries to load the content <local_domain>/-/whats_new?v=... without the reference to "/gitlab" --> <local_domain>/gitlab/-/whats_new?v=...
What is the current bug behavior?
The link try to load the address <local_domain>/-/whats_new?V=...
What is the expected correct behavior?
The link should try to load the address <local_domain>/gitlab/-/whats_new?V=... or <external_url_value>/-/whats_new?V=...
Relevant logs and/or screenshots
Output of checks
This bug happens on self-managed instance.
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Ubuntu 20.04 Current User: git Using RVM: no Ruby Version: 2.7.4p191 Gem Version: 3.1.4 Bundler Version:2.1.4 Rake Version: 13.0.6 Redis Version: 6.0.16 Git Version: 2.33.0. Sidekiq Version:6.2.2 Go Version: unknown GitLab information Version: 14.4.1 Revision: 1a23d731c9f Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 12.6 URL: http:///gitlab HTTP Clone URL: http:///gitlab/some-group/some-project.git SSH Clone URL: git@:some-group/some-project.git Using LDAP: yes Using Omniauth: yes Omniauth Providers: GitLab Shell Version: 13.21.1 Repository storage paths: - default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
Checking GitLab subtasks ...Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 13.21.1 ? ... OK (13.21.1) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Gitaly ...
Gitaly: ... default ... OK
Checking Gitaly ... Finished
Checking Sidekiq ...
Sidekiq: ... Running? ... yes Number of Sidekiq processes (cluster/worker) ... 1/1
Checking Sidekiq ... Finished
Checking Incoming Email ...
Incoming Email: ... Reply by email is disabled in config/gitlab.yml
Checking Incoming Email ... Finished
Checking LDAP ...
LDAP: ... Server: ldapmain LDAP authentication... Success LDAP users with access to your GitLab server (only showing the first 100 results) User output sanitized. Found 100 users of 100 limit.
Checking LDAP ... Finished
Checking GitLab App ...
Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 3/1 ... yes 3/2 ... yes 3/4 ... yes 3/6 ... yes 3/7 ... yes 3/8 ... yes 20/11 ... yes 3/12 ... yes 22/14 ... yes 3/15 ... yes 24/17 ... yes 24/18 ... yes 24/19 ... yes 3/20 ... yes 26/21 ... yes 26/22 ... yes 3/23 ... yes 3/24 ... yes 26/25 ... yes 26/26 ... yes 26/27 ... yes 26/28 ... yes 3/29 ... yes 37/30 ... yes 37/31 ... yes 37/32 ... yes 37/34 ... yes 3/35 ... yes 3/36 ... yes Redis version >= 5.0.0? ... yes Ruby version >= 2.7.2 ? ... yes (2.7.4) Git version >= 2.33.0 ? ... yes (2.33.0) Git user has default SSH configuration? ... yes Active users: ... 23 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished