If you see an error box on the upgrade tab containing the message java.net.ConnectException: Connection refused: connect, your host application server may be having trouble contacting http://plugins.atlassian.com. This may be a problem with your application's proxy settings.

Note: the Universal Plugin Manager will access and use the proxy settings of the host application. See documentation for :

as well as UPM-693

  • ラベルなし

2 Comments

  1. Michael Regelin

    Oct 13, 2010

    Hi everyone,

    I'm really surprise to read this page.

    We may not be the only one in this situation, but all our servers http/https ports are blocked to receive from outside our organistion.

    This mean that we cant use the new plugin manager because it takes so long time to wait for an error and I keep getting those "ConnectException".

    By the past, wh had the choice of going totally offline by not using the repository....
    Is there a workaround for those enterprise that dont let there servers not communicate with internet ???

    1. Michael Regelin

      Oct 13, 2010

      hello again,

      the problem may be a little more specific.

      Our attention spotted the fact that we hadnt configured a proxy for the launch of the JVM. And thus, when loading the universal plugin manager, it takes hours and hours to load and finishing by throwing  an error message.

      By applying a -Dpac.baseurl=http://localhost/invalidurl, i'm still unable to connect to the plugin attlassian site but the error is immediate.

      I can after easily upload new plugin....

      Hope that helps...