After installing a fresh copy of Jira 4.4 and importing my Jira 4.1.1 from backup, I notice a gadget I've created on my dashboard in the 4.1 version come up with the following:
----------------------------------------------------------------------------------
Unknown legacy portlet
This gadget was uninstalled by the administrator. Please delete it from your dashboard.
Error details:
I have the same error report after a fresh and empty 5.0.5 installation. Works fine through HTTP on JIRA port (8180 in this case), but not when using the URL as entered in the base-url in the adminstration interface (using the https scheme).
HTTPS is used in this case, which is terminated as described on the Apache side. This setup is implemented as described in the Atlassian docs and works fine for an older site (4.3.4).
Apache 2.2 isused, so the HTTP-proxy configuration is straight forward and using the parameter "ProxyPreserveHost On".
Strange point is the one that one regarding the "no ALLOW permission" and the section where it tells, that the gadget got deleted.
in the top of the page it tells to be usind the wrong scheme "http instead of https", which is simply wrong, because i use https for the access as well as for the base-url in the JIRA config.
I already checked the involved configurations, did a fresh install (purged DB and jira_home)... nothing changed.
Radoslaw,
Are you saying that the error about the gadgets would have something to do with the Apache not being setup correctly?
That sounds strange to me because it worked fine before I upgraded. I had 5.1.8 and upgraded to 5.2.6 and now most of the widgets fail making Jira like much less useful at this point.
Thank you.
Alexis
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
From memory, I just removed the gadget from my dashboard and recreated it again. It didn't have anything to do with SSL from what I remember.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This page should help in such cases:
https://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+Apache+using+SSL
See section: "Alternative configuration if HTTPS is terminated on the proxy server"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.