Confluence https based, no access to the atlassian marketplace

[Reinhard Piltz]

After updating my https based Confluence to version 6, no access to the atlassian marketplace.
Proxy and firewall settings have not been changed.
Before the update, the access worked with https.
What is the ultimate setting? 

Collaborative Editing works with https.

[Rob Woodgate]

Hi Reinhard,

If you mean that the Universal Plugin Manager can't connect to the Marketplace, try going through Atlassian's troubleshooting suggestions.

[Reinhard Piltz]

Hi Rob,

Yes, I mean the Universal Plugin Manager.
According to Atlassian's troubleshooting suggestions, I've tried everything. Without success.

If https is switched off, the access to the marketplace also works.

It is an https setting. Only what?

[Rob Woodgate]

Hi Reinhard,

Based on the comments in the troubleshooting article, a lot of people have had a missing certificate.  Try the instructions on this page, see if that helps.

That article also links to this answer, which contains further options.

The following comments on the troubleshooting article might also help:

• https://confluence.atlassian.com/display/UPM/Problems+Connecting+to+the+Atlassian+Marketplace?focusedCommentId=296092577#comment-296092577
• https://confluence.atlassian.com/display/UPM/Problems+Connecting+to+the+Atlassian+Marketplace?focusedCommentId=302809611#comment-302809611
• https://confluence.atlassian.com/display/UPM/Problems+Connecting+to+the+Atlassian+Marketplace?focusedCommentId=300815284#comment-300815284
• https://confluence.atlassian.com/display/UPM/Problems+Connecting+to+the+Atlassian+Marketplace?focusedCommentId=306350799#comment-306350799

[Reinhard Piltz]

Hi Rob,
Found the problem.
Incorrect entry in the Confluence Windows service.

The entry
-Djavax.net.ssl.trustStore = $ {com.sun.aas.instanceRoot} / path / ks-name
 pointed to the private keyfile.
It must be right:
-Djavax.net.ssl.keyStore = $ {com.sun.aas.instanceRoot} / path / ts-name

 Thanks for your help

[Rob Woodgate]