Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,415,125
Community Members
 
Community Events
170
Community Groups

[Bug] After upgrade jira v6.4.x to jira-core v7.4.1: Oops, you've found a dead link.

After upgrading from Jira v6.4.14 to Jira Core v7.4.1, the main URL for JIRA returns the following message:

 

Oops, you've found a dead link.
Atlassian
 

An analysis directly on the machine with the links browser shows that jira has lost it's base URL - JIRA is supposed to run from /jira, but instead now runs from /. Is there a mechanism to upgrade jira without jira trashing it's configuration?

1 comment

Hi, 

could you check server.xml file, and base url. 

 

In fact, jira gets from 2 points info:

1. In $CATALINA_HOME/conf/server.xml. I mean context path info

https://confluence.atlassian.com/jirakb/how-to-change-the-jira-application-context-path-225119408.html

2. Next is base_url. You can in admin panel.

3. Additional: just check it on revers proxy if you have it.

 

Ii it is not clear, 

Kindly provide here a server.xml, 

 

Thanks 

Gonchik

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events