Try to manage add-ons but it didn't connect
when I checked log files found this
http-bio-443-exec-7562 WARN dave 819x1332792x5 47kpwe /rest/plugins/1.0/available/featured [c.a.upm.pac.AddonMarketplaceQueries] Marketplace product query failed: com.atlassian.marketplace.client.MpacException: org.apache.http.conn.ConnectTimeoutException: Connect to marketplace.atlassian.com:443 [marketplace.atlassian.com/220.127.116.11, marketplace.atlassian.com/18.104.22.168, marketplace.atlassian.com/22.214.171.124] failed: connect timed out
2017-04-07 13:41:47,047 http-bio-443-exec-7562 ERROR [o.a.c.c.C.[.[localhost].[/].[default]] Servlet.service() for servlet [default] in context with path  threw exception
http-bio-443-exec-7555 WARN dave 820x1332897x5 47kpwe 10.119.50.17 /rest/plugins/1.0/installed-marketplace [c.a.upm.pac.PacClientImpl] Update check request may take longer because of the number of add-ons
Not sure if this problem is still ongoing. If this was a fluke, then https://status.atlassian.com/ could have indicated if the marketplace site was down during that time. If that site is up, then the problem is more commonly seen to exist on the machine/network running this JIRA server instance.
The most common cause for this kind of error is that JIRA cannot connect to the marketplace site because the system is being restricted from establishing outbound network connections. This could be due to a firewall, or an outbound proxy that the system has to use in order to make connections like this. It can also happen when the server is on an isolated network without internet access.
As a general guide I'd recommend following Configuring Marketplace Connectivity as a means to explain this error and find ways to try to troubleshoot this.
First thing I would try to would be logon to the box running JIRA, then open a browser and see if you can reach the Atlassian Marketplace site directly https://marketplace.atlassian.com
If you cannot reach this site, try other websites to see what you can reach if anything. In this case the restriction likely the server cannot make any outbound network connections or the server does not have a route to that hostname.
If you can reach this site in the browser, but JIRA on the same server cannot, that tends to indicate that JIRA is not configured with the same outbound proxy settings that the host Operating System is. How to configure an outbound HTTP and HTTPS proxy for JIRA has steps on how you can configure JIRA to use outbound proxy settings. You will need to likely contact your network admin to make sure you have the correct settings for JIRA to use. Also applying these settings will require a restart of JIRA before they take effect.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs