User on networks with proxy face ECONNREFUSED error when trying to edit via Atlassian Companion

Issue Summary

Customers are no longer able to edit and upload new versions of attachments using Atlassian companion app on a network with proxy setup. The file upload step to api.media.atlassian.com fails with ECONNREFUSED. This is consistent with the application attempting a direct connection to api.media.atlassian.com instead of using the network proxy.

Steps to Reproduce

1. Users login to Atlassian Account on a network that has proxy
2. Users go to any Confluence page and attach a Atlassian Companion file like Excel , Word or Wordpad RTF format files
3. They log out then relogin and try to edit this file

Expected Results

The Atlassian companion save the edited file when the file is saved on local desktop

Actual Results

The file keeps loading and is never saved. The below exception is thrown in the companion log file:

.....
{"errno":"ECONNREFUSED","code":"ECONNREFUSED","syscall":"connect","address":"xx.xx.xx.xx","port":xxx},"node":"v12.0.0"},"message":"Error: connect ECONNREFUSED xx.xx.xx.xx:xxx","exception":[{"type":"Error","value":"connect ECONNREFUSED xx.xx.xx.xx:xxx","stacktrace":{"frames":[{"filename":"net.js","lineno":1061,"colno":14,"function":"TCPConnectWrap.afterConnect [as oncomplete]","in_app":false,"module":"net"}]}}],"user":{}
...

Workaround

On the impacted network - there is no workaround. But using any other network seems to help customer just fine.

Option 1
Allow requests to https://s3-us-west-1.amazonaws.com/asap-public-key-repo.us-west-1.uswest.atl-inf.io and https://s3.amazonaws.com/asap-public-key-repo.us-east-1.useast.atl-inf.io to bypass the proxy.

Option 2
The user can downgrade to Companion 0.6.2 by installing with the MSI (which does not auto update), download here