starred/s3fs-fuse
1
0
Fork 0
mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 05:16:00 +03:00
Code Issues 305 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #706] Unable to mount S3 in Asia Pacific(Mumbai) - InvalidRequest #398

New issue
Closed
opened 2026-03-04 01:45:10 +03:00 by kerem · 3 comments
kerem commented 2026-03-04 01:45:10 +03:00
Owner
Copy link

Originally created by @socialglass on GitHub (Jan 11, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/706

Additional Information

Version of s3fs being used (s3fs --version)

1.83(commit:e1dafe7)

Version of fuse being used (pkg-config --modversion fuse)

2.9.4

System information (uname -r)

4.4.44-39.55.amzn1.x86_64

Distro (cat /etc/issue)

Kernel \r on an \m

s3fs command line used (if applicable)

sudo s3fs yoroshare /mnt -o passwd_file=/home/ec2-user/.passwd-s3fs -d -d -f -o f2 -o curldbg

Details about issue

When I try to mount my S3 bucket (in Asia Pacific - Mumbai), I get these logs and don't see the mount -

Also, checked that my bucket indeed shows as in Asia Pacific (Mumbai).

[CRT] s3fs.cpp:set_s3fs_log_level(271): change debug level from [CRT] to [INF]
[CRT] s3fs.cpp:set_s3fs_log_level(271): change debug level from [INF] to [DBG]
[INF] s3fs.cpp:set_mountpoint_attribute(4206): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755)
FUSE library version: 2.9.4
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
INIT: 7.23
flags=0x0003fffb
max_readahead=0x00020000
[INF] s3fs.cpp:s3fs_init(3371): init v1.83(commit:e1dafe7) with OpenSSL
[INF] s3fs.cpp:s3fs_check_service(3747): check services.
[INF] curl.cpp:CheckBucket(3068): check a bucket.
[DBG] curl.cpp:GetHandler(285): Get handler from pool: 31
[INF] curl.cpp:prepare_url(4253): URL is https://s3.amazonaws.com/yoroshare/
[INF] curl.cpp:prepare_url(4285): URL changed is https://yoroshare.s3.amazonaws.com/
[INF] curl.cpp:insertV4Headers(2400): computing signature [GET] [/] [] []
[INF] curl.cpp:url_to_host(101): url is https://s3.amazonaws.com
[DBG] curl.cpp:RequestPerform(2034): connecting to URL https://yoroshare.s3.amazonaws.com/

  • Trying 52.219.64.24...
  • Connected to yoroshare.s3.amazonaws.com (52.219.64.24) port 443 (#0)
  • Initializing NSS with certpath: sql:/etc/pki/nssdb
  • CAfile: /etc/pki/tls/certs/ca-bundle.crt
    CApath: none
  • ALPN/NPN, server did not agree to a protocol
  • SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  • Server certificate:
  • subject: CN=*.s3.amazonaws.com,O=Amazon.com Inc.,L=Seattle,ST=Washington,C=US
  • start date: Sep 22 00:00:00 2017 GMT
  • expire date: Jan 03 12:00:00 2019 GMT
  • common name: *.s3.amazonaws.com
  • issuer: CN=DigiCert Baltimore CA-2 G2,OU=www.digicert.com,O=DigiCert Inc,C=US

GET / HTTP/1.1
host: yoroshare.s3.amazonaws.com
User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL)
Accept: /
Authorization: AWS4-HMAC-SHA256 Credential=AKIAJJM62B4GZ7CVJ4XA/20180111/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=58fb3b0f35b0a6fca92604b109e09b08c0f8d240221848f22629488d1b44c44e
x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date: 20180111T044404Z

< HTTP/1.1 400 Bad Request
< x-amz-bucket-region: ap-south-1
< x-amz-request-id: B2096BDB4E9EB66D
< x-amz-id-2: WTfophBquqO+/3ckxKWewBuaoSWic6LGi8XqnWf6oj+R7I0DxoKcaUJJXSgI+TQw48E5dJPiQpc=
< Content-Type: application/xml
< Transfer-Encoding: chunked
< Date: Thu, 11 Jan 2018 04:44:04 GMT
< Connection: close
< Server: AmazonS3
<

  • Closing connection 0
    [INF] curl.cpp:RequestPerform(2063): HTTP response code 400 was returned, returning EIO.
    [DBG] curl.cpp:RequestPerform(2064): Body Text:
    AuthorizationHeaderMalformedThe authorization header is malformed; the region 'us-east-1' is wrong; expecting 'ap-south-1'ap-south-1B2096BDB4E9EB66DWTfophBquqO+/3ckxKWewBuaoSWic6LGi8XqnWf6oj+R7I0DxoKcaUJJXSgI+TQw48E5dJPiQpc=
    [ERR] curl.cpp:CheckBucket(3096): Check bucket failed, S3 response:
    AuthorizationHeaderMalformedThe authorization header is malformed; the region 'us-east-1' is wrong; expecting 'ap-south-1'ap-south-1B2096BDB4E9EB66DWTfophBquqO+/3ckxKWewBuaoSWic6LGi8XqnWf6oj+R7I0DxoKcaUJJXSgI+TQw48E5dJPiQpc=
    [CRT] s3fs.cpp:s3fs_check_service(3768): Could not connect wrong region us-east-1, so retry to connect region ap-south-1.
    [DBG] curl.cpp:ReturnHandler(308): Return handler to pool: 31
    [INF] curl.cpp:CheckBucket(3068): check a bucket.
    [DBG] curl.cpp:GetHandler(285): Get handler from pool: 31
    [INF] curl.cpp:prepare_url(4253): URL is https://s3-ap-south-1.amazonaws.com/yoroshare/
    [INF] curl.cpp:prepare_url(4285): URL changed is https://yoroshare.s3-ap-south-1.amazonaws.com/
    [INF] curl.cpp:insertV4Headers(2400): computing signature [GET] [/] [] []
    [INF] curl.cpp:url_to_host(101): url is https://s3-ap-south-1.amazonaws.com
    [DBG] curl.cpp:RequestPerform(2034): connecting to URL https://yoroshare.s3-ap-south-1.amazonaws.com/
  • Trying 52.219.66.34...
  • Connected to yoroshare.s3-ap-south-1.amazonaws.com (52.219.66.34) port 443 (#1)
  • CAfile: /etc/pki/tls/certs/ca-bundle.crt
    CApath: none
  • ALPN/NPN, server did not agree to a protocol
  • SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  • Server certificate:
  • subject: CN=*.s3.ap-south-1.amazonaws.com,O=Amazon.com Inc.,L=Seattle,ST=Washington,C=US
  • start date: Jul 12 00:00:00 2017 GMT
  • expire date: May 02 12:00:00 2018 GMT
  • common name: *.s3.ap-south-1.amazonaws.com
  • issuer: CN=DigiCert Baltimore CA-2 G2,OU=www.digicert.com,O=DigiCert Inc,C=US

GET / HTTP/1.1
host: yoroshare.s3-ap-south-1.amazonaws.com
User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL)
Accept: /
Authorization: AWS4-HMAC-SHA256 Credential=AKIAJJM62B4GZ7CVJ4XA/20180111/ap-south-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=39ac64070414a0423c1702f79647c23dffa6174a7117499f799301770a03c9e2
x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date: 20180111T044404Z

< HTTP/1.1 403 Forbidden
< x-amz-bucket-region: ap-south-1
< x-amz-request-id: 292E01700CFDAE30
< x-amz-id-2: WN2zg/KFJvYw8M6dnHjDkvkwMnw2QpCDoVPFjdwIclBfBY/ePlAYm6JRqgWD3ePlkXRPbHiejf4=
< Content-Type: application/xml
< Transfer-Encoding: chunked
< Date: Thu, 11 Jan 2018 04:44:04 GMT
< Server: AmazonS3
<

  • Connection #1 to host yoroshare.s3-ap-south-1.amazonaws.com left intact
    [INF] curl.cpp:RequestPerform(2068): HTTP response code 403 was returned, returning EPERM
    [DBG] curl.cpp:RequestPerform(2069): Body Text:
    SignatureDoesNotMatchThe request signature we calculated does not match the signature you provided. Check your key and signing method.AKIAJJM62B4GZ7CVJ4XAAWS4-HMAC-SHA256
    20180111T044404Z
    20180111/ap-south-1/s3/aws4_request
    c3c0fbb82263d0502010a3b7af9691b388df934cfb6391dc31f47e8142a942d839ac64070414a0423c1702f79647c23dffa6174a7117499f799301770a03c9e241 57 53 34 2d 48 4d 41 43 2d 53 48 41 32 35 36 0a 32 30 31 38 30 31 31 31 54 30 34 34 34 30 34 5a 0a 32 30 31 38 30 31 31 31 2f 61 70 2d 73 6f 75 74 68 2d 31 2f 73 33 2f 61 77 73 34 5f 72 65 71 75 65 73 74 0a 63 33 63 30 66 62 62 38 32 32 36 33 64 30 35 30 32 30 31 30 61 33 62 37 61 66 39 36 39 31 62 33 38 38 64 66 39 33 34 63 66 62 36 33 39 31 64 63 33 31 66 34 37 65 38 31 34 32 61 39 34 32 64 38GET
    /

host:yoroshare.s3-ap-south-1.amazonaws.com
x-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date:20180111T044404Z

host;x-amz-content-sha256;x-amz-date
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b85547 45 54 0a 2f 0a 0a 68 6f 73 74 3a 79 6f 72 6f 73 68 61 72 65 2e 73 33 2d 61 70 2d 73 6f 75 74 68 2d 31 2e 61 6d 61 7a 6f 6e 61 77 73 2e 63 6f 6d 0a 78 2d 61 6d 7a 2d 63 6f 6e 74 65 6e 74 2d 73 68 61 32 35 36 3a 65 33 62 30 63 34 34 32 39 38 66 63 31 63 31 34 39 61 66 62 66 34 63 38 39 39 36 66 62 39 32 34 32 37 61 65 34 31 65 34 36 34 39 62 39 33 34 63 61 34 39 35 39 39 31 62 37 38 35 32 62 38 35 35 0a 78 2d 61 6d 7a 2d 64 61 74 65 3a 32 30 31 38 30 31 31 31 54 30 34 34 34 30 34 5a 0a 0a 68 6f 73 74 3b 78 2d 61 6d 7a 2d 63 6f 6e 74 65 6e 74 2d 73 68 61 32 35 36 3b 78 2d 61 6d 7a 2d 64 61 74 65 0a 65 33 62 30 63 34 34 32 39 38 66 63 31 63 31 34 39 61 66 62 66 34 63 38 39 39 36 66 62 39 32 34 32 37 61 65 34 31 65 34 36 34 39 62 39 33 34 63 61 34 39 35 39 39 31 62 37 38 35 32 62 38 35 35292E01700CFDAE30WN2zg/KFJvYw8M6dnHjDkvkwMnw2QpCDoVPFjdwIclBfBY/ePlAYm6JRqgWD3ePlkXRPbHiejf4=
[ERR] curl.cpp:CheckBucket(3096): Check bucket failed, S3 response:
SignatureDoesNotMatchThe request signature we calculated does not match the signature you provided. Check your key and signing method.AKIAJJM62B4GZ7CVJ4XAAWS4-HMAC-SHA256
20180111T044404Z
20180111/ap-south-1/s3/aws4_request
c3c0fbb82263d0502010a3b7af9691b388df934cfb6391dc31f47e8142a942d839ac64070414a0423c1702f79647c23dffa6174a7117499f799301770a03c9e241 57 53 34 2d 48 4d 41 43 2d 53 48 41 32 35 36 0a 32 30 31 38 30 31 31 31 54 30 34 34 34 30 34 5a 0a 32 30 31 38 30 31 31 31 2f 61 70 2d 73 6f 75 74 68 2d 31 2f 73 33 2f 61 77 73 34 5f 72 65 71 75 65 73 74 0a 63 33 63 30 66 62 62 38 32 32 36 33 64 30 35 30 32 30 31 30 61 33 62 37 61 66 39 36 39 31 62 33 38 38 64 66 39 33 34 63 66 62 36 33 39 31 64 63 33 31 66 34 37 65 38 31 34 32 61 39 34 32 64 38GET
/

host:yoroshare.s3-ap-south-1.amazonaws.com
x-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date:20180111T044404Z

host;x-amz-content-sha256;x-amz-date
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b85547 45 54 0a 2f 0a 0a 68 6f 73 74 3a 79 6f 72 6f 73 68 61 72 65 2e 73 33 2d 61 70 2d 73 6f 75 74 68 2d 31 2e 61 6d 61 7a 6f 6e 61 77 73 2e 63 6f 6d 0a 78 2d 61 6d 7a 2d 63 6f 6e 74 65 6e 74 2d 73 68 61 32 35 36 3a 65 33 62 30 63 34 34 32 39 38 66 63 31 63 31 34 39 61 66 62 66 34 63 38 39 39 36 66 62 39 32 34 32 37 61 65 34 31 65 34 36 34 39 62 39 33 34 63 61 34 39 35 39 39 31 62 37 38 35 32 62 38 35 35 0a 78 2d 61 6d 7a 2d 64 61 74 65 3a 32 30 31 38 30 31 31 31 54 30 34 34 34 30 34 5a 0a 0a 68 6f 73 74 3b 78 2d 61 6d 7a 2d 63 6f 6e 74 65 6e 74 2d 73 68 61 32 35 36 3b 78 2d 61 6d 7a 2d 64 61 74 65 0a 65 33 62 30 63 34 34 32 39 38 66 63 31 63 31 34 39 61 66 62 66 34 63 38 39 39 36 66 62 39 32 34 32 37 61 65 34 31 65 34 36 34 39 62 39 33 34 63 61 34 39 35 39 39 31 62 37 38 35 32 62 38 35 35292E01700CFDAE30WN2zg/KFJvYw8M6dnHjDkvkwMnw2QpCDoVPFjdwIclBfBY/ePlAYm6JRqgWD3ePlkXRPbHiejf4=
[WAN] s3fs.cpp:s3fs_check_service(3788): Could not connect, so retry to connect by signature version 2.
[DBG] curl.cpp:ReturnHandler(308): Return handler to pool: 31
[INF] curl.cpp:CheckBucket(3068): check a bucket.
[DBG] curl.cpp:GetHandler(285): Get handler from pool: 31
[INF] curl.cpp:prepare_url(4253): URL is https://s3-ap-south-1.amazonaws.com/yoroshare/
[INF] curl.cpp:prepare_url(4285): URL changed is https://yoroshare.s3-ap-south-1.amazonaws.com/
[DBG] curl.cpp:RequestPerform(2034): connecting to URL https://yoroshare.s3-ap-south-1.amazonaws.com/

  • Found bundle for host yoroshare.s3-ap-south-1.amazonaws.com: 0x7f03a415df00 [can pipeline]
  • Re-using existing connection! (#1) with host yoroshare.s3-ap-south-1.amazonaws.com
  • Connected to yoroshare.s3-ap-south-1.amazonaws.com (52.219.66.34) port 443 (#1)

GET / HTTP/1.1
Host: yoroshare.s3-ap-south-1.amazonaws.com
User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL)
Accept: /
Authorization: AWS AKIAJJM62B4GZ7CVJ4XA:fHFybmyA0wPorD2ewhUp1DFcOQw=
Date: Thu, 11 Jan 2018 04:44:04 GMT

< HTTP/1.1 400 Bad Request
< x-amz-bucket-region: ap-south-1
< x-amz-request-id: B5E1586467BC6E24
< x-amz-id-2: QOlB1VBElGy6t9m7DhCEoD2Nbpg9aFP78UK7m6ysIluLi86CxxNcfyuWrhZhfGbG5psPwYq3PfU=
< x-amz-region: ap-south-1
< Content-Type: application/xml
< Transfer-Encoding: chunked
< Date: Thu, 11 Jan 2018 04:44:04 GMT
< Connection: close
< Server: AmazonS3
<

  • Closing connection 1
    [INF] curl.cpp:RequestPerform(2063): HTTP response code 400 was returned, returning EIO.
    [DBG] curl.cpp:RequestPerform(2064): Body Text:
    InvalidRequestThe authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.B5E1586467BC6E24QOlB1VBElGy6t9m7DhCEoD2Nbpg9aFP78UK7m6ysIluLi86CxxNcfyuWrhZhfGbG5psPwYq3PfU=
    [ERR] curl.cpp:CheckBucket(3096): Check bucket failed, S3 response:
    InvalidRequestThe authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.B5E1586467BC6E24QOlB1VBElGy6t9m7DhCEoD2Nbpg9aFP78UK7m6ysIluLi86CxxNcfyuWrhZhfGbG5psPwYq3PfU=
    [CRT] s3fs.cpp:s3fs_check_service(3800): Bad Request(host=https://s3-ap-south-1.amazonaws.com) - result of checking service.
    [DBG] curl.cpp:ReturnHandler(308): Return handler to pool: 31
    [ERR] s3fs.cpp:s3fs_exit_fuseloop(3361): Exiting FUSE event loop due to errors

    INIT: 7.19
    flags=0x00000011
    max_readahead=0x00020000
    max_write=0x00020000
    max_background=0
    congestion_threshold=0
    unique: 1, success, outsize: 40
    [INF] s3fs.cpp:s3fs_destroy(3434): destroy
    [WAN] s3fs.cpp:s3fs_destroy(3438): Could not release curl library.

Originally created by @socialglass on GitHub (Jan 11, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/706 ### Additional Information #### Version of s3fs being used (s3fs --version) 1.83(commit:e1dafe7) #### Version of fuse being used (pkg-config --modversion fuse) 2.9.4 #### System information (uname -r) 4.4.44-39.55.amzn1.x86_64 #### Distro (cat /etc/issue) Kernel \r on an \m #### s3fs command line used (if applicable) ``` sudo s3fs yoroshare /mnt -o passwd_file=/home/ec2-user/.passwd-s3fs -d -d -f -o f2 -o curldbg ``` ### Details about issue When I try to mount my S3 bucket (in Asia Pacific - Mumbai), I get these logs and don't see the mount - Also, checked that my bucket indeed shows as in Asia Pacific (Mumbai). > [CRT] s3fs.cpp:set_s3fs_log_level(271): change debug level from [CRT] to [INF] > [CRT] s3fs.cpp:set_s3fs_log_level(271): change debug level from [INF] to [DBG] > [INF] s3fs.cpp:set_mountpoint_attribute(4206): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755) > FUSE library version: 2.9.4 > nullpath_ok: 0 > nopath: 0 > utime_omit_ok: 0 > unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0 > INIT: 7.23 > flags=0x0003fffb > max_readahead=0x00020000 > [INF] s3fs.cpp:s3fs_init(3371): init v1.83(commit:e1dafe7) with OpenSSL > [INF] s3fs.cpp:s3fs_check_service(3747): check services. > [INF] curl.cpp:CheckBucket(3068): check a bucket. > [DBG] curl.cpp:GetHandler(285): Get handler from pool: 31 > [INF] curl.cpp:prepare_url(4253): URL is https://s3.amazonaws.com/yoroshare/ > [INF] curl.cpp:prepare_url(4285): URL changed is https://yoroshare.s3.amazonaws.com/ > [INF] curl.cpp:insertV4Headers(2400): computing signature [GET] [/] [] [] > [INF] curl.cpp:url_to_host(101): url is https://s3.amazonaws.com > [DBG] curl.cpp:RequestPerform(2034): connecting to URL https://yoroshare.s3.amazonaws.com/ > * Trying 52.219.64.24... > * Connected to yoroshare.s3.amazonaws.com (52.219.64.24) port 443 (#0) > * Initializing NSS with certpath: sql:/etc/pki/nssdb > * CAfile: /etc/pki/tls/certs/ca-bundle.crt > CApath: none > * ALPN/NPN, server did not agree to a protocol > * SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 > * Server certificate: > * subject: CN=*.s3.amazonaws.com,O=Amazon.com Inc.,L=Seattle,ST=Washington,C=US > * start date: Sep 22 00:00:00 2017 GMT > * expire date: Jan 03 12:00:00 2019 GMT > * common name: *.s3.amazonaws.com > * issuer: CN=DigiCert Baltimore CA-2 G2,OU=www.digicert.com,O=DigiCert Inc,C=US > > GET / HTTP/1.1 > host: yoroshare.s3.amazonaws.com > User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL) > Accept: */* > Authorization: AWS4-HMAC-SHA256 Credential=AKIAJJM62B4GZ7CVJ4XA/20180111/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=58fb3b0f35b0a6fca92604b109e09b08c0f8d240221848f22629488d1b44c44e > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 > x-amz-date: 20180111T044404Z > > < HTTP/1.1 400 Bad Request > < x-amz-bucket-region: ap-south-1 > < x-amz-request-id: B2096BDB4E9EB66D > < x-amz-id-2: WTfophBquqO+/3ckxKWewBuaoSWic6LGi8XqnWf6oj+R7I0DxoKcaUJJXSgI+TQw48E5dJPiQpc= > < Content-Type: application/xml > < Transfer-Encoding: chunked > < Date: Thu, 11 Jan 2018 04:44:04 GMT > < Connection: close > < Server: AmazonS3 > < > * Closing connection 0 > [INF] curl.cpp:RequestPerform(2063): HTTP response code 400 was returned, returning EIO. > [DBG] curl.cpp:RequestPerform(2064): Body Text: <?xml version="1.0" encoding="UTF-8"?> > <Error><Code>AuthorizationHeaderMalformed</Code><Message>The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'ap-south-1'</Message><Region>ap-south-1</Region><RequestId>B2096BDB4E9EB66D</RequestId><HostId>WTfophBquqO+/3ckxKWewBuaoSWic6LGi8XqnWf6oj+R7I0DxoKcaUJJXSgI+TQw48E5dJPiQpc=</HostId></Error> > [ERR] curl.cpp:CheckBucket(3096): Check bucket failed, S3 response: <?xml version="1.0" encoding="UTF-8"?> > <Error><Code>AuthorizationHeaderMalformed</Code><Message>The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'ap-south-1'</Message><Region>ap-south-1</Region><RequestId>B2096BDB4E9EB66D</RequestId><HostId>WTfophBquqO+/3ckxKWewBuaoSWic6LGi8XqnWf6oj+R7I0DxoKcaUJJXSgI+TQw48E5dJPiQpc=</HostId></Error> > [CRT] s3fs.cpp:s3fs_check_service(3768): Could not connect wrong region us-east-1, so retry to connect region ap-south-1. > [DBG] curl.cpp:ReturnHandler(308): Return handler to pool: 31 > [INF] curl.cpp:CheckBucket(3068): check a bucket. > [DBG] curl.cpp:GetHandler(285): Get handler from pool: 31 > [INF] curl.cpp:prepare_url(4253): URL is https://s3-ap-south-1.amazonaws.com/yoroshare/ > [INF] curl.cpp:prepare_url(4285): URL changed is https://yoroshare.s3-ap-south-1.amazonaws.com/ > [INF] curl.cpp:insertV4Headers(2400): computing signature [GET] [/] [] [] > [INF] curl.cpp:url_to_host(101): url is https://s3-ap-south-1.amazonaws.com > [DBG] curl.cpp:RequestPerform(2034): connecting to URL https://yoroshare.s3-ap-south-1.amazonaws.com/ > * Trying 52.219.66.34... > * Connected to yoroshare.s3-ap-south-1.amazonaws.com (52.219.66.34) port 443 (#1) > * CAfile: /etc/pki/tls/certs/ca-bundle.crt > CApath: none > * ALPN/NPN, server did not agree to a protocol > * SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 > * Server certificate: > * subject: CN=*.s3.ap-south-1.amazonaws.com,O=Amazon.com Inc.,L=Seattle,ST=Washington,C=US > * start date: Jul 12 00:00:00 2017 GMT > * expire date: May 02 12:00:00 2018 GMT > * common name: *.s3.ap-south-1.amazonaws.com > * issuer: CN=DigiCert Baltimore CA-2 G2,OU=www.digicert.com,O=DigiCert Inc,C=US > > GET / HTTP/1.1 > host: yoroshare.s3-ap-south-1.amazonaws.com > User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL) > Accept: */* > Authorization: AWS4-HMAC-SHA256 Credential=AKIAJJM62B4GZ7CVJ4XA/20180111/ap-south-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=39ac64070414a0423c1702f79647c23dffa6174a7117499f799301770a03c9e2 > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 > x-amz-date: 20180111T044404Z > > < HTTP/1.1 403 Forbidden > < x-amz-bucket-region: ap-south-1 > < x-amz-request-id: 292E01700CFDAE30 > < x-amz-id-2: WN2zg/KFJvYw8M6dnHjDkvkwMnw2QpCDoVPFjdwIclBfBY/ePlAYm6JRqgWD3ePlkXRPbHiejf4= > < Content-Type: application/xml > < Transfer-Encoding: chunked > < Date: Thu, 11 Jan 2018 04:44:04 GMT > < Server: AmazonS3 > < > * Connection #1 to host yoroshare.s3-ap-south-1.amazonaws.com left intact > [INF] curl.cpp:RequestPerform(2068): HTTP response code 403 was returned, returning EPERM > [DBG] curl.cpp:RequestPerform(2069): Body Text: <?xml version="1.0" encoding="UTF-8"?> > <Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><AWSAccessKeyId>AKIAJJM62B4GZ7CVJ4XA</AWSAccessKeyId><StringToSign>AWS4-HMAC-SHA256 > 20180111T044404Z > 20180111/ap-south-1/s3/aws4_request > c3c0fbb82263d0502010a3b7af9691b388df934cfb6391dc31f47e8142a942d8</StringToSign><SignatureProvided>39ac64070414a0423c1702f79647c23dffa6174a7117499f799301770a03c9e2</SignatureProvided><StringToSignBytes>41 57 53 34 2d 48 4d 41 43 2d 53 48 41 32 35 36 0a 32 30 31 38 30 31 31 31 54 30 34 34 34 30 34 5a 0a 32 30 31 38 30 31 31 31 2f 61 70 2d 73 6f 75 74 68 2d 31 2f 73 33 2f 61 77 73 34 5f 72 65 71 75 65 73 74 0a 63 33 63 30 66 62 62 38 32 32 36 33 64 30 35 30 32 30 31 30 61 33 62 37 61 66 39 36 39 31 62 33 38 38 64 66 39 33 34 63 66 62 36 33 39 31 64 63 33 31 66 34 37 65 38 31 34 32 61 39 34 32 64 38</StringToSignBytes><CanonicalRequest>GET > / > > host:yoroshare.s3-ap-south-1.amazonaws.com > x-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 > x-amz-date:20180111T044404Z > > host;x-amz-content-sha256;x-amz-date > e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855</CanonicalRequest><CanonicalRequestBytes>47 45 54 0a 2f 0a 0a 68 6f 73 74 3a 79 6f 72 6f 73 68 61 72 65 2e 73 33 2d 61 70 2d 73 6f 75 74 68 2d 31 2e 61 6d 61 7a 6f 6e 61 77 73 2e 63 6f 6d 0a 78 2d 61 6d 7a 2d 63 6f 6e 74 65 6e 74 2d 73 68 61 32 35 36 3a 65 33 62 30 63 34 34 32 39 38 66 63 31 63 31 34 39 61 66 62 66 34 63 38 39 39 36 66 62 39 32 34 32 37 61 65 34 31 65 34 36 34 39 62 39 33 34 63 61 34 39 35 39 39 31 62 37 38 35 32 62 38 35 35 0a 78 2d 61 6d 7a 2d 64 61 74 65 3a 32 30 31 38 30 31 31 31 54 30 34 34 34 30 34 5a 0a 0a 68 6f 73 74 3b 78 2d 61 6d 7a 2d 63 6f 6e 74 65 6e 74 2d 73 68 61 32 35 36 3b 78 2d 61 6d 7a 2d 64 61 74 65 0a 65 33 62 30 63 34 34 32 39 38 66 63 31 63 31 34 39 61 66 62 66 34 63 38 39 39 36 66 62 39 32 34 32 37 61 65 34 31 65 34 36 34 39 62 39 33 34 63 61 34 39 35 39 39 31 62 37 38 35 32 62 38 35 35</CanonicalRequestBytes><RequestId>292E01700CFDAE30</RequestId><HostId>WN2zg/KFJvYw8M6dnHjDkvkwMnw2QpCDoVPFjdwIclBfBY/ePlAYm6JRqgWD3ePlkXRPbHiejf4=</HostId></Error> > [ERR] curl.cpp:CheckBucket(3096): Check bucket failed, S3 response: <?xml version="1.0" encoding="UTF-8"?> > <Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><AWSAccessKeyId>AKIAJJM62B4GZ7CVJ4XA</AWSAccessKeyId><StringToSign>AWS4-HMAC-SHA256 > 20180111T044404Z > 20180111/ap-south-1/s3/aws4_request > c3c0fbb82263d0502010a3b7af9691b388df934cfb6391dc31f47e8142a942d8</StringToSign><SignatureProvided>39ac64070414a0423c1702f79647c23dffa6174a7117499f799301770a03c9e2</SignatureProvided><StringToSignBytes>41 57 53 34 2d 48 4d 41 43 2d 53 48 41 32 35 36 0a 32 30 31 38 30 31 31 31 54 30 34 34 34 30 34 5a 0a 32 30 31 38 30 31 31 31 2f 61 70 2d 73 6f 75 74 68 2d 31 2f 73 33 2f 61 77 73 34 5f 72 65 71 75 65 73 74 0a 63 33 63 30 66 62 62 38 32 32 36 33 64 30 35 30 32 30 31 30 61 33 62 37 61 66 39 36 39 31 62 33 38 38 64 66 39 33 34 63 66 62 36 33 39 31 64 63 33 31 66 34 37 65 38 31 34 32 61 39 34 32 64 38</StringToSignBytes><CanonicalRequest>GET > / > > host:yoroshare.s3-ap-south-1.amazonaws.com > x-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 > x-amz-date:20180111T044404Z > > host;x-amz-content-sha256;x-amz-date > e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855</CanonicalRequest><CanonicalRequestBytes>47 45 54 0a 2f 0a 0a 68 6f 73 74 3a 79 6f 72 6f 73 68 61 72 65 2e 73 33 2d 61 70 2d 73 6f 75 74 68 2d 31 2e 61 6d 61 7a 6f 6e 61 77 73 2e 63 6f 6d 0a 78 2d 61 6d 7a 2d 63 6f 6e 74 65 6e 74 2d 73 68 61 32 35 36 3a 65 33 62 30 63 34 34 32 39 38 66 63 31 63 31 34 39 61 66 62 66 34 63 38 39 39 36 66 62 39 32 34 32 37 61 65 34 31 65 34 36 34 39 62 39 33 34 63 61 34 39 35 39 39 31 62 37 38 35 32 62 38 35 35 0a 78 2d 61 6d 7a 2d 64 61 74 65 3a 32 30 31 38 30 31 31 31 54 30 34 34 34 30 34 5a 0a 0a 68 6f 73 74 3b 78 2d 61 6d 7a 2d 63 6f 6e 74 65 6e 74 2d 73 68 61 32 35 36 3b 78 2d 61 6d 7a 2d 64 61 74 65 0a 65 33 62 30 63 34 34 32 39 38 66 63 31 63 31 34 39 61 66 62 66 34 63 38 39 39 36 66 62 39 32 34 32 37 61 65 34 31 65 34 36 34 39 62 39 33 34 63 61 34 39 35 39 39 31 62 37 38 35 32 62 38 35 35</CanonicalRequestBytes><RequestId>292E01700CFDAE30</RequestId><HostId>WN2zg/KFJvYw8M6dnHjDkvkwMnw2QpCDoVPFjdwIclBfBY/ePlAYm6JRqgWD3ePlkXRPbHiejf4=</HostId></Error> > [WAN] s3fs.cpp:s3fs_check_service(3788): Could not connect, so retry to connect by signature version 2. > [DBG] curl.cpp:ReturnHandler(308): Return handler to pool: 31 > [INF] curl.cpp:CheckBucket(3068): check a bucket. > [DBG] curl.cpp:GetHandler(285): Get handler from pool: 31 > [INF] curl.cpp:prepare_url(4253): URL is https://s3-ap-south-1.amazonaws.com/yoroshare/ > [INF] curl.cpp:prepare_url(4285): URL changed is https://yoroshare.s3-ap-south-1.amazonaws.com/ > [DBG] curl.cpp:RequestPerform(2034): connecting to URL https://yoroshare.s3-ap-south-1.amazonaws.com/ > * Found bundle for host yoroshare.s3-ap-south-1.amazonaws.com: 0x7f03a415df00 [can pipeline] > * Re-using existing connection! (#1) with host yoroshare.s3-ap-south-1.amazonaws.com > * Connected to yoroshare.s3-ap-south-1.amazonaws.com (52.219.66.34) port 443 (#1) > > GET / HTTP/1.1 > Host: yoroshare.s3-ap-south-1.amazonaws.com > User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL) > Accept: */* > Authorization: AWS AKIAJJM62B4GZ7CVJ4XA:fHFybmyA0wPorD2ewhUp1DFcOQw= > Date: Thu, 11 Jan 2018 04:44:04 GMT > > < HTTP/1.1 400 Bad Request > < x-amz-bucket-region: ap-south-1 > < x-amz-request-id: B5E1586467BC6E24 > < x-amz-id-2: QOlB1VBElGy6t9m7DhCEoD2Nbpg9aFP78UK7m6ysIluLi86CxxNcfyuWrhZhfGbG5psPwYq3PfU= > < x-amz-region: ap-south-1 > < Content-Type: application/xml > < Transfer-Encoding: chunked > < Date: Thu, 11 Jan 2018 04:44:04 GMT > < Connection: close > < Server: AmazonS3 > < > * Closing connection 1 > [INF] curl.cpp:RequestPerform(2063): HTTP response code 400 was returned, returning EIO. > [DBG] curl.cpp:RequestPerform(2064): Body Text: <?xml version="1.0" encoding="UTF-8"?> > <Error><Code>InvalidRequest</Code><Message>The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.</Message><RequestId>B5E1586467BC6E24</RequestId><HostId>QOlB1VBElGy6t9m7DhCEoD2Nbpg9aFP78UK7m6ysIluLi86CxxNcfyuWrhZhfGbG5psPwYq3PfU=</HostId></Error> > [ERR] curl.cpp:CheckBucket(3096): Check bucket failed, S3 response: <?xml version="1.0" encoding="UTF-8"?> > <Error><Code>InvalidRequest</Code><Message>The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.</Message><RequestId>B5E1586467BC6E24</RequestId><HostId>QOlB1VBElGy6t9m7DhCEoD2Nbpg9aFP78UK7m6ysIluLi86CxxNcfyuWrhZhfGbG5psPwYq3PfU=</HostId></Error> > [CRT] s3fs.cpp:s3fs_check_service(3800): Bad Request(host=https://s3-ap-south-1.amazonaws.com) - result of checking service. > [DBG] curl.cpp:ReturnHandler(308): Return handler to pool: 31 > [ERR] s3fs.cpp:s3fs_exit_fuseloop(3361): Exiting FUSE event loop due to errors > > INIT: 7.19 > flags=0x00000011 > max_readahead=0x00020000 > max_write=0x00020000 > max_background=0 > congestion_threshold=0 > unique: 1, success, outsize: 40 > [INF] s3fs.cpp:s3fs_destroy(3434): destroy > [WAN] s3fs.cpp:s3fs_destroy(3438): Could not release curl library.
kerem closed this issue 2026-03-04 01:45:10 +03:00
kerem commented 2026-03-04 01:45:11 +03:00
Author
Owner
Copy link

@gaul commented on GitHub (Jan 11, 2018):

Does setting -o endpoint=ap-south-1 work around this issue? However, s3fs should auto-detect the region.

<!-- gh-comment-id:356833857 --> @gaul commented on GitHub (Jan 11, 2018): Does setting `-o endpoint=ap-south-1` work around this issue? However, s3fs should auto-detect the region.
kerem commented 2026-03-04 01:45:11 +03:00
Author
Owner
Copy link

@socialglass commented on GitHub (Jan 11, 2018):

That seems to resolve the region mismatch, but still getting an authorization error -

[ec2-user@ip mnt]$ sudo s3fs yoroshare1 /mnt -o passwd_file=/home/ec2-user/.passwd-s3fs -d -d -f -o f2 -o curldbg -o endpoint=ap-south-1
[CRT] s3fs.cpp:set_s3fs_log_level(271): change debug level from [CRT] to [INF]
[CRT] s3fs.cpp:set_s3fs_log_level(271): change debug level from [INF] to [DBG]
[INF] s3fs.cpp:set_mountpoint_attribute(4206): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755)
FUSE library version: 2.9.4
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
INIT: 7.23
flags=0x0003fffb
max_readahead=0x00020000
[INF] s3fs.cpp:s3fs_init(3371): init v1.83(commit:e1dafe7) with OpenSSL
[INF] s3fs.cpp:s3fs_check_service(3747): check services.
[INF] curl.cpp:CheckBucket(3068): check a bucket.
[DBG] curl.cpp:GetHandler(285): Get handler from pool: 31
[INF] curl.cpp:prepare_url(4253): URL is https://s3.amazonaws.com/yoroshare1/
[INF] curl.cpp:prepare_url(4285): URL changed is https://yoroshare1.s3.amazonaws.com/
[INF] curl.cpp:insertV4Headers(2400): computing signature [GET] [/] [] []
[INF] curl.cpp:url_to_host(101): url is https://s3.amazonaws.com
[DBG] curl.cpp:RequestPerform(2034): connecting to URL https://yoroshare1.s3.amazonaws.com/

  • Trying 52.216.85.59...
  • Connected to yoroshare1.s3.amazonaws.com (52.216.85.59) port 443 (#0)
  • Initializing NSS with certpath: sql:/etc/pki/nssdb
  • CAfile: /etc/pki/tls/certs/ca-bundle.crt
    CApath: none
  • ALPN/NPN, server did not agree to a protocol
  • SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  • Server certificate:
  • subject: CN=*.s3.amazonaws.com,O=Amazon.com Inc.,L=Seattle,ST=Washington,C=US
  • start date: Sep 22 00:00:00 2017 GMT
  • expire date: Jan 03 12:00:00 2019 GMT
  • common name: *.s3.amazonaws.com
  • issuer: CN=DigiCert Baltimore CA-2 G2,OU=www.digicert.com,O=DigiCert Inc,C=US

GET / HTTP/1.1
host: yoroshare1.s3.amazonaws.com
User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL)
Accept: /
Authorization: AWS4-HMAC-SHA256 Credential=AKIAJJM62B4GZ7CVJ4XA/20180111/ap-south-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=2ac2e8f2bd447cf70f5ea296a4421592ac9a60ed940a51481eca361b12e68d09
x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date: 20180111T060205Z

< HTTP/1.1 307 Temporary Redirect
< x-amz-bucket-region: ap-south-1
< x-amz-request-id: C8435975BF43B45A
< x-amz-id-2: R8o15L1bgwwpsL8OVjpF67mdSiXidxMYvDhW6cYI8OMM4eFsXv/UsWnFkmUBhNesK/9rCvdG02k=
< Location: https://yoroshare1.s3.ap-south-1.amazonaws.com/
< Content-Type: application/xml
< Transfer-Encoding: chunked
< Date: Thu, 11 Jan 2018 06:02:05 GMT
< Server: AmazonS3
<

  • Ignoring the response-body
  • Connection #0 to host yoroshare1.s3.amazonaws.com left intact
  • Issue another request to this URL: 'https://yoroshare1.s3.ap-south-1.amazonaws.com/'
  • Trying 52.219.66.38...
  • Connected to yoroshare1.s3.ap-south-1.amazonaws.com (52.219.66.38) port 443 (#1)
  • CAfile: /etc/pki/tls/certs/ca-bundle.crt
    CApath: none
  • ALPN/NPN, server did not agree to a protocol
  • SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  • Server certificate:
  • subject: CN=*.s3.ap-south-1.amazonaws.com,O=Amazon.com Inc.,L=Seattle,ST=Washington,C=US
  • start date: Jul 12 00:00:00 2017 GMT
  • expire date: May 02 12:00:00 2018 GMT
  • common name: *.s3.ap-south-1.amazonaws.com
  • issuer: CN=DigiCert Baltimore CA-2 G2,OU=www.digicert.com,O=DigiCert Inc,C=US

GET / HTTP/1.1
Host: yoroshare1.s3.ap-south-1.amazonaws.com
User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL)
Accept: /
Authorization: AWS4-HMAC-SHA256 Credential=AKIAJJM62B4GZ7CVJ4XA/20180111/ap-south-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=2ac2e8f2bd447cf70f5ea296a4421592ac9a60ed940a51481eca361b12e68d09
x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date: 20180111T060205Z

< HTTP/1.1 403 Forbidden
< x-amz-bucket-region: ap-south-1
< x-amz-request-id: 70F79DCF656BCEF8
< x-amz-id-2: pGZWh/0XJc+VI5N6X0GoWMFMlQJIXYGWYkUYt3RqHVLyxxIFUC/S7gwkFv4q8rGbwm+2zGWOw9o=
< Content-Type: application/xml
< Transfer-Encoding: chunked
< Date: Thu, 11 Jan 2018 06:02:05 GMT
< Server: AmazonS3
<

  • Connection #1 to host yoroshare1.s3.ap-south-1.amazonaws.com left intact
    [INF] curl.cpp:RequestPerform(2068): HTTP response code 403 was returned, returning EPERM
    [DBG] curl.cpp:RequestPerform(2069): Body Text:
    SignatureDoesNotMatchThe request signature we calculated does not match the signature you provided. Check your key and signing method.AKIAJJM62B4GZ7CVJ4XAAWS4-HMAC-SHA256
    20180111T060205Z
    20180111/ap-south-1/s3/aws4_request
    295ed6a3db8e7efd552e208da1c167a329676fe14ee23578dea6e72b517eb2ce2ac2e8f2bd447cf70f5ea296a4421592ac9a60ed940a51481eca361b12e68d0941 57 53 34 2d 48 4d 41 43 2d 53 48 41 32 35 36 0a 32 30 31 38 30 31 31 31 54 30 36 30 32 30 35 5a 0a 32 30 31 38 30 31 31 31 2f 61 70 2d 73 6f 75 74 68 2d 31 2f 73 33 2f 61 77 73 34 5f 72 65 71 75 65 73 74 0a 32 39 35 65 64 36 61 33 64 62 38 65 37 65 66 64 35 35 32 65 32 30 38 64 61 31 63 31 36 37 61 33 32 39 36 37 36 66 65 31 34 65 65 32 33 35 37 38 64 65 61 36 65 37 32 62 35 31 37 65 62 32 63 65GET
    /

host:yoroshare1.s3.ap-south-1.amazonaws.com
x-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date:20180111T060205Z

host;x-amz-content-sha256;x-amz-date
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b85547 45 54 0a 2f 0a 0a 68 6f 73 74 3a 79 6f 72 6f 73 68 61 72 65 31 2e 73 33 2e 61 70 2d 73 6f 75 74 68 2d 31 2e 61 6d 61 7a 6f 6e 61 77 73 2e 63 6f 6d 0a 78 2d 61 6d 7a 2d 63 6f 6e 74 65 6e 74 2d 73 68 61 32 35 36 3a 65 33 62 30 63 34 34 32 39 38 66 63 31 63 31 34 39 61 66 62 66 34 63 38 39 39 36 66 62 39 32 34 32 37 61 65 34 31 65 34 36 34 39 62 39 33 34 63 61 34 39 35 39 39 31 62 37 38 35 32 62 38 35 35 0a 78 2d 61 6d 7a 2d 64 61 74 65 3a 32 30 31 38 30 31 31 31 54 30 36 30 32 30 35 5a 0a 0a 68 6f 73 74 3b 78 2d 61 6d 7a 2d 63 6f 6e 74 65 6e 74 2d 73 68 61 32 35 36 3b 78 2d 61 6d 7a 2d 64 61 74 65 0a 65 33 62 30 63 34 34 32 39 38 66 63 31 63 31 34 39 61 66 62 66 34 63 38 39 39 36 66 62 39 32 34 32 37 61 65 34 31 65 34 36 34 39 62 39 33 34 63 61 34 39 35 39 39 31 62 37 38 35 32 62 38 35 3570F79DCF656BCEF8pGZWh/0XJc+VI5N6X0GoWMFMlQJIXYGWYkUYt3RqHVLyxxIFUC/S7gwkFv4q8rGbwm+2zGWOw9o=
[ERR] curl.cpp:CheckBucket(3096): Check bucket failed, S3 response:
SignatureDoesNotMatchThe request signature we calculated does not match the signature you provided. Check your key and signing method.AKIAJJM62B4GZ7CVJ4XAAWS4-HMAC-SHA256
20180111T060205Z
20180111/ap-south-1/s3/aws4_request
295ed6a3db8e7efd552e208da1c167a329676fe14ee23578dea6e72b517eb2ce2ac2e8f2bd447cf70f5ea296a4421592ac9a60ed940a51481eca361b12e68d0941 57 53 34 2d 48 4d 41 43 2d 53 48 41 32 35 36 0a 32 30 31 38 30 31 31 31 54 30 36 30 32 30 35 5a 0a 32 30 31 38 30 31 31 31 2f 61 70 2d 73 6f 75 74 68 2d 31 2f 73 33 2f 61 77 73 34 5f 72 65 71 75 65 73 74 0a 32 39 35 65 64 36 61 33 64 62 38 65 37 65 66 64 35 35 32 65 32 30 38 64 61 31 63 31 36 37 61 33 32 39 36 37 36 66 65 31 34 65 65 32 33 35 37 38 64 65 61 36 65 37 32 62 35 31 37 65 62 32 63 65GET
/

host:yoroshare1.s3.ap-south-1.amazonaws.com
x-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date:20180111T060205Z

host;x-amz-content-sha256;x-amz-date
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b85547 45 54 0a 2f 0a 0a 68 6f 73 74 3a 79 6f 72 6f 73 68 61 72 65 31 2e 73 33 2e 61 70 2d 73 6f 75 74 68 2d 31 2e 61 6d 61 7a 6f 6e 61 77 73 2e 63 6f 6d 0a 78 2d 61 6d 7a 2d 63 6f 6e 74 65 6e 74 2d 73 68 61 32 35 36 3a 65 33 62 30 63 34 34 32 39 38 66 63 31 63 31 34 39 61 66 62 66 34 63 38 39 39 36 66 62 39 32 34 32 37 61 65 34 31 65 34 36 34 39 62 39 33 34 63 61 34 39 35 39 39 31 62 37 38 35 32 62 38 35 35 0a 78 2d 61 6d 7a 2d 64 61 74 65 3a 32 30 31 38 30 31 31 31 54 30 36 30 32 30 35 5a 0a 0a 68 6f 73 74 3b 78 2d 61 6d 7a 2d 63 6f 6e 74 65 6e 74 2d 73 68 61 32 35 36 3b 78 2d 61 6d 7a 2d 64 61 74 65 0a 65 33 62 30 63 34 34 32 39 38 66 63 31 63 31 34 39 61 66 62 66 34 63 38 39 39 36 66 62 39 32 34 32 37 61 65 34 31 65 34 36 34 39 62 39 33 34 63 61 34 39 35 39 39 31 62 37 38 35 32 62 38 35 3570F79DCF656BCEF8pGZWh/0XJc+VI5N6X0GoWMFMlQJIXYGWYkUYt3RqHVLyxxIFUC/S7gwkFv4q8rGbwm+2zGWOw9o=
[WAN] s3fs.cpp:s3fs_check_service(3788): Could not connect, so retry to connect by signature version 2.
[DBG] curl.cpp:ReturnHandler(308): Return handler to pool: 31
[INF] curl.cpp:CheckBucket(3068): check a bucket.
[DBG] curl.cpp:GetHandler(285): Get handler from pool: 31
[INF] curl.cpp:prepare_url(4253): URL is https://s3.amazonaws.com/yoroshare1/
[INF] curl.cpp:prepare_url(4285): URL changed is https://yoroshare1.s3.amazonaws.com/
[DBG] curl.cpp:RequestPerform(2034): connecting to URL https://yoroshare1.s3.amazonaws.com/

  • Found bundle for host yoroshare1.s3.amazonaws.com: 0x7f1b4015e2e0 [can pipeline]
  • Re-using existing connection! (#0) with host yoroshare1.s3.amazonaws.com
  • Connected to yoroshare1.s3.amazonaws.com (52.216.85.59) port 443 (#0)

GET / HTTP/1.1
Host: yoroshare1.s3.amazonaws.com
User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL)
Accept: /
Authorization: AWS AKIAJJM62B4GZ7CVJ4XA:s89PMWBI4pxTsE/HSpeK5QUUORg=
Date: Thu, 11 Jan 2018 06:02:06 GMT

< HTTP/1.1 307 Temporary Redirect
< x-amz-bucket-region: ap-south-1
< x-amz-request-id: CDACA2F4133522F6
< x-amz-id-2: Lb70BiSzRxaLikdKbNFfMtUTNcjNSnsqsks07a/Kflclr2su+6creiQot0ZnXywJiwajwuqTNhE=
< Location: https://yoroshare1.s3.ap-south-1.amazonaws.com/
< Content-Type: application/xml
< Transfer-Encoding: chunked
< Date: Thu, 11 Jan 2018 06:02:05 GMT
< Server: AmazonS3
<

  • Ignoring the response-body
  • Connection #0 to host yoroshare1.s3.amazonaws.com left intact
  • Issue another request to this URL: 'https://yoroshare1.s3.ap-south-1.amazonaws.com/'
  • Found bundle for host yoroshare1.s3.ap-south-1.amazonaws.com: 0x7f1b401db710 [can pipeline]
  • Re-using existing connection! (#1) with host yoroshare1.s3.ap-south-1.amazonaws.com
  • Connected to yoroshare1.s3.ap-south-1.amazonaws.com (52.219.66.38) port 443 (#1)

GET / HTTP/1.1
Host: yoroshare1.s3.ap-south-1.amazonaws.com
User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL)
Accept: /
Authorization: AWS AKIAJJM62B4GZ7CVJ4XA:s89PMWBI4pxTsE/HSpeK5QUUORg=
Date: Thu, 11 Jan 2018 06:02:06 GMT

< HTTP/1.1 400 Bad Request
< x-amz-bucket-region: ap-south-1
< x-amz-request-id: 59D4BA985A0D750F
< x-amz-id-2: QaRhfhdCUt+nySbz8m8szKPW4qRUAayExRj7ig/fKfIs5khJHFFd8WofoUOqCdjYLEwIrZcoD4k=
< x-amz-region: ap-south-1
< Content-Type: application/xml
< Transfer-Encoding: chunked
< Date: Thu, 11 Jan 2018 06:02:05 GMT
< Connection: close
< Server: AmazonS3
<

  • Closing connection 1
    [INF] curl.cpp:RequestPerform(2063): HTTP response code 400 was returned, returning EIO.
    [DBG] curl.cpp:RequestPerform(2064): Body Text:
    InvalidRequestThe authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.59D4BA985A0D750FQaRhfhdCUt+nySbz8m8szKPW4qRUAayExRj7ig/fKfIs5khJHFFd8WofoUOqCdjYLEwIrZcoD4k=
    [ERR] curl.cpp:CheckBucket(3096): Check bucket failed, S3 response:
    InvalidRequestThe authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.59D4BA985A0D750FQaRhfhdCUt+nySbz8m8szKPW4qRUAayExRj7ig/fKfIs5khJHFFd8WofoUOqCdjYLEwIrZcoD4k=
    [CRT] s3fs.cpp:s3fs_check_service(3800): Bad Request(host=https://s3.amazonaws.com) - result of checking service.
    [DBG] curl.cpp:ReturnHandler(308): Return handler to pool: 31
    [ERR] s3fs.cpp:s3fs_exit_fuseloop(3361): Exiting FUSE event loop due to errors

    INIT: 7.19
    flags=0x00000011
    max_readahead=0x00020000
    max_write=0x00020000
    max_background=0
    congestion_threshold=0
    unique: 1, success, outsize: 40
    [INF] s3fs.cpp:s3fs_destroy(3434): destroy
    [WAN] s3fs.cpp:s3fs_destroy(3438): Could not release curl library.

<!-- gh-comment-id:356835555 --> @socialglass commented on GitHub (Jan 11, 2018): That seems to resolve the region mismatch, but still getting an authorization error - > [ec2-user@ip mnt]$ sudo s3fs yoroshare1 /mnt -o passwd_file=/home/ec2-user/.passwd-s3fs -d -d -f -o f2 -o curldbg -o endpoint=ap-south-1 > [CRT] s3fs.cpp:set_s3fs_log_level(271): change debug level from [CRT] to [INF] > [CRT] s3fs.cpp:set_s3fs_log_level(271): change debug level from [INF] to [DBG] > [INF] s3fs.cpp:set_mountpoint_attribute(4206): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755) > FUSE library version: 2.9.4 > nullpath_ok: 0 > nopath: 0 > utime_omit_ok: 0 > unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0 > INIT: 7.23 > flags=0x0003fffb > max_readahead=0x00020000 > [INF] s3fs.cpp:s3fs_init(3371): init v1.83(commit:e1dafe7) with OpenSSL > [INF] s3fs.cpp:s3fs_check_service(3747): check services. > [INF] curl.cpp:CheckBucket(3068): check a bucket. > [DBG] curl.cpp:GetHandler(285): Get handler from pool: 31 > [INF] curl.cpp:prepare_url(4253): URL is https://s3.amazonaws.com/yoroshare1/ > [INF] curl.cpp:prepare_url(4285): URL changed is https://yoroshare1.s3.amazonaws.com/ > [INF] curl.cpp:insertV4Headers(2400): computing signature [GET] [/] [] [] > [INF] curl.cpp:url_to_host(101): url is https://s3.amazonaws.com > [DBG] curl.cpp:RequestPerform(2034): connecting to URL https://yoroshare1.s3.amazonaws.com/ > * Trying 52.216.85.59... > * Connected to yoroshare1.s3.amazonaws.com (52.216.85.59) port 443 (#0) > * Initializing NSS with certpath: sql:/etc/pki/nssdb > * CAfile: /etc/pki/tls/certs/ca-bundle.crt > CApath: none > * ALPN/NPN, server did not agree to a protocol > * SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 > * Server certificate: > * subject: CN=*.s3.amazonaws.com,O=Amazon.com Inc.,L=Seattle,ST=Washington,C=US > * start date: Sep 22 00:00:00 2017 GMT > * expire date: Jan 03 12:00:00 2019 GMT > * common name: *.s3.amazonaws.com > * issuer: CN=DigiCert Baltimore CA-2 G2,OU=www.digicert.com,O=DigiCert Inc,C=US > > GET / HTTP/1.1 > host: yoroshare1.s3.amazonaws.com > User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL) > Accept: */* > Authorization: AWS4-HMAC-SHA256 Credential=AKIAJJM62B4GZ7CVJ4XA/20180111/ap-south-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=2ac2e8f2bd447cf70f5ea296a4421592ac9a60ed940a51481eca361b12e68d09 > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 > x-amz-date: 20180111T060205Z > > < HTTP/1.1 307 Temporary Redirect > < x-amz-bucket-region: ap-south-1 > < x-amz-request-id: C8435975BF43B45A > < x-amz-id-2: R8o15L1bgwwpsL8OVjpF67mdSiXidxMYvDhW6cYI8OMM4eFsXv/UsWnFkmUBhNesK/9rCvdG02k= > < Location: https://yoroshare1.s3.ap-south-1.amazonaws.com/ > < Content-Type: application/xml > < Transfer-Encoding: chunked > < Date: Thu, 11 Jan 2018 06:02:05 GMT > < Server: AmazonS3 > < > * Ignoring the response-body > * Connection #0 to host yoroshare1.s3.amazonaws.com left intact > * Issue another request to this URL: 'https://yoroshare1.s3.ap-south-1.amazonaws.com/' > * Trying 52.219.66.38... > * Connected to yoroshare1.s3.ap-south-1.amazonaws.com (52.219.66.38) port 443 (#1) > * CAfile: /etc/pki/tls/certs/ca-bundle.crt > CApath: none > * ALPN/NPN, server did not agree to a protocol > * SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 > * Server certificate: > * subject: CN=*.s3.ap-south-1.amazonaws.com,O=Amazon.com Inc.,L=Seattle,ST=Washington,C=US > * start date: Jul 12 00:00:00 2017 GMT > * expire date: May 02 12:00:00 2018 GMT > * common name: *.s3.ap-south-1.amazonaws.com > * issuer: CN=DigiCert Baltimore CA-2 G2,OU=www.digicert.com,O=DigiCert Inc,C=US > > GET / HTTP/1.1 > Host: yoroshare1.s3.ap-south-1.amazonaws.com > User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL) > Accept: */* > Authorization: AWS4-HMAC-SHA256 Credential=AKIAJJM62B4GZ7CVJ4XA/20180111/ap-south-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=2ac2e8f2bd447cf70f5ea296a4421592ac9a60ed940a51481eca361b12e68d09 > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 > x-amz-date: 20180111T060205Z > > < HTTP/1.1 403 Forbidden > < x-amz-bucket-region: ap-south-1 > < x-amz-request-id: 70F79DCF656BCEF8 > < x-amz-id-2: pGZWh/0XJc+VI5N6X0GoWMFMlQJIXYGWYkUYt3RqHVLyxxIFUC/S7gwkFv4q8rGbwm+2zGWOw9o= > < Content-Type: application/xml > < Transfer-Encoding: chunked > < Date: Thu, 11 Jan 2018 06:02:05 GMT > < Server: AmazonS3 > < > * Connection #1 to host yoroshare1.s3.ap-south-1.amazonaws.com left intact > [INF] curl.cpp:RequestPerform(2068): HTTP response code 403 was returned, returning EPERM > [DBG] curl.cpp:RequestPerform(2069): Body Text: <?xml version="1.0" encoding="UTF-8"?> > <Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><AWSAccessKeyId>AKIAJJM62B4GZ7CVJ4XA</AWSAccessKeyId><StringToSign>AWS4-HMAC-SHA256 > 20180111T060205Z > 20180111/ap-south-1/s3/aws4_request > 295ed6a3db8e7efd552e208da1c167a329676fe14ee23578dea6e72b517eb2ce</StringToSign><SignatureProvided>2ac2e8f2bd447cf70f5ea296a4421592ac9a60ed940a51481eca361b12e68d09</SignatureProvided><StringToSignBytes>41 57 53 34 2d 48 4d 41 43 2d 53 48 41 32 35 36 0a 32 30 31 38 30 31 31 31 54 30 36 30 32 30 35 5a 0a 32 30 31 38 30 31 31 31 2f 61 70 2d 73 6f 75 74 68 2d 31 2f 73 33 2f 61 77 73 34 5f 72 65 71 75 65 73 74 0a 32 39 35 65 64 36 61 33 64 62 38 65 37 65 66 64 35 35 32 65 32 30 38 64 61 31 63 31 36 37 61 33 32 39 36 37 36 66 65 31 34 65 65 32 33 35 37 38 64 65 61 36 65 37 32 62 35 31 37 65 62 32 63 65</StringToSignBytes><CanonicalRequest>GET > / > > host:yoroshare1.s3.ap-south-1.amazonaws.com > x-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 > x-amz-date:20180111T060205Z > > host;x-amz-content-sha256;x-amz-date > e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855</CanonicalRequest><CanonicalRequestBytes>47 45 54 0a 2f 0a 0a 68 6f 73 74 3a 79 6f 72 6f 73 68 61 72 65 31 2e 73 33 2e 61 70 2d 73 6f 75 74 68 2d 31 2e 61 6d 61 7a 6f 6e 61 77 73 2e 63 6f 6d 0a 78 2d 61 6d 7a 2d 63 6f 6e 74 65 6e 74 2d 73 68 61 32 35 36 3a 65 33 62 30 63 34 34 32 39 38 66 63 31 63 31 34 39 61 66 62 66 34 63 38 39 39 36 66 62 39 32 34 32 37 61 65 34 31 65 34 36 34 39 62 39 33 34 63 61 34 39 35 39 39 31 62 37 38 35 32 62 38 35 35 0a 78 2d 61 6d 7a 2d 64 61 74 65 3a 32 30 31 38 30 31 31 31 54 30 36 30 32 30 35 5a 0a 0a 68 6f 73 74 3b 78 2d 61 6d 7a 2d 63 6f 6e 74 65 6e 74 2d 73 68 61 32 35 36 3b 78 2d 61 6d 7a 2d 64 61 74 65 0a 65 33 62 30 63 34 34 32 39 38 66 63 31 63 31 34 39 61 66 62 66 34 63 38 39 39 36 66 62 39 32 34 32 37 61 65 34 31 65 34 36 34 39 62 39 33 34 63 61 34 39 35 39 39 31 62 37 38 35 32 62 38 35 35</CanonicalRequestBytes><RequestId>70F79DCF656BCEF8</RequestId><HostId>pGZWh/0XJc+VI5N6X0GoWMFMlQJIXYGWYkUYt3RqHVLyxxIFUC/S7gwkFv4q8rGbwm+2zGWOw9o=</HostId></Error> > [ERR] curl.cpp:CheckBucket(3096): Check bucket failed, S3 response: <?xml version="1.0" encoding="UTF-8"?> > <Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><AWSAccessKeyId>AKIAJJM62B4GZ7CVJ4XA</AWSAccessKeyId><StringToSign>AWS4-HMAC-SHA256 > 20180111T060205Z > 20180111/ap-south-1/s3/aws4_request > 295ed6a3db8e7efd552e208da1c167a329676fe14ee23578dea6e72b517eb2ce</StringToSign><SignatureProvided>2ac2e8f2bd447cf70f5ea296a4421592ac9a60ed940a51481eca361b12e68d09</SignatureProvided><StringToSignBytes>41 57 53 34 2d 48 4d 41 43 2d 53 48 41 32 35 36 0a 32 30 31 38 30 31 31 31 54 30 36 30 32 30 35 5a 0a 32 30 31 38 30 31 31 31 2f 61 70 2d 73 6f 75 74 68 2d 31 2f 73 33 2f 61 77 73 34 5f 72 65 71 75 65 73 74 0a 32 39 35 65 64 36 61 33 64 62 38 65 37 65 66 64 35 35 32 65 32 30 38 64 61 31 63 31 36 37 61 33 32 39 36 37 36 66 65 31 34 65 65 32 33 35 37 38 64 65 61 36 65 37 32 62 35 31 37 65 62 32 63 65</StringToSignBytes><CanonicalRequest>GET > / > > host:yoroshare1.s3.ap-south-1.amazonaws.com > x-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 > x-amz-date:20180111T060205Z > > host;x-amz-content-sha256;x-amz-date > e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855</CanonicalRequest><CanonicalRequestBytes>47 45 54 0a 2f 0a 0a 68 6f 73 74 3a 79 6f 72 6f 73 68 61 72 65 31 2e 73 33 2e 61 70 2d 73 6f 75 74 68 2d 31 2e 61 6d 61 7a 6f 6e 61 77 73 2e 63 6f 6d 0a 78 2d 61 6d 7a 2d 63 6f 6e 74 65 6e 74 2d 73 68 61 32 35 36 3a 65 33 62 30 63 34 34 32 39 38 66 63 31 63 31 34 39 61 66 62 66 34 63 38 39 39 36 66 62 39 32 34 32 37 61 65 34 31 65 34 36 34 39 62 39 33 34 63 61 34 39 35 39 39 31 62 37 38 35 32 62 38 35 35 0a 78 2d 61 6d 7a 2d 64 61 74 65 3a 32 30 31 38 30 31 31 31 54 30 36 30 32 30 35 5a 0a 0a 68 6f 73 74 3b 78 2d 61 6d 7a 2d 63 6f 6e 74 65 6e 74 2d 73 68 61 32 35 36 3b 78 2d 61 6d 7a 2d 64 61 74 65 0a 65 33 62 30 63 34 34 32 39 38 66 63 31 63 31 34 39 61 66 62 66 34 63 38 39 39 36 66 62 39 32 34 32 37 61 65 34 31 65 34 36 34 39 62 39 33 34 63 61 34 39 35 39 39 31 62 37 38 35 32 62 38 35 35</CanonicalRequestBytes><RequestId>70F79DCF656BCEF8</RequestId><HostId>pGZWh/0XJc+VI5N6X0GoWMFMlQJIXYGWYkUYt3RqHVLyxxIFUC/S7gwkFv4q8rGbwm+2zGWOw9o=</HostId></Error> > [WAN] s3fs.cpp:s3fs_check_service(3788): Could not connect, so retry to connect by signature version 2. > [DBG] curl.cpp:ReturnHandler(308): Return handler to pool: 31 > [INF] curl.cpp:CheckBucket(3068): check a bucket. > [DBG] curl.cpp:GetHandler(285): Get handler from pool: 31 > [INF] curl.cpp:prepare_url(4253): URL is https://s3.amazonaws.com/yoroshare1/ > [INF] curl.cpp:prepare_url(4285): URL changed is https://yoroshare1.s3.amazonaws.com/ > [DBG] curl.cpp:RequestPerform(2034): connecting to URL https://yoroshare1.s3.amazonaws.com/ > * Found bundle for host yoroshare1.s3.amazonaws.com: 0x7f1b4015e2e0 [can pipeline] > * Re-using existing connection! (#0) with host yoroshare1.s3.amazonaws.com > * Connected to yoroshare1.s3.amazonaws.com (52.216.85.59) port 443 (#0) > > GET / HTTP/1.1 > Host: yoroshare1.s3.amazonaws.com > User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL) > Accept: */* > Authorization: AWS AKIAJJM62B4GZ7CVJ4XA:s89PMWBI4pxTsE/HSpeK5QUUORg= > Date: Thu, 11 Jan 2018 06:02:06 GMT > > < HTTP/1.1 307 Temporary Redirect > < x-amz-bucket-region: ap-south-1 > < x-amz-request-id: CDACA2F4133522F6 > < x-amz-id-2: Lb70BiSzRxaLikdKbNFfMtUTNcjNSnsqsks07a/Kflclr2su+6creiQot0ZnXywJiwajwuqTNhE= > < Location: https://yoroshare1.s3.ap-south-1.amazonaws.com/ > < Content-Type: application/xml > < Transfer-Encoding: chunked > < Date: Thu, 11 Jan 2018 06:02:05 GMT > < Server: AmazonS3 > < > * Ignoring the response-body > * Connection #0 to host yoroshare1.s3.amazonaws.com left intact > * Issue another request to this URL: 'https://yoroshare1.s3.ap-south-1.amazonaws.com/' > * Found bundle for host yoroshare1.s3.ap-south-1.amazonaws.com: 0x7f1b401db710 [can pipeline] > * Re-using existing connection! (#1) with host yoroshare1.s3.ap-south-1.amazonaws.com > * Connected to yoroshare1.s3.ap-south-1.amazonaws.com (52.219.66.38) port 443 (#1) > > GET / HTTP/1.1 > Host: yoroshare1.s3.ap-south-1.amazonaws.com > User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL) > Accept: */* > Authorization: AWS AKIAJJM62B4GZ7CVJ4XA:s89PMWBI4pxTsE/HSpeK5QUUORg= > Date: Thu, 11 Jan 2018 06:02:06 GMT > > < HTTP/1.1 400 Bad Request > < x-amz-bucket-region: ap-south-1 > < x-amz-request-id: 59D4BA985A0D750F > < x-amz-id-2: QaRhfhdCUt+nySbz8m8szKPW4qRUAayExRj7ig/fKfIs5khJHFFd8WofoUOqCdjYLEwIrZcoD4k= > < x-amz-region: ap-south-1 > < Content-Type: application/xml > < Transfer-Encoding: chunked > < Date: Thu, 11 Jan 2018 06:02:05 GMT > < Connection: close > < Server: AmazonS3 > < > * Closing connection 1 > [INF] curl.cpp:RequestPerform(2063): HTTP response code 400 was returned, returning EIO. > [DBG] curl.cpp:RequestPerform(2064): Body Text: <?xml version="1.0" encoding="UTF-8"?> > <Error><Code>InvalidRequest</Code><Message>The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.</Message><RequestId>59D4BA985A0D750F</RequestId><HostId>QaRhfhdCUt+nySbz8m8szKPW4qRUAayExRj7ig/fKfIs5khJHFFd8WofoUOqCdjYLEwIrZcoD4k=</HostId></Error> > [ERR] curl.cpp:CheckBucket(3096): Check bucket failed, S3 response: <?xml version="1.0" encoding="UTF-8"?> > <Error><Code>InvalidRequest</Code><Message>The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.</Message><RequestId>59D4BA985A0D750F</RequestId><HostId>QaRhfhdCUt+nySbz8m8szKPW4qRUAayExRj7ig/fKfIs5khJHFFd8WofoUOqCdjYLEwIrZcoD4k=</HostId></Error> > [CRT] s3fs.cpp:s3fs_check_service(3800): Bad Request(host=https://s3.amazonaws.com) - result of checking service. > [DBG] curl.cpp:ReturnHandler(308): Return handler to pool: 31 > [ERR] s3fs.cpp:s3fs_exit_fuseloop(3361): Exiting FUSE event loop due to errors > > INIT: 7.19 > flags=0x00000011 > max_readahead=0x00020000 > max_write=0x00020000 > max_background=0 > congestion_threshold=0 > unique: 1, success, outsize: 40 > [INF] s3fs.cpp:s3fs_destroy(3434): destroy > [WAN] s3fs.cpp:s3fs_destroy(3438): Could not release curl library.
kerem commented 2026-03-04 01:45:11 +03:00
Author
Owner
Copy link

@socialglass commented on GitHub (Jan 13, 2018):

Was an incorrect credential issue thereafter. Still not clear why it didn't pick the region automatically though.

<!-- gh-comment-id:357409067 --> @socialglass commented on GitHub (Jan 13, 2018): Was an incorrect credential issue thereafter. Still not clear why it didn't pick the region automatically though.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
v1.97
v1.96
v1.95
v1.94
v1.93
v1.92
v1.91
v1.90
v1.89
v1.88
v1.87
v1.86
v1.85
v1.84
v1.83
v1.82
v1.81
v1.80
v1.79
v1.78
Pre-v1.78
v1.77
v1.76
v1.75
v1.74
Labels
Clear labels   
bug

   
bug

   
dataloss

   
duplicate

   
enhancement

   
feature request

   
help wanted

   
invalid

   
need info

   
performance

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question

   
testing
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/s3fs-fuse#398
No description provided.