I only can see 2 gadgets on JIRA SOFTWARE

Sistemas MGS August 13, 2019

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?

4 comments

Andrew
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 13, 2019

Hi @Sistemas MGS ,

That link is showing in your view?

A.PNG

B.R.

Like # people like this
Sistemas MGS August 13, 2019

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

 

image.png

Andrew
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 13, 2019

Hi @Sistemas MGS ,

Could You please provide details You use cloud or server?

If server I found that https://community.atlassian.com/t5/Jira-questions/Default-dashboard-gadgets-are-missing/qaq-p/338845

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

B.R.

Mohamed Benziane
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 13, 2019

Hi @Sistemas MGS 

 

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

Sistemas MGS August 14, 2019

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 [c.a.t.j.healthcheck.support.GadgetFeedUrlHealthCheck] An error occurred when performing the Gadget feed URL healthcheck
org.apache.http.conn.ConnectTimeoutException: Connect to jira.xxxx.com:443 [jira.xxxx.com/xxx.xxx.xxx.xxx] failed: connect timed out
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
at com.atlassian.troubleshooting.jira.healthcheck.support.GadgetFeedUrlHealthCheck.check(GadgetFeedUrlHealthCheck.java:56)
at com.atlassian.troubleshooting.healthcheck.impl.PluginSuppliedSupportHealthCheck.check(PluginSuppliedSupportHealthCheck.java:49)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

 

If in the browser I use the URL: https://jira.xxx.com:8443 instead of https://jira.xxx.com the error does not occur.

Like Andrew likes this
Sistemas MGS August 14, 2019

We have changed in the system configuration the value of the base URL https://jira.xxxx.com to https://jira.xxxx.com:8443 and it seems that the problem has been solved.

Can this be the solution?

Captura.JPG

Thxs

Andrew
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 14, 2019

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 https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-753894340.html

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

B.R.

Sistemas MGS August 14, 2019

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

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events