Skip to end of metadata
Go to start of metadata

Universal Plugin Manager 1.6

The Universal Plugin Manager (UPM) provides you with a powerful and user-friendly interface to manage your plugins. The Universal Plugin Manager itself is a plugin, which contains a number of modules that are implementations of the Atlassian REST plugin module type. It allows you to perform common plugin tasks, such as:
  • Enabling/disabling plugins and their plugin modules.
  • Installing new plugins.
  • Configuring advanced plugin options.
  • Finding out-of-date plugins and updating them.
  • Checking the compatibility of your installed plugins against newer versions of the application.

The Universal Plugin Manager also interfaces with the Atlassian Plugin Exchange, so you can browse the wide range of plugins available for your application from within your application. You can install any of these plugins with a single click, or upload your own plugins using the Universal Plugin Manager as well.

Read more about the Universal Plugin Manager in the topics linked below:

  • No labels


  1. Anonymous

    A useful comment here could be which sites this plugins tries to reach so i can allow the internal iptables protecting our test env to reach the internet sites it needs. Does such a list exist?

  2. Please also include upgrade guide for this plugin. I migrated from 3.4.2 to 3.5 but the UPM is still running at 1.2.4. Can't seem to find anyway to upgrade it to 1.3.1. Help please. Thanks.

    1. Anonymous

      I have the exact same problem.  I'm working with support now.  When I upload the 1.3.1 jar file, it says I need to restart Confluence.  So I do, and it STILL says I need to restart Confluence...

      1. Anonymous

        Can you please include the link to your support ticket? Thanks.

      2. Unfortunately it appears there is a bug in the UPM that after the upgrade occurs confluence to think the UPM hasn't been upgraded on a restart. Clicking the x will clear the message and tell you that the upgrade was aborted, however, if you check and confirm with a restart, it in fact was upgraded to 1.4.

        Thus it appears this is just a bug in the way the UPM detects if it was upgraded or not.

Write a comment…