Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

I only can see 2 gadgets on JIRA SOFTWARE

Hello, i have finished the installation of JIRA SOFTWARE 8.3, but i am a problem, i only can see 2 gadgets, no more. How can i see all the gadgets?


Hi @Sistemas MGS ,

That link is showing in your view?



Like # people like this

My JIRA shows this message, in spanish, i cannot see to "load all gadgets"



Hi @Sistemas MGS ,

Could You please provide details You use cloud or server?

If server I found that

and could You please check log files maybe exist more information errors?


Hi @Sistemas MGS 


Can you click on "Vuelva a intentario" this link might load all gadget.

I think it's a problem with port redirection. We make a redirection from port 443 to port 8443 and see in the logs of jira (atlassian-jira.log) the following message:


2019-08-12 13:57:38,587 HealthCheck:thread-3 ERROR [] An error occurred when performing the Gadget feed URL healthcheck
org.apache.http.conn.ConnectTimeoutException: Connect to [] failed: connect timed out
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(
at org.apache.http.impl.execchain.MainClientExec.establishRoute(
at org.apache.http.impl.execchain.MainClientExec.execute(
at org.apache.http.impl.execchain.ProtocolExec.execute(
at org.apache.http.impl.execchain.RetryExec.execute(
at org.apache.http.impl.execchain.RedirectExec.execute(
at org.apache.http.impl.client.InternalHttpClient.doExecute(
at org.apache.http.impl.client.CloseableHttpClient.execute(
at org.apache.http.impl.client.CloseableHttpClient.execute(
at org.apache.http.impl.client.CloseableHttpClient.execute(
at com.atlassian.troubleshooting.healthcheck.impl.PluginSuppliedSupportHealthCheck.check(
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$


If in the browser I use the URL: instead of the error does not occur.

Like Andrew likes this

We have changed in the system configuration the value of the base URL to and it seems that the problem has been solved.

Can this be the solution?



Hi @Sistemas MGS ,

I think it depends on Your wishes. Sure You can work with URL as https://server:port but but you may have problems with legacy links. And users don't like to use some kind of weird URL.

I recommend asking your network support team to use the proxy

Or try to find the reason "ConnectTimeoutException: Connect to " and fix it. I suppose because the redirect works for the external network interface, but does not work when the request comes from or just DN set as localhost in 'hosts' config file.


Thxs Andrew, We'll see what you tell us about using a proxy.


Log in or Sign up to comment

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