Hi everyone,
I updated my Jira Software in Virtual Server from https://jira.host1.com to https://jira.host2.com following these articles:
- https://confluence.atlassian.com/jirakb/how-to-change-the-base-url-in-jira-1005786896.html
After upgrading my Jira server switched to the new hostname but I met these issues below:
1. In browser, when I press Ctrl + left click to open ticket in the new tab, the new tab open a wrong URL https://jira.host2.comhttps//jira.host2.com/browse/ticket-number
2. In Dashboard, when I click on Add Gadget > Load more gadget > the Add Gadget window close
3. In Backlog, when I press Ctrl + left click to open ticket in the new tab, the window flicks 1 time before open this ticket in the new tab
I found these error in log file but I'm not sure it's related to duplicate hostname
2021-05-04 00:15:45,145 http-nio-8080-exec-12 url: /secure/Dashboard.jspa; user: peter.dang.vn ERROR peter.dang.vn 15x111985x1 kryd68 14.160.187.101,127.0.0.1 /secure/Dashboard.jspa [c.t.folio.conditions.AbstractKitoCondition] A license is currently stored, however, it is invalid.
2021-05-04 00:23:08,142 http-nio-8080-exec-13 url: /rest/dashboards/1.0/12901/gadget/13820/prefs; user: peter.dang.vn WARN peter.dang.vn 23x112674x1 kryd68 14.160.187.101,127.0.0.1 /rest/dashboards/1.0/12901/gadget/13820/prefs [c.a.jira.dashboard.JiraDashboardStateStoreManager] Stored state for dashboard with id '12901' is not the same as in-memory state. Trying to rewrite the entire state...
Point 1 in your list of symptoms looks very much like the base url is set incorrectly, like you've added the new url to the old one, rather than replaced it. That would also be one way to achieve both point 2 and 3 as well.
I would also want to check the settings on any proxies you may have, and then any context settings in the Tomcat connector, but please double-check the base url first
I follow the proxy configuration in this article https://confluence.atlassian.com/adminjiraserver0712/configuring-apache-reverse-proxy-using-the-ajp-protocol-959314162.html . During updating base URL, I don't touch to the proxy so I think it's not able a root cause.
For this advise "added the new url to the old one, rather than replaced it", could you share me more more details because I just know 1 method to follow the article of Atlassian and I'm in trouble with it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you didn't change the proxy, how does it know it is now supposed to be serving Jira on the new url?
>For this advise "added the new url to the old one, rather than replaced it", could you share me more more details
When you go into general configuration and amend the base url, did you append instead of copying?
I mean, if the field had:
when you changed it to the new host, did you accidentally put in
https://jira.host2.comhttps//jira.host2.com
instead of
- I ask because what you are seeing is exactly what I would expect to see if you'd put the base url in twice.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For Apache proxy configuration, I just replaced jira.hostname1.com by jira.hostname2.com and ketp all other settings.
For Base URL in Jira settings, I replaced jira.hostname1.com by jira.hostname2.com. I have just checked for sure and no expand https://jira.hostname2.comjira.hostname2.com there. I also followed the article to replace all details that related to jira.hostname1.com by jira.hostname2.com
Another detail is our Jira Maintenance license was expired on 2018, but I don't think it's a reason.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, so that rules out the two problems that would usually cause this.
Next thing to look at is a bit more debugging - if you can hover your cursor over the link to an issue, what is the url being presented in the tooltip?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
After updating Base URL, my Jira works nearly normal. But:
1. On Dashboard, in the gadget Assign to me, if I press ctrl + left click to open in the new tab, the URL will be https://jira.hostname2.comhttps//jira.hostname2.com/browse/<ticket.number>. It seems the system adds https scheme & proxyName to the URL. And pls take note it just happen when press ctrl + left click to open in a new tab.
2. On Dashboard, if I click on Add Gadget > Load all gadget, the Add Gadget popup window will disappear
3. In backlog, if I press ctrl + left click to open a ticket in a new tab, the current window will flick before opening ticket in a new tab
All other activities are normal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But what do the links look like when you hover over them?
If you're worried about the proxy settings, could you post the connector settings and proxypass lines here (obscure hostnames etc)?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The link is correct when I hover over them. It's https://jira.hostname2.com/browse/<ticket.number>. When I left click to open directly, everything is ok, I just meet the issue when press ctrl + left click to open in a new tab.
The proxy setting is ok too, because:
1. I still can left click to open ticket, all other activities are normal, just issue with press ctrl + left click
2. I just changed the hostname in the Apache site configuration file from jira.hostname1.com to jira.hostname2.com without any other changing,
We developed 2 custom add-on, do you think it may be an issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If the urls presented are ok when examined, it rules out Jira from being the problem. The question becomes why your browser is mangling things on ctrl-click
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I fixed the issue. I found the root cause is conflict from one of our custom add-ons
Thank you very much for your support & suggestions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.