Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure retrieving auto configuration script #10694

Closed
cyberduck opened this issue May 3, 2019 · 6 comments
Closed

Failure retrieving auto configuration script #10694

cyberduck opened this issue May 3, 2019 · 6 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented May 3, 2019

d59283d created the issue

Upon fresh install on MacOS 10.14.4 with homebrew "duck --list ..." (and other options) throws following error, before printing correct output:

2019-05-03 15:43:51.135 duck[2689:92359] Failure retrieving auto configuration script from http://wpad/wpad.dat: Error Domain=NSCocoaErrorDomain Code=260 "The file “wpad.dat” couldn’t be opened because there is no such file." UserInfo={NSURL=http://wpad/wpad.dat, NSUnderlyingError=0x7fec67dd0100 {Error Domain=NSURLErrorDomain Code=-1003 "A server with the specified hostname could not be found." UserInfo={NSUnderlyingError=0x7fec6b01ee80 {Error Domain=kCFErrorDomainCFNetwork Code=-1003 "A server with the specified hostname could not be found." UserInfo={NSErrorFailingURLStringKey=http://wpad/wpad.dat, NSErrorFailingURLKey=http://wpad/wpad.dat, _kCFStreamErrorCodeKey=8, _kCFStreamErrorDomainKey=12, NSLocalizedDescription=A server with the specified hostname could not be found.}}, NSErrorFailingURLStringKey=http://wpad/wpad.dat, NSErrorFailingURLKey=http://wpad/wpad.dat, _kCFStreamErrorDomainKey=12, _kCFStreamErrorCodeKey=8, NSLocalizedDescription=A server with the specified hostname could not be found.

Trying to connect to S3 bucket fails entirely and additionally throws following error:

Connection failed. DNS lookup for my-bucket failed. DNS is the network service that translates a server name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing access to the network.

Any idea what's causing this?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 3, 2019

@dkocher commented

Please check your proxy settings in System Preferences → Network.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 3, 2019

d59283d commented

Not using any proxy, only "Auto Proxy Discovery" ticked.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 3, 2019

@dkocher commented

Replying to [comment:4 julianhinz]:

Not using any proxy, only "Auto Proxy Discovery" ticked.
Please uncheck.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 3, 2019

d59283d commented

Replying to [comment:5 dkocher]:

Replying to [comment:4 julianhinz]:

Not using any proxy, only "Auto Proxy Discovery" ticked.
Please uncheck.

Great, first part of the issue resolved. Second part persists though, I guess it may not be directly related. What could cause this?

Connection failed. DNS lookup for my-bucket failed. DNS is the network service that translates a server name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing access to the network.

Only for S3 (for me at least), Dropbox and OneDrive not showing this.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 4, 2019

d59283d commented

One more thing: None of the errors occur when using Cyberduck, only when using the CLI.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 30, 2019

@dkocher commented

Please refer to our documentation on URIs. You should use duck --list s3:/mybucket/ when connecting to Amazon S3.

Loading

@cyberduck cyberduck closed this May 30, 2019
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant