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

Fatal Error: no such host #30

Closed
Fluffy9 opened this issue Jun 8, 2018 · 2 comments
Closed

Fatal Error: no such host #30

Fluffy9 opened this issue Jun 8, 2018 · 2 comments

Comments

@Fluffy9
Copy link

Fluffy9 commented Jun 8, 2018

c:\Users\My\Path\Hugo\Sites\HugoWebsite>c:/Users/My/Path/s3deploy/s3deploy.exe -bucket sub.mybucket.com -region us-west
s3deploy 2.0.2, commit cc7116a, built at 2018-04-24T20:31:38Z

Total in 0.37 seconds
error: RequestError: send request failed
caused by: Get https://s3.us-west.amazonaws.com/sub.mybucket.com: dial tcp: lookup s3.us-west.amazonaws.com: no such host

@Jos512
Copy link

Jos512 commented Jun 9, 2018

Hm, that's an odd error. Sorry to ask, but did you double-check your settings? Your code snippet uses us-west, but that's not a valid S3 region from what I understand.

us-west-1 is used for California buckets, us-west-2 for Oregon. But I couldn't find what area us-west is.


Edit: I get the same error message when I use a wrong region:

> s3deploy -bucket eu.example.com -region us-west
Total in 0.32 seconds
error: RequestError: send request failed
caused by: Get https://s3.us-west.amazonaws.com/eu.example.com: dial tcp: lookup s3.us-west.amazonaws.com: no such host

@Fluffy9
Copy link
Author

Fluffy9 commented Jun 10, 2018

Thanks, that was exactly the issue. Sorry!

@Fluffy9 Fluffy9 closed this as completed Jun 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants