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

Error: x509: certificate signed by unknown authority #97

Closed
bateller opened this issue Aug 10, 2016 · 3 comments
Closed

Error: x509: certificate signed by unknown authority #97

bateller opened this issue Aug 10, 2016 · 3 comments

Comments

@bateller
Copy link

bateller commented Aug 10, 2016

Tried to run goofys from command line and had this issue. Ideas?

# ./bin/goofys -f --region us-east-1 bucket-test /mnt/bucket-test/
2016/08/10 16:39:02.923064 s3.ERROR code=RequestError msg=send request failed, err=Head https://s3.amazonaws.com/bucket-test: x509: certificate signed by unknown authority

2016/08/10 16:39:03.259353 s3.INFO Unable to detect bucket region, staying at 'us-east-1'
2016/08/10 16:39:03.259374 s3.INFO Falling back to v2 signer
2016/08/10 16:39:03.574995 s3.ERROR code=RequestError msg=send request failed, err=Head https://s3.amazonaws.com/bucket-test: x509: certificate signed by unknown authority

2016/08/10 16:39:03.575021 main.ERROR Unable to access 'bucket-test': RequestError: send request failed
caused by: Head https://s3.amazonaws.com/bucket-test: x509: certificate signed by unknown authority
2016/08/10 16:39:03.575034 main.FATAL Mounting file system: Mount: initialization failed

Used yum to install golang:

Package golang-1.5.1-0.el6.x86_64

CentOS 6.x:

 # uname -a
Linux server.example.com 2.6.32-642.3.1.el6.x86_64 #1 SMP Tue Jul 12 18:30:56 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
@kahing
Copy link
Owner

kahing commented Aug 12, 2016

Is the bucket name actually bucket-test? I correctly got a 403 when I tried to use goofys to access that bucket and didn't get a certificate problem. Do you have other proxies between you and S3?

@bateller
Copy link
Author

No its a different bucket name. No proxies. EC2 instance running CentOS 5.x AMI at AWS us-east-1

@kahing
Copy link
Owner

kahing commented Aug 18, 2016

I am not able to reproduce this problem with Centos 5.4 x6_64 HVM (ami-0053dd30). What happens if you do something like:

curl -I https://s3.amazonaws.com/bucket-test

@kahing kahing closed this as completed Oct 1, 2016
kahing pushed a commit that referenced this issue Aug 16, 2021
Currently, after committing a blob for azure, we continue renewing lease. This PR fixes this behavior.
* add logs
* more logs
* fix break
* clean up logs
* just return
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants