Plugins don't want to load details

[Paweł Mroczek]

After the change of JIRA license some plugins don't want to load details.

Below are the answers to the questions you probably will ask :)

• Which plugins do not load?
  Only those plugins that have a license key. In my case Tempo Timesheet, ScriprRunner and JSU.
• After changing the license to JIRA, did you change the license keys for the plugins?
  Yes I changed them.
  I had to use a workaround - I turned off "Connect to the Atlassian Marketplace" and then the plugins details started to load, and I can able to changed the license keys.
• Have you restarted JIRA?
  Yes, I restarted JIRA several times.
• Did you delete the plugins cache?
  Yes, I removed all plugins cache.

Does anyone know the solution why with "Connect to the Atlassian Marketplace" turned on, the plugin details won't load?

Unfortunately, a workaround (disabling "Connect to the Atlassian Marketplace") in this case is not helpful, because then it does not get news about plugin updates.

[Benjamin]

I have observe this. This happens when my Jira instance is not connected to the internet. I have some jira instances that are internal that have this issue. But the ones that are external, there is no issues. I think the reason is because it is trying to pull information internet for possible updates. 

Hope this helps answers your question

[Paweł Mroczek]

The network is not a problem here. My instance is available from the internet and has access to the atlassian marketplace.
The problem concerns only plugins that were installed on my instance
In general, my JIRA has access to the marketplace and I can install found add-ons from "Find new apps".

[Benjamin]

If not network issues or dns problems, have you updated the UPM?

[Paweł Mroczek]

Hi @Benjamin ,

I found the cause of the problem.
Our network administrator has set CSP (Content Security Policy) permissions for https://marketplace-cdn.atlassian.com and therefore plugin details didn't work correctly for already installed plugins.
For new plugins this problem didn't occur.

[Benjamin]

Hi @Paweł Mroczek 

Ah, so The culprit turn out to be an external issue with the network. Thanks for sharing. Were you able to get an exception from your network administrator?