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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Gadget Titles showing as _MSG_gadget


Some gadgets on our production instance show the titles as _msg_gadget but the gadgets on test instance show the titles correctly as shown in the images attached.

Both are on the latest version of 8.5.0, upgraded last week. This issue existed even before the upgrade.

Could you please provide steps to resolve this.Production_Gadget.JPGTest_Gadget.JPG


2 answers

0 votes

Hi @Pangeel Shubha ,

Do you have the same versions of plugins installed on both environments? If so, maybe you have different locales?

Both instances have same versions of plugins as both versions were upgraded just last week.

I googled a bit and there are a lot of info related to SSLHandshakeException in log. Do you have such kind of errors in atlassian-jira.log? Maybe your test instance works through http while your production works through https.

0 votes

This basically means the Jira server cannot talk to itself.  This could be firewalls, network routing, unusual network config, and quite a few other things.  The most common cause I see is, exactly as @Aleksandr Zuevich suggests, the SSL for Jira to see itself.

If it is the SSL, then the usual cause is that while Jira is happily serving data up over HTTPS, it does not have a certificate that enables it to see itself!

To get to the bottom of this, start with a simple "wget" or "curl" - try to fetch your own Jira's login page from the command line on your Jira server.  Not "get localhost", but check it over the network.  Assuming your Jira is running on "", then log into the server on the command line (doesn't need to be root or anything, any standard human account will work) and run "wget" - the error message you get back will tell us if the problem is network based, or down to SSL.

Thank you for the detailed answer.

The issue got resolved when i was trying your suggestion although it was actually not an issue. When I copied the page address to use in wget command, I noticed that the page was missing the domain part...

Production was http://ourserver:port/

Test was   

When i refreshed the page adding the it works fine.

Apparently, only I was seeing this issue due to the way I was accessing the page :(

Thank you for all your answers and suggestions.

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you