Publishing to S3 Fails/not working.

[deevannaveed]

• Electron-Builder Version: 24.4.0

• Node Version: 14.18.3

• Electron Version: 16.0.7
• Electron Type (current, beta, nightly): Previous version

• Target: MacOS

When I add the publish key with below config in the electron-builder config it shows an error! I am not sure what am I doing wrong.
I tested the bucket and S3 credentials I can upload using the cli and I can access the objects publicly.
I tested on Windows and it works fine, the only problem is on MacOS.

  publish: {
    provider: 's3',
    bucket: 'my-bucket-here',
    region: 'us-west-2',
    path: '/',
    endpoint: 'https://s3.us-west-2.amazonaws.com',
  },

Error log:

  ⨯ RequestError: send request failed
caused by: Put "https://s3.us-west-2.amazonaws.com/my-bucket-here/my-app--1.0.0.dmg.blockmap": proxyconnect tcp: dial tcp :0: connect: can't assign requested address
github.com/develar/app-builder/pkg/publisher.upload
	/Volumes/data/Documents/app-builder/pkg/publisher/s3.go:169
github.com/develar/app-builder/pkg/publisher.ConfigurePublishToS3Command.func1
	/Volumes/data/Documents/app-builder/pkg/publisher/s3.go:57
github.com/alecthomas/kingpin.(*actionMixin).applyActions
	/Volumes/data/go/pkg/mod/github.com/alecthomas/kingpin@v2.2.6+incompatible/actions.go:28
github.com/alecthomas/kingpin.(*Application).applyActions
	/Volumes/data/go/pkg/mod/github.com/alecthomas/kingpin@v2.2.6+incompatible/app.go:557
github.com/alecthomas/kingpin.(*Application).execute
	/Volumes/data/go/pkg/mod/github.com/alecthomas/kingpin@v2.2.6+incompatible/app.go:390
github.com/alecthomas/kingpin.(*Application).Parse
	/Volumes/data/go/pkg/mod/github.com/alecthomas/kingpin@v2.2.6+incompatible/app.go:222
main.main
	/Volumes/data/Documents/app-builder/main.go:90
runtime.main
	/usr/local/Cellar/go/1.17/libexec/src/runtime/proc.go:255
runtime.goexit
	/usr/local/Cellar/go/1.17/libexec/src/runtime/asm_amd64.s:1581

[mmaietta]

Sorry, that's a Go-specific error being thrown in a upstream dependency develar/app-builder. Since it's specific to your mac environment, I'd recommend checking any active networking app/services and make sure your terminal (?) has the correct permissions set?