Problems when accessing Jira from a non-base url

[Va man]

Hi everyone,

I have a on-premise Jira on v9.1.1 with JIRA Service Management Application v5.1.1

My Jira got a defined base url which is https://myjira.com

For some usages, we need to access this jria from another url, which is https://otherurl.com

Now, for accessing the portal it works properly. my user A can log in, and access his tickets.

Now, when this user A tries to access the "real Jira/Backoffice" (dunno how to call that properly) he can log on without problem too, and see his tickets.

However, my user A can access dashboards when shared with him, but gadgets names are bugged and some gadgets don't even work and/or filters are buggued

I attached a screen to show you that. 

If this user A connects from the base url https://myjira.com, problem dissapears. In both cases, he uses the same account, with same rights, filters and dashboards are properly shared with him. 

I added the https://otherurl.com/* wildcard to the allowlist, but it changed nothing

I seen some 404 not found in the console when requesting from the otherurl.com, on a https://otherurl.com/plugins/servlet/gadgets/error/spec-not-found

When I try to add a gadget, from https://myjira.com I got 24 gadgets and no problem. From otherurl.com I only got 21 (and not the filter result gadget, which is the one in Gadget error on the upper picture

Any clue ? 

[Marc - Devoteam]

Hi @Va man 

I haven't configured Jira on-prem for a long time.

But look at this KB article; fix-gadget-titles-showing-as-__msg_gadget-in-jira-server 

I hope this will help you out.