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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Issue on instance health check - Getting warning on Gadget feed URL

Hi All,

On checking the instance health check we found an warring returned for the below instance

Gadget feed URL

Please refer below screenshot for reference. Kindly help me to resolve this issue. TIA



1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Dec 02, 2021

Welcome to the Community!

Either your base url is set incorrectly, or your network is misconfigured in a way that prevents the server going out of the network and seeing itself there.

The first one is easy to check - go to your Jira and look at any issue you want.  Look in the browser's url bar and you will see something like https://jira.ourdomain.somewhere/browse/ABC-123 or https://ourdomain.somewhere/tools/jira/browse/ABC-123

Or even just the dashboard, as a non-issue page - that'll be https://jira.ourdomain.somewhere/secure/Dashboard.jspa or https://ourdomain.somewhere/secure/Dashboard.jspa

The base url of your Jira needs to be set to the bit before the "browse"  or "secure".

The networking is harder, you'll need to get on to the server and perform basic DNS lookups, checks on routing, and probably certificates too (the logs will help you find those)

Suggest an answer

Log in or Sign up to answer