Universal Plugin Manager Crashes when Numbered Headings Plugin is Installed

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

The following exception is shown in the logs when using the Universal Plugin Manager (UPM):

1 2 3 4 5 6 com.atlassian.plugins.PacException at com.atlassian.plugins.client.service.AbstractRestServiceClient.getEntityFromResponse(AbstractRestServiceClient.java:163) at com.atlassian.plugins.client.service.plugin.PluginVersionServiceClientImpl.getCompatibilityStatus(PluginVersionServiceClientImpl.java:176) at com.atlassian.upm.pac.PacClientImpl.getProductUpgradePluginCompatibility(PacClientImpl.java:91) at com.atlassian.upm.rest.resources.ProductUpgradePluginCompatibilityResource.get(ProductUpgradePluginCompatibilityResource.java:42) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

The following error is shown after doing an upgrade check in UPM:

1 An error occurred while connecting to the Atlassian Plugin Exchange. For more information about this problem, please refer to the [UPM documentation|http://confluence.atlassian.com/display/UPM/Problems+Connecting+to+the+Atlassian+Plugin+Exchange].
(Auto-migrated image: description temporarily unavailable)

Cause

This problem happens when the Numbered Headings Plugin is installed in Confluence and the UPM does an upgrade check. This issue is tracked by CONF-20511.

Resolution

Disable the Numbered Headings plugin when you want to use the Check feature in UPM, you can enable it again after making the check. If you're still getting the same error after disabling the plugin you may need to uninstall it temporarily.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.