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

[GH-ISSUE #1509] ap-east-1 can not mount s3fs #792

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

Originally created by @ntulp on GitHub (Dec 30, 2020).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1509

when i create us-east-1 bucket will mount success .. something wrong on ap-east-1 (HK)

Version of s3fs being used (s3fs --version)

V1.87

Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)

2.9.9

Kernel information (uname -r)

4.19.0-13-cloud-amd64

GNU/Linux Distribution, if applicable (cat /etc/os-release)

command result: cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"

s3fs command line used, if applicable

/usr/local/bin/s3fs mys3 /mnt -o passwd_file=/root/.passwd-s3fs -o endpoint=ap-east-1   -d -d -f -o f2 -o curldbg

/etc/fstab entry, if applicable

s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)

if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages

[CRT] s3fs_logger.cpp:LowSetLogLevel(201): change debug level from [CRT] to [INF]
[CRT] s3fs_logger.cpp:LowSetLogLevel(201): change debug level from [INF] to [DBG]
[INF]     s3fs.cpp:set_mountpoint_attribute(3989): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755)
[DBG] curl.cpp:InitMimeType(410): Try to load mime types from /etc/mime.types file.
[DBG] curl.cpp:InitMimeType(415): The old mime types are cleared to load new mime types.
[INF] curl.cpp:InitMimeType(438): Loaded mime information from /etc/mime.types
[INF] fdcache_stat.cpp:CheckCacheFileStatTopDir(79): The path to cache top dir is empty, thus not need to check permission.
FUSE library version: 2.9.9
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
INIT: 7.27
flags=0x003ffffb
max_readahead=0x00020000
[INF] s3fs.cpp:s3fs_init(3300): init v1.87(commit:d1c638a) with OpenSSL
[INF] s3fs.cpp:s3fs_check_service(3416): check services.
[INF]       curl.cpp:CheckBucket(3310): check a bucket.
[DBG] curl_handlerpool.cpp:GetHandler(81): Get handler from pool: rest = 31
[INF]       curl_util.cpp:prepare_url(223): URL is https://s3.amazonaws.com/mys3/
[INF]       curl_util.cpp:prepare_url(256): URL changed is https://mys3.s3.amazonaws.com/
[DBG] curl.cpp:RequestPerform(2226): connecting to URL https://mys3.s3.amazonaws.com/
[INF]       curl.cpp:insertV4Headers(2590): computing signature [GET] [/] [] []
[INF]       curl_util.cpp:url_to_host(300): url is https://s3.amazonaws.com
[CURL DBG] * Expire in 0 ms for 6 (transfer 0x5613c967f230)
[CURL DBG] * Expire in 300000 ms for 2 (transfer 0x5613c967f230)
[CURL DBG] * Uses proxy env variable https_proxy == 'http://172.20.0.248:3128'
[CURL DBG] *   Trying 172.20.0.248...
[CURL DBG] * TCP_NODELAY set
[CURL DBG] * Expire in 200 ms for 4 (transfer 0x5613c967f230)
[CURL DBG] * Connected to 172.20.0.248 (172.20.0.248) port 3128 (#0)
[CURL DBG] * allocate connect buffer!
[CURL DBG] * Establish HTTP proxy tunnel to mys3.s3.amazonaws.com:443
[CURL DBG] > CONNECT mys3.s3.amazonaws.com:443 HTTP/1.1
[CURL DBG] > Host: mys3.s3.amazonaws.com:443
[CURL DBG] > User-Agent: s3fs/1.87 (commit hash d1c638a; OpenSSL)
[CURL DBG] > Proxy-Connection: Keep-Alive
[CURL DBG] >
[CURL DBG] < HTTP/1.1 200 Connection established
[CURL DBG] <
[CURL DBG] * Proxy replied 200 to CONNECT request
[CURL DBG] * CONNECT phase completed!
[CURL DBG] * successfully set certificate verify locations:
[CURL DBG] *   CAfile: none
  CApath: /etc/ssl/certs
[CURL DBG] * TLSv1.3 (OUT), TLS handshake, Client hello (1):
[CURL DBG] * CONNECT phase completed!
[CURL DBG] * CONNECT phase completed!
[CURL DBG] * TLSv1.3 (IN), TLS handshake, Server hello (2):
[CURL DBG] * TLSv1.2 (IN), TLS handshake, Certificate (11):
[CURL DBG] * TLSv1.2 (IN), TLS handshake, Server key exchange (12):
[CURL DBG] * TLSv1.2 (IN), TLS handshake, Server finished (14):
[CURL DBG] * TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
[CURL DBG] * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
[CURL DBG] * TLSv1.2 (OUT), TLS handshake, Finished (20):
[CURL DBG] * TLSv1.2 (IN), TLS handshake, Finished (20):
[CURL DBG] * SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
[CURL DBG] * Server certificate:
[CURL DBG] *  subject: C=US; ST=Washington; L=Seattle; O=Amazon.com, Inc.; CN=*.s3.amazonaws.com
[CURL DBG] *  start date: Nov  9 00:00:00 2019 GMT
[CURL DBG] *  expire date: Mar 12 12:00:00 2021 GMT
[CURL DBG] *  subjectAltName: host "mys3.s3.amazonaws.com" matched cert's "*.s3.amazonaws.com"
[CURL DBG] *  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert Baltimore CA-2 G2
[CURL DBG] *  SSL certificate verify ok.
[CURL DBG] > GET / HTTP/1.1
[CURL DBG] > Host: mys3.s3.amazonaws.com
[CURL DBG] > User-Agent: s3fs/1.87 (commit hash d1c638a; OpenSSL)
[CURL DBG] > Accept: */*
[CURL DBG] > Authorization: AWS4-HMAC-SHA256 Credential=AKJSDOIWNBFU/20201230/ap-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=wefkwmnfhfbnm,fle,flwmnfwew
[CURL DBG] > x-amz-content-sha256: fwifwnjkwlf,womfnwinfiwwhgwhjklw,m23b
[CURL DBG] > x-amz-date: 20201230T145748Z
[CURL DBG] >
[CURL DBG] < HTTP/1.1 400 Bad Request
[CURL DBG] < x-amz-bucket-region: ap-east-1
[CURL DBG] < x-amz-request-id: BC02CD607D9DA493
[CURL DBG] < x-amz-id-2: sdfnwkwlfw kmmKNJNJKLWMD:LWMDKNJBFWKK=
[CURL DBG] < Content-Type: application/xml
[CURL DBG] < Transfer-Encoding: chunked
[CURL DBG] < Date: Wed, 30 Dec 2020 14:57:48 GMT
[CURL DBG] < Connection: close
[CURL DBG] < Server: AmazonS3
[CURL DBG] <
[CURL DBG] * Closing connection 0
[ERR] curl.cpp:RequestPerform(2274): HTTP response code 400, returning EIO. Body Text: <?xml version="1.0" encoding="UTF-8"?>
<Error><Code>IllegalLocationConstraintException</Code><Message>The ap-east-1 location constraint is incompatible for the region specific endpoint this request was sent to.</Message><RequestId>sadnafwlfkwef</RequestId><HostId>asdlfmwlnjwlkfmemfw;f =</HostId></Error>
[ERR] curl.cpp:CheckBucket(3336): Check bucket failed, S3 response: <?xml version="1.0" encoding="UTF-8"?>
<Error><Code>IllegalLocationConstraintException</Code><Message>The ap-east-1 location constraint is incompatible for the region specific endpoint this request was sent to.</Message><RequestId>aslkmdnfjkwlfmenfjw</RequestId><HostId>lkmnwkfkmlNIUBHJKNMLL=</HostId></Error>
[CRT] s3fs.cpp:s3fs_check_service(3471): Failed to connect by sigv4, so retry to connect by signature version 2.
[DBG] curl_handlerpool.cpp:ReturnHandler(103): Return handler to pool
[INF] curl_handlerpool.cpp:ReturnHandler(110): Pool full: destroy the oldest handler
[INF]       curl.cpp:CheckBucket(3310): check a bucket.
[DBG] curl_handlerpool.cpp:GetHandler(81): Get handler from pool: rest = 30
[INF]       curl_util.cpp:prepare_url(223): URL is https://s3.amazonaws.com/tmys3/
[INF]       curl_util.cpp:prepare_url(256): URL changed is https://mys3.s3.amazonaws.com/
[DBG] curl.cpp:RequestPerform(2226): connecting to URL https://mys3.s3.amazonaws.com/
[CURL DBG] * Expire in 0 ms for 6 (transfer 0x5613c967f230)
[CURL DBG] * Expire in 300000 ms for 2 (transfer 0x5613c967f230)
[CURL DBG] * Uses proxy env variable https_proxy == 'http://172.20.0.248:3128'
[CURL DBG] * Hostname 172.20.0.248 was found in DNS cache
[CURL DBG] *   Trying 172.20.0.248...
[CURL DBG] * TCP_NODELAY set
[CURL DBG] * Expire in 200 ms for 4 (transfer 0x5613c967f230)
[CURL DBG] * Connected to 172.20.0.248 (172.20.0.248) port 3128 (#1)
[CURL DBG] * allocate connect buffer!
[CURL DBG] * Establish HTTP proxy tunnel to mys3.s3.amazonaws.com:443
[CURL DBG] > CONNECT mys3.s3.amazonaws.com:443 HTTP/1.1
[CURL DBG] > Host: mys3.s3.amazonaws.com:443
[CURL DBG] > User-Agent: s3fs/1.87 (commit hash d1c638a; OpenSSL)
[CURL DBG] > Proxy-Connection: Keep-Alive
[CURL DBG] >
[CURL DBG] < HTTP/1.1 200 Connection established
[CURL DBG] <
[CURL DBG] * Proxy replied 200 to CONNECT request
[CURL DBG] * CONNECT phase completed!
[CURL DBG] * successfully set certificate verify locations:
[CURL DBG] *   CAfile: none
  CApath: /etc/ssl/certs
[CURL DBG] * SSL re-using session ID
[CURL DBG] * TLSv1.3 (OUT), TLS handshake, Client hello (1):
[CURL DBG] * CONNECT phase completed!
[CURL DBG] * CONNECT phase completed!
[CURL DBG] * TLSv1.3 (IN), TLS handshake, Server hello (2):
[CURL DBG] * TLSv1.2 (IN), TLS handshake, Certificate (11):
[CURL DBG] * TLSv1.2 (IN), TLS handshake, Server key exchange (12):
[CURL DBG] * TLSv1.2 (IN), TLS handshake, Server finished (14):
[CURL DBG] * TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
[CURL DBG] * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
[CURL DBG] * TLSv1.2 (OUT), TLS handshake, Finished (20):
[CURL DBG] * TLSv1.2 (IN), TLS handshake, Finished (20):
[CURL DBG] * old SSL session ID is stale, removing
[CURL DBG] * SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
[CURL DBG] * Server certificate:
[CURL DBG] *  subject: C=US; ST=Washington; L=Seattle; O=Amazon.com, Inc.; CN=*.s3.amazonaws.com
[CURL DBG] *  start date: Nov  9 00:00:00 2019 GMT
[CURL DBG] *  expire date: Mar 12 12:00:00 2021 GMT
[CURL DBG] *  subjectAltName: host "mys3.s3.amazonaws.com" matched cert's "*.s3.amazonaws.com"
[CURL DBG] *  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert Baltimore CA-2 G2
[CURL DBG] *  SSL certificate verify ok.
[CURL DBG] > GET / HTTP/1.1
[CURL DBG] > Host: mys3s3.amazonaws.com
[CURL DBG] > User-Agent: s3fs/1.87 (commit hash d1c638a; OpenSSL)
[CURL DBG] > Accept: */*
[CURL DBG] > Authorization: AWS ;wflmkwnjflkf;ljaNKHBJNKLlkJNK/4whWr7BTCWiWq22t0Jv/lo=
[CURL DBG] > Date: Wed, 30 Dec 2020 14:57:49 GMT
[CURL DBG] >
[CURL DBG] < HTTP/1.1 400 Bad Request
[CURL DBG] < x-amz-bucket-region: ap-east-1
[CURL DBG] < x-amz-request-id: wlekjnsakmldkNJKNKJ
[CURL DBG] < x-amz-id-2: slaniJOIJOSJDW++UO/wOks5be3T1/wefkmiUHYBNM+wekfmlfew+lskamdKKKM=
[CURL DBG] < Content-Type: application/xml
[CURL DBG] < Transfer-Encoding: chunked
[CURL DBG] < Date: Wed, 30 Dec 2020 14:57:49 GMT
[CURL DBG] < Connection: close
[CURL DBG] < Server: AmazonS3
[CURL DBG] <
[CURL DBG] * Closing connection 1
[ERR] curl.cpp:RequestPerform(2274): HTTP response code 400, returning EIO. Body Text: <?xml version="1.0" encoding="UTF-8"?>
<Error><Code>IllegalLocationConstraintException</Code><Message>The ap-east-1 location constraint is incompatible for the region specific endpoint this request was sent to.</Message><RequestId>LKJNBKLK</RequestId><HostId>wkjnfjnbBBNON++UO/wOks5be3T1/i23n68E9ErKCE48+LKJNjkwlfm+wel;fmknjNBYUGBH=</HostId></Error>
[ERR] curl.cpp:CheckBucket(3336): Check bucket failed, S3 response: <?xml version="1.0" encoding="UTF-8"?>
<Error><Code>IllegalLocationConstraintException</Code><Message>The ap-east-1 location constraint is incompatible for the region specific endpoint this request was sent to.</Message><RequestId>KLJHGJNIMK</RequestId><HostId>IJOIMNLK++UO/:MJKLKM/i23n68E9ErKCE48+L:KMN+EIqUWv0ngV58WMPgww=</HostId></Error>
[CRT] s3fs.cpp:s3fs_check_service(3483): Bad Request(host=https://s3.amazonaws.com) - result of checking service.
[DBG] curl_handlerpool.cpp:ReturnHandler(103): Return handler to pool
[ERR] s3fs.cpp:s3fs_exit_fuseloop(3290): 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(3358): destroy

Details about issue

Originally created by @ntulp on GitHub (Dec 30, 2020). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1509 when i create us-east-1 bucket will mount success .. something wrong on ap-east-1 (HK) #### Version of s3fs being used (s3fs --version) V1.87 #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) 2.9.9 #### Kernel information (uname -r) 4.19.0-13-cloud-amd64 #### GNU/Linux Distribution, if applicable (cat /etc/os-release) _command result: cat /etc/os-release_ PRETTY_NAME="Debian GNU/Linux 10 (buster)" #### s3fs command line used, if applicable ``` /usr/local/bin/s3fs mys3 /mnt -o passwd_file=/root/.passwd-s3fs -o endpoint=ap-east-1 -d -d -f -o f2 -o curldbg ``` #### /etc/fstab entry, if applicable ``` ``` #### s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs) _if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_ ``` [CRT] s3fs_logger.cpp:LowSetLogLevel(201): change debug level from [CRT] to [INF] [CRT] s3fs_logger.cpp:LowSetLogLevel(201): change debug level from [INF] to [DBG] [INF] s3fs.cpp:set_mountpoint_attribute(3989): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755) [DBG] curl.cpp:InitMimeType(410): Try to load mime types from /etc/mime.types file. [DBG] curl.cpp:InitMimeType(415): The old mime types are cleared to load new mime types. [INF] curl.cpp:InitMimeType(438): Loaded mime information from /etc/mime.types [INF] fdcache_stat.cpp:CheckCacheFileStatTopDir(79): The path to cache top dir is empty, thus not need to check permission. FUSE library version: 2.9.9 nullpath_ok: 0 nopath: 0 utime_omit_ok: 0 unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0 INIT: 7.27 flags=0x003ffffb max_readahead=0x00020000 [INF] s3fs.cpp:s3fs_init(3300): init v1.87(commit:d1c638a) with OpenSSL [INF] s3fs.cpp:s3fs_check_service(3416): check services. [INF] curl.cpp:CheckBucket(3310): check a bucket. [DBG] curl_handlerpool.cpp:GetHandler(81): Get handler from pool: rest = 31 [INF] curl_util.cpp:prepare_url(223): URL is https://s3.amazonaws.com/mys3/ [INF] curl_util.cpp:prepare_url(256): URL changed is https://mys3.s3.amazonaws.com/ [DBG] curl.cpp:RequestPerform(2226): connecting to URL https://mys3.s3.amazonaws.com/ [INF] curl.cpp:insertV4Headers(2590): computing signature [GET] [/] [] [] [INF] curl_util.cpp:url_to_host(300): url is https://s3.amazonaws.com [CURL DBG] * Expire in 0 ms for 6 (transfer 0x5613c967f230) [CURL DBG] * Expire in 300000 ms for 2 (transfer 0x5613c967f230) [CURL DBG] * Uses proxy env variable https_proxy == 'http://172.20.0.248:3128' [CURL DBG] * Trying 172.20.0.248... [CURL DBG] * TCP_NODELAY set [CURL DBG] * Expire in 200 ms for 4 (transfer 0x5613c967f230) [CURL DBG] * Connected to 172.20.0.248 (172.20.0.248) port 3128 (#0) [CURL DBG] * allocate connect buffer! [CURL DBG] * Establish HTTP proxy tunnel to mys3.s3.amazonaws.com:443 [CURL DBG] > CONNECT mys3.s3.amazonaws.com:443 HTTP/1.1 [CURL DBG] > Host: mys3.s3.amazonaws.com:443 [CURL DBG] > User-Agent: s3fs/1.87 (commit hash d1c638a; OpenSSL) [CURL DBG] > Proxy-Connection: Keep-Alive [CURL DBG] > [CURL DBG] < HTTP/1.1 200 Connection established [CURL DBG] < [CURL DBG] * Proxy replied 200 to CONNECT request [CURL DBG] * CONNECT phase completed! [CURL DBG] * successfully set certificate verify locations: [CURL DBG] * CAfile: none CApath: /etc/ssl/certs [CURL DBG] * TLSv1.3 (OUT), TLS handshake, Client hello (1): [CURL DBG] * CONNECT phase completed! [CURL DBG] * CONNECT phase completed! [CURL DBG] * TLSv1.3 (IN), TLS handshake, Server hello (2): [CURL DBG] * TLSv1.2 (IN), TLS handshake, Certificate (11): [CURL DBG] * TLSv1.2 (IN), TLS handshake, Server key exchange (12): [CURL DBG] * TLSv1.2 (IN), TLS handshake, Server finished (14): [CURL DBG] * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): [CURL DBG] * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): [CURL DBG] * TLSv1.2 (OUT), TLS handshake, Finished (20): [CURL DBG] * TLSv1.2 (IN), TLS handshake, Finished (20): [CURL DBG] * SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256 [CURL DBG] * Server certificate: [CURL DBG] * subject: C=US; ST=Washington; L=Seattle; O=Amazon.com, Inc.; CN=*.s3.amazonaws.com [CURL DBG] * start date: Nov 9 00:00:00 2019 GMT [CURL DBG] * expire date: Mar 12 12:00:00 2021 GMT [CURL DBG] * subjectAltName: host "mys3.s3.amazonaws.com" matched cert's "*.s3.amazonaws.com" [CURL DBG] * issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert Baltimore CA-2 G2 [CURL DBG] * SSL certificate verify ok. [CURL DBG] > GET / HTTP/1.1 [CURL DBG] > Host: mys3.s3.amazonaws.com [CURL DBG] > User-Agent: s3fs/1.87 (commit hash d1c638a; OpenSSL) [CURL DBG] > Accept: */* [CURL DBG] > Authorization: AWS4-HMAC-SHA256 Credential=AKJSDOIWNBFU/20201230/ap-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=wefkwmnfhfbnm,fle,flwmnfwew [CURL DBG] > x-amz-content-sha256: fwifwnjkwlf,womfnwinfiwwhgwhjklw,m23b [CURL DBG] > x-amz-date: 20201230T145748Z [CURL DBG] > [CURL DBG] < HTTP/1.1 400 Bad Request [CURL DBG] < x-amz-bucket-region: ap-east-1 [CURL DBG] < x-amz-request-id: BC02CD607D9DA493 [CURL DBG] < x-amz-id-2: sdfnwkwlfw kmmKNJNJKLWMD:LWMDKNJBFWKK= [CURL DBG] < Content-Type: application/xml [CURL DBG] < Transfer-Encoding: chunked [CURL DBG] < Date: Wed, 30 Dec 2020 14:57:48 GMT [CURL DBG] < Connection: close [CURL DBG] < Server: AmazonS3 [CURL DBG] < [CURL DBG] * Closing connection 0 [ERR] curl.cpp:RequestPerform(2274): HTTP response code 400, returning EIO. Body Text: <?xml version="1.0" encoding="UTF-8"?> <Error><Code>IllegalLocationConstraintException</Code><Message>The ap-east-1 location constraint is incompatible for the region specific endpoint this request was sent to.</Message><RequestId>sadnafwlfkwef</RequestId><HostId>asdlfmwlnjwlkfmemfw;f =</HostId></Error> [ERR] curl.cpp:CheckBucket(3336): Check bucket failed, S3 response: <?xml version="1.0" encoding="UTF-8"?> <Error><Code>IllegalLocationConstraintException</Code><Message>The ap-east-1 location constraint is incompatible for the region specific endpoint this request was sent to.</Message><RequestId>aslkmdnfjkwlfmenfjw</RequestId><HostId>lkmnwkfkmlNIUBHJKNMLL=</HostId></Error> [CRT] s3fs.cpp:s3fs_check_service(3471): Failed to connect by sigv4, so retry to connect by signature version 2. [DBG] curl_handlerpool.cpp:ReturnHandler(103): Return handler to pool [INF] curl_handlerpool.cpp:ReturnHandler(110): Pool full: destroy the oldest handler [INF] curl.cpp:CheckBucket(3310): check a bucket. [DBG] curl_handlerpool.cpp:GetHandler(81): Get handler from pool: rest = 30 [INF] curl_util.cpp:prepare_url(223): URL is https://s3.amazonaws.com/tmys3/ [INF] curl_util.cpp:prepare_url(256): URL changed is https://mys3.s3.amazonaws.com/ [DBG] curl.cpp:RequestPerform(2226): connecting to URL https://mys3.s3.amazonaws.com/ [CURL DBG] * Expire in 0 ms for 6 (transfer 0x5613c967f230) [CURL DBG] * Expire in 300000 ms for 2 (transfer 0x5613c967f230) [CURL DBG] * Uses proxy env variable https_proxy == 'http://172.20.0.248:3128' [CURL DBG] * Hostname 172.20.0.248 was found in DNS cache [CURL DBG] * Trying 172.20.0.248... [CURL DBG] * TCP_NODELAY set [CURL DBG] * Expire in 200 ms for 4 (transfer 0x5613c967f230) [CURL DBG] * Connected to 172.20.0.248 (172.20.0.248) port 3128 (#1) [CURL DBG] * allocate connect buffer! [CURL DBG] * Establish HTTP proxy tunnel to mys3.s3.amazonaws.com:443 [CURL DBG] > CONNECT mys3.s3.amazonaws.com:443 HTTP/1.1 [CURL DBG] > Host: mys3.s3.amazonaws.com:443 [CURL DBG] > User-Agent: s3fs/1.87 (commit hash d1c638a; OpenSSL) [CURL DBG] > Proxy-Connection: Keep-Alive [CURL DBG] > [CURL DBG] < HTTP/1.1 200 Connection established [CURL DBG] < [CURL DBG] * Proxy replied 200 to CONNECT request [CURL DBG] * CONNECT phase completed! [CURL DBG] * successfully set certificate verify locations: [CURL DBG] * CAfile: none CApath: /etc/ssl/certs [CURL DBG] * SSL re-using session ID [CURL DBG] * TLSv1.3 (OUT), TLS handshake, Client hello (1): [CURL DBG] * CONNECT phase completed! [CURL DBG] * CONNECT phase completed! [CURL DBG] * TLSv1.3 (IN), TLS handshake, Server hello (2): [CURL DBG] * TLSv1.2 (IN), TLS handshake, Certificate (11): [CURL DBG] * TLSv1.2 (IN), TLS handshake, Server key exchange (12): [CURL DBG] * TLSv1.2 (IN), TLS handshake, Server finished (14): [CURL DBG] * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): [CURL DBG] * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): [CURL DBG] * TLSv1.2 (OUT), TLS handshake, Finished (20): [CURL DBG] * TLSv1.2 (IN), TLS handshake, Finished (20): [CURL DBG] * old SSL session ID is stale, removing [CURL DBG] * SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256 [CURL DBG] * Server certificate: [CURL DBG] * subject: C=US; ST=Washington; L=Seattle; O=Amazon.com, Inc.; CN=*.s3.amazonaws.com [CURL DBG] * start date: Nov 9 00:00:00 2019 GMT [CURL DBG] * expire date: Mar 12 12:00:00 2021 GMT [CURL DBG] * subjectAltName: host "mys3.s3.amazonaws.com" matched cert's "*.s3.amazonaws.com" [CURL DBG] * issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert Baltimore CA-2 G2 [CURL DBG] * SSL certificate verify ok. [CURL DBG] > GET / HTTP/1.1 [CURL DBG] > Host: mys3s3.amazonaws.com [CURL DBG] > User-Agent: s3fs/1.87 (commit hash d1c638a; OpenSSL) [CURL DBG] > Accept: */* [CURL DBG] > Authorization: AWS ;wflmkwnjflkf;ljaNKHBJNKLlkJNK/4whWr7BTCWiWq22t0Jv/lo= [CURL DBG] > Date: Wed, 30 Dec 2020 14:57:49 GMT [CURL DBG] > [CURL DBG] < HTTP/1.1 400 Bad Request [CURL DBG] < x-amz-bucket-region: ap-east-1 [CURL DBG] < x-amz-request-id: wlekjnsakmldkNJKNKJ [CURL DBG] < x-amz-id-2: slaniJOIJOSJDW++UO/wOks5be3T1/wefkmiUHYBNM+wekfmlfew+lskamdKKKM= [CURL DBG] < Content-Type: application/xml [CURL DBG] < Transfer-Encoding: chunked [CURL DBG] < Date: Wed, 30 Dec 2020 14:57:49 GMT [CURL DBG] < Connection: close [CURL DBG] < Server: AmazonS3 [CURL DBG] < [CURL DBG] * Closing connection 1 [ERR] curl.cpp:RequestPerform(2274): HTTP response code 400, returning EIO. Body Text: <?xml version="1.0" encoding="UTF-8"?> <Error><Code>IllegalLocationConstraintException</Code><Message>The ap-east-1 location constraint is incompatible for the region specific endpoint this request was sent to.</Message><RequestId>LKJNBKLK</RequestId><HostId>wkjnfjnbBBNON++UO/wOks5be3T1/i23n68E9ErKCE48+LKJNjkwlfm+wel;fmknjNBYUGBH=</HostId></Error> [ERR] curl.cpp:CheckBucket(3336): Check bucket failed, S3 response: <?xml version="1.0" encoding="UTF-8"?> <Error><Code>IllegalLocationConstraintException</Code><Message>The ap-east-1 location constraint is incompatible for the region specific endpoint this request was sent to.</Message><RequestId>KLJHGJNIMK</RequestId><HostId>IJOIMNLK++UO/:MJKLKM/i23n68E9ErKCE48+L:KMN+EIqUWv0ngV58WMPgww=</HostId></Error> [CRT] s3fs.cpp:s3fs_check_service(3483): Bad Request(host=https://s3.amazonaws.com) - result of checking service. [DBG] curl_handlerpool.cpp:ReturnHandler(103): Return handler to pool [ERR] s3fs.cpp:s3fs_exit_fuseloop(3290): 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(3358): destroy ``` ### Details about issue
kerem closed this issue 2026-03-04 01:48:50 +03:00
kerem commented 2026-03-04 01:48:51 +03:00
Author
Owner
Copy link

@gaul commented on GitHub (Dec 30, 2020):

Could you also add -o url=s3.ap-east-1.amazonaws.com? I believe that newly-created buckets take some time to propagate the DNS update. s3fs could also be smarter about this.

<!-- gh-comment-id:752666718 --> @gaul commented on GitHub (Dec 30, 2020): Could you also add `-o url=s3.ap-east-1.amazonaws.com`? I believe that newly-created buckets take some time to propagate the DNS update. s3fs could also be smarter about this.
kerem commented 2026-03-04 01:48:51 +03:00
Author
Owner
Copy link

@ntulp commented on GitHub (Dec 31, 2020):

Could you also add -o url=s3.ap-east-1.amazonaws.com? I believe that newly-created buckets take some time to propagate the DNS update. s3fs could also be smarter about this.

you save me !! -o url=s3.ap-east-1.amazonaws.com it's work,
this args was not found during debugging , thank you

<!-- gh-comment-id:752830589 --> @ntulp commented on GitHub (Dec 31, 2020): > Could you also add `-o url=s3.ap-east-1.amazonaws.com`? I believe that newly-created buckets take some time to propagate the DNS update. s3fs could also be smarter about this. you save me !! `-o url=s3.ap-east-1.amazonaws.com` it's work, this args was not found during debugging , thank you
kerem commented 2026-03-04 01:48:51 +03:00
Author
Owner
Copy link

@martinheidegger commented on GitHub (Aug 17, 2021):

Currently - version 1.89 - I need to prefix the url with "https" to -o url=https://s3.ap-east-1.amazonaws.com on Amazon Linux, but even then: the result is "The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.".

<!-- gh-comment-id:900005210 --> @martinheidegger commented on GitHub (Aug 17, 2021): Currently - version 1.89 - I need to prefix the url with "https" to `-o url=https://s3.ap-east-1.amazonaws.com` on Amazon Linux, but even then: the result is "The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.".
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#792
No description provided.