This version of JIRA is unrecognized by the Atlassian Marketplace

TOBBUND August 24, 2020

Hi,

I got this error message in Version&License. 

"This version of JIRA is unrecognized by the Atlassian Marketplace. It might be a non-standard build or be too new to appear."

Could you please help me? How can I fix this?

 

1 answer

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 26, 2020

Hi,

Sorry to hear about this problem.  The error message you mentioned is commonly seen when running an EAP version of Jira.  These are early access program versions of Jira, in cases like this those versions are not listed in Marketplace, which in turn can cause the message you have seen here.

What version of Jira Server are you running here?  I can see that you have indicated 8.11, but that version was release on 15 July 2020, so you should not be seeing this error today.  Perhaps if you installed an EAP or RC (release candidate) version of 8.11, then that might be able to explain the error you see here.

Try going to ⚙︎ > System > System info (or directly visit the URL /secure/admin/ViewSystemInfo.jspa ) and then scroll down to Jira Info.  Let me know what you have for your Build Number value there.  This should be better able to tell us the exact build of Jira you are running here.

Andy

TOBBUND August 28, 2020

Hi, 

I found it which you said.

Build number: 811001

Thank you for your support.

Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 28, 2020

That is the correct build number for the 8.11.0 release. (v8.11.0#811001-sha1:80088f0) is the exact build number I see in the footer of most pages of my Jira site. My own values here:

Version 8.11.0
Build Number 811001
Build Date Mon Jul 13 00:00:00 CDT 2020
Build Revision 80088f01d75d98b126dbf4f3763c1b8161d5db6b

It might be possible that you had a release candidate version (RC) which could still show this kind of error.  But if that is the case, then I would expect the Build Date and Revision to be different here.

Could you grab a screenshot of the entire page where you see this error?  I am curious if perhaps this error is in regards to an application version like Jira Service Desk or Jira Software that might be installed here.

Andy

TOBBUND August 31, 2020

jira 2.JPGjira1.JPGIs that enough for you or do you need more pics?

Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 1, 2020

Well your version is not the problem here.  I suspect that your Jira application is unable to connect to our Marketplace site and in turn the Jira application is unable to confirm what versions of apps/plugins are compatible with your Jira site.

This most commonly happens in networks that might be restricting Jira's outbound connection to our Marketplace site.  I would recommend checking with your network administrator to see if perhaps there is an outbound proxy that Jira would need settings for in order to contact the Marketplace site. 

We could probably confirm this if you could try to load that same page once more, and then immediately check the $JIRAHOME/log/atlassian-jira.log file.  I would expect that you would see some kind of stack trace there that indicates a connecting timeout to our marketplace.atlassian.com site.

 

I'd be interested to see if adding following code under JVM arguments

-Dhttp.nonProxyHosts=localhost|*.atlassian.com

Where *.atlassian.com means Jira should allow all options with .atlassian.com in their URL access through the proxy.
In this case, you would need to add the marketplace.atlassian.com to the list that does not need to pass through the forward proxy

-Dhttp.nonProxyHosts=localhost|marketplace.atlassian.com

We have steps on how you can configure this within Jira over in Configure an outbound proxy for use in Jira server.

Try this and let me know if you have any questions about these steps.

Andy

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.11
TAGS
AUG Leaders

Atlassian Community Events