Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,467,374
Community Members
 
Community Events
177
Community Groups

Broke my Jira

Matt DeLaCruz
Matt DeLaCruz Mar 05, 2018

I was configuring Crowd for SSO with Jira. After which the Jira address at 8080 gives a 404. Anything obvious I should check? I don't even know what information to provide. 

 

Well, maybe this: When I was editing those documents I think the instructions indicated to shut down the jira service. I did not do this accidentally. Have I broken my Jira beyond repair? Thanks. 

Answer
Watch
Like Be the first to like this
431 views

1 answer

1 accepted

1 vote
Answer accepted
Daniel Wester
Daniel Wester Rising Star Mar 05, 2018

Check your atlassian-jira.log (and the catalina.log). I would suggest making sure to stop Jira (and make sure it's stopped) and then restart it and watch the logs while it comes back up.

View More Comments
Matt DeLaCruz
Matt DeLaCruz Mar 06, 2018

Thank you for your response! The problem was resolved when I revisted the SSO instructions and restored to the original state and then following the instructions again. 

Like
Reply

Suggest an answer

Log in or Sign up to answer
Crowd
Crowd
TAGS

Atlassian Community Events

See all events