FYI: I am seeing this issue:
Upgraded Jira from 7.1.4 to 7.12.3 & Confluence 5.9.9 to 6.12.2. Upgrade via a migrate.

https://ecosystem.atlassian.net/browse/ATST-916

Tracked as https://ecosystem.atlassian.net/browse/ATST-916

Upgraded Jira from 7.3.3 to 7.12.1 and Confluence from 6.2.2 to 6.11.1 and having the same behavior.

v7.12.1 still having the issue

v7.11.2 is having same behavior

Same Behavior on Jira v7.11.2 in combination with Confluence 6.10.2

Seeing the same behaviour after upgrading to Jira 7.12.1 in combination with Confluence 6.4.2 and 6.8.2.

Also seeing this in Jira Server v7.10.1 

I apologize for the inconvenience. Unfortunately, I did not read the title correctly.

@Atlassian;
You need to get this fix and respond to this issue!

Giuseppe - 

If you don't have an external application link, your error is a different one then in this ticket. We've seen this one as well with a load balancer in place. Though we aren't certain it's exclusive to that, we believe it may be exacerbated by it.

That error is an erroneous notice from Jira when it's in the middle of it's sync process where someone happens to refresh and Jira isn't quite sure the links are working due to some operation in the sync process.

That error seems to appear more often the larger your instance grows.

Definitely separate from the /constant/ error message that exists for external links.

Same issue here with Jira 7.11.0, Confluence 6.9.1. 

Jira reports report broken application link, but application link settings reports 'connected' without any errors.

When I refresh/rescan the system health status the error disappears.

Maybe a problem with a reverse proxy setup?

I noticed this error after a few changes inside my proxy config, but I don't know what I changed exactly.

Jira 7.11.2, Confluence 6.11.0. Same problem. Jira reports about broken application links due to network error, but application link settings reports 'connected' without any errors

Same problem with Jira 7.11.0 and Fisheye 4.6.0

We also see this with Jira v7.11.0

we see this error in app links from Jira to Confluence, Bitbucket and Bamboo.

After updating to Jira Software 7.11.1 we have started to see the same problem for our Application Link to Fisheye (newest version).
Atlassian: Wake up!

That sounds like it would disable all warnings about any issues with Application Links, not just these faulty ones... We still want to get warnings about the actual problems if there are any, so that's not an option for us.

Actually there is a way to disable the warning:

• Go to Manage Add-Ons
• Find the Atlassian Troubleshooting and Support Plugin
• Expand the Plugin-View
• Click on the "40 of 41 modules enabled" link on the lower right hand side
• Find the "healthcheck.appLinksStatus.name" module
• Hover over the module and click "Disable"

That worked for me.

There's no way to eliminate the message. Both behaviors... The warning notification and the tag on the link, are by design. Only thing I can figure is Atlassian no longer wants anyone to integrate Jira with non-Atlassian products, but they can't just outright disable that. But someone decided that nagging users over and over may get them to abandon them.

I see absolutely zero functional reason to have a third party app link cause the health check to fail.

Hi,

We are using Atlassian's own Add-on: trello connector for Jira server. When we configure Application link between Jira and Trello, we are getting the message  "Health Check warning for the external application link" under Instance Health checks. Also, we are getting "Non-Atlassian" as status under Application links. The health check fails as a result of this.

Can anyone help?

Regards

Sudhir

This is so annoying.

You think that there is a real issue but not.

Just unnecessary noise.

If you ignore that you will miss real error ...

+1, still waiting on this to be resolved as well and continuing to track.

This issue is approaching its one year anniversary, with "no work logged on this issue."

When can we expect a fix?

Hey guys...

My customer also have this issue and they keep complaining to me about this error... Please give us a way to remove it. Thanks!

Remove this for external links please.  The warning is very distracting and even when you select to not show again, it keeps showing.  This is not an error state and should not throw an alert!

Upgraded to latest 7.9.2 from an old 7.3 to find this lovely warning added now... !  The only hiccup in the whole upgrade procedure

Please remove!

As long as we do not start ignoring real issues - we are getting used to ignoring the warning.

This reminds me of the 80's when "Good Errors" were common place.

Tends to make you ignore errors all together.

Also agree – looking forward to a mechanism to removing this pop-up for external links.

Agree, this is very annoying when logging in everyday. 

Agreed, our entire admin team gets this on a daily (or more) basis because we have an AppLink to NewRelic for some plugin or other.  Please reserve those messages for things that actually need to be fixed.

+1 to adding an acknowledge button or something. This is super annoying.

same on 7.9

Just updated to 7.8.2, same issue

Same on 7.6.4.

Same on 7.5.3

Same on 7.8.0

Not that it needs saying since it's apparently still around as of 7.7, but my company just upgraded server from 7.2 to 7.6.2, and we're encountering this.

Seeing this in Jira v7.7.0 too.

Seeing this with 7.6.3 as well, any workarounds?

Same issue with since 7.4.3. Now with 7.6.1 as well. We are premier support customers. Please provide a fix asap. Getting fed up with these false alarms.

Same problem. Non-profit organisation. Please provide a workaround. Does the option to disable this specific error notification exist? 

JIRA v7.7.0-m0003

We have the same issue, please fix this.

There should not be a Health Check warning or there should at least have a way to discard/accept that the link is legit.

There are instructions in the Jira documentation to setup an external application link. Why make a warning of it ?

Seeing this with Jira 7.5.2 as well.

The following also shows up in the atlassian-jira.log for each such configured Application Link during Jira service startup.

• <Date> <thread> WARN <userid> <sessionid> <IP Address> /plugins/servlet/streams [c.a.streams.internal.StreamsCompletionService] Registering failure for stream provider <Application-Link-Name> due to error other

We have the same problem in 7.5.1 Server, kind of annyoing.
Application link to external application works properly, but health checks warns.