[GH-ISSUE #227] mount s3fs eroor 404 #125

New issue

Closed

opened 2026-03-04 01:42:21 +03:00 by kerem · 28 comments

kerem commented 2026-03-04 01:42:21 +03:00

Owner

Copy link

Originally created by @novoxd on GitHub (Aug 11, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/227

s3fs instaled from git, os ubuntu

when I use:
s3fs koshka-owncloud /s3mnt -ouse_cache=/tmp/cache -d -f
I get:
set_moutpoint_attribute(3291): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40777)
s3fs_init(2595): init
s3fs_check_service(2894): check services.
CheckBucket(2228): check a bucket.
RequestPerform(1467): connecting to URL http://koshka-owncloud.s3.amazonaws.com/
RequestPerform(1595): ### CURLE_HTTP_RETURNED_ERROR
RequestPerform(1600): HTTP response code =400
s3fs: Failed to access bucket.

when I use:
s3fs koshka-owncloud /s3mnt -ouse_cache=/tmp/cache -ouse_sse=/etc/passwd-s3fs -ourl=http://s3-eu-west-1.amazonaws.com -d -f

I get:
set_moutpoint_attribute(3291): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40777)
s3fs_init(2595): init
s3fs_check_service(2894): check services.
CheckBucket(2228): check a bucket.
RequestPerform(1467): connecting to URL http://koshka-owncloud.s3-eu-west-1.amazonaws.com/
RequestPerform(1483): HTTP response code 301
^Cs3fs_destroy(2628): destroy

after 301 it suspeneds

the key format in ~/.passwd-s3fs is ok

Originally created by @novoxd on GitHub (Aug 11, 2015). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/227 s3fs instaled from git, os ubuntu when I use: s3fs koshka-owncloud /s3mnt -ouse_cache=/tmp/cache -d -f I get: set_moutpoint_attribute(3291): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40777) s3fs_init(2595): init s3fs_check_service(2894): check services. CheckBucket(2228): check a bucket. RequestPerform(1467): connecting to URL http://koshka-owncloud.s3.amazonaws.com/ RequestPerform(1595): ### CURLE_HTTP_RETURNED_ERROR RequestPerform(1600): HTTP response code =400 s3fs: Failed to access bucket. when I use: s3fs koshka-owncloud /s3mnt -ouse_cache=/tmp/cache -ouse_sse=/etc/passwd-s3fs -ourl=http://s3-eu-west-1.amazonaws.com -d -f I get: set_moutpoint_attribute(3291): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40777) s3fs_init(2595): init s3fs_check_service(2894): check services. CheckBucket(2228): check a bucket. RequestPerform(1467): connecting to URL http://koshka-owncloud.s3-eu-west-1.amazonaws.com/ RequestPerform(1483): HTTP response code 301 ^Cs3fs_destroy(2628): destroy after 301 it suspeneds the key format in ~/.passwd-s3fs is ok

kerem closed this issue 2026-03-04 01:42:21 +03:00

kerem commented 2026-03-04 01:42:22 +03:00

Author

Owner

Copy link

@Doerge commented on GitHub (Aug 11, 2015):

301 means moved. It says in the response that it is located in the eu-central region:

<Error>
  <Code>PermanentRedirect</Code>
    <Message>
    The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
    </Message>
    <Bucket>koshka-owncloud</Bucket>
    <Endpoint>koshka-owncloud.s3.eu-central-1.amazonaws.com</Endpoint>
    <RequestId>F209B49176187E86</RequestId>
    <HostId>
      AhvzxSDiG91Uu0wjJwsJgRvy2n/+y/bRNiJXQiTbNJyd4X6+ahf6R2lz6LxSJSOpUk1BX7xzlV8=
    </HostId>
</Error>

try using koshka-owncloud.s3.eu-central-1.amazonaws.com.

<!-- gh-comment-id:130033734 --> @Doerge commented on GitHub (Aug 11, 2015): 301 means moved. It says in the response that it is located in the eu-central region: ``` <Error> <Code>PermanentRedirect</Code> <Message> The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint. </Message> <Bucket>koshka-owncloud</Bucket> <Endpoint>koshka-owncloud.s3.eu-central-1.amazonaws.com</Endpoint> <RequestId>F209B49176187E86</RequestId> <HostId> AhvzxSDiG91Uu0wjJwsJgRvy2n/+y/bRNiJXQiTbNJyd4X6+ahf6R2lz6LxSJSOpUk1BX7xzlV8= </HostId> </Error> ``` try using `koshka-owncloud.s3.eu-central-1.amazonaws.com`.

kerem commented 2026-03-04 01:42:22 +03:00

Author

Owner

Copy link

@novoxd commented on GitHub (Aug 11, 2015):

s3fs koshka-owncloud /s3mnt -ouse_cache=/tmp/cache -ouse_sse=/etc/passwd-s3fs -ourl=http://koshka-owncloud.s3.eu-central-1.amazonaws.com -d -f

set_moutpoint_attribute(3291): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40777)
s3fs_init(2595): init
s3fs_check_service(2894): check services.
CheckBucket(2228): check a bucket.
RequestPerform(1467): connecting to URL http://koshka-owncloud.koshka-owncloud.s3.eu-central-1.amazonaws.com/koshka-owncloud/.s3.eu-central-1.amazonaws.com/koshka-owncloud/
RequestPerform(1595): ### CURLE_HTTP_RETURNED_ERROR
RequestPerform(1600): HTTP response code =400
s3fs: Failed to access bucket.

<!-- gh-comment-id:130036367 --> @novoxd commented on GitHub (Aug 11, 2015): s3fs koshka-owncloud /s3mnt -ouse_cache=/tmp/cache -ouse_sse=/etc/passwd-s3fs -ourl=http://koshka-owncloud.s3.eu-central-1.amazonaws.com -d -f set_moutpoint_attribute(3291): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40777) s3fs_init(2595): init s3fs_check_service(2894): check services. CheckBucket(2228): check a bucket. RequestPerform(1467): connecting to URL http://koshka-owncloud.koshka-owncloud.s3.eu-central-1.amazonaws.com/koshka-owncloud/.s3.eu-central-1.amazonaws.com/koshka-owncloud/ RequestPerform(1595): ### CURLE_HTTP_RETURNED_ERROR RequestPerform(1600): HTTP response code =400 s3fs: Failed to access bucket.

kerem commented 2026-03-04 01:42:22 +03:00

Author

Owner

Copy link

@kahing commented on GitHub (Aug 11, 2015):

try s3.eu-central-1.amazonaws.com without the bucket:

s3fs koshka-owncloud /s3mnt -ouse_cache=/tmp/cache -ouse_sse=/etc/passwd-s3fs -ourl=http://s3.eu-central-1.amazonaws.com -d -f

<!-- gh-comment-id:130039351 --> @kahing commented on GitHub (Aug 11, 2015): try s3.eu-central-1.amazonaws.com without the bucket: ``` s3fs koshka-owncloud /s3mnt -ouse_cache=/tmp/cache -ouse_sse=/etc/passwd-s3fs -ourl=http://s3.eu-central-1.amazonaws.com -d -f ```

kerem commented 2026-03-04 01:42:22 +03:00

Author

Owner

Copy link

@novoxd commented on GitHub (Aug 11, 2015):

s3fs koshka-owncloud /s3mnt -ouse_cache=/tmp/cache -ouse_sse=/etc/passwd-s3fs -ourl=http://s3.eu-central-1.amazonaws.com -d -f

set_moutpoint_attribute(3291): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40777)

s3fs_init(2595): init
s3fs_check_service(2894): check services.
CheckBucket(2228): check a bucket.
RequestPerform(1467): connecting to URL http://koshka-owncloud.s3.eu-central-1.amazonaws.com/
RequestPerform(1595): ### CURLE_HTTP_RETURNED_ERROR
RequestPerform(1600): HTTP response code =400
s3fs: Failed to access bucket.

<!-- gh-comment-id:130045017 --> @novoxd commented on GitHub (Aug 11, 2015): s3fs koshka-owncloud /s3mnt -ouse_cache=/tmp/cache -ouse_sse=/etc/passwd-s3fs -ourl=http://s3.eu-central-1.amazonaws.com -d -f ``` set_moutpoint_attribute(3291): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40777) ``` s3fs_init(2595): init s3fs_check_service(2894): check services. CheckBucket(2228): check a bucket. RequestPerform(1467): connecting to URL http://koshka-owncloud.s3.eu-central-1.amazonaws.com/ RequestPerform(1595): ### CURLE_HTTP_RETURNED_ERROR RequestPerform(1600): HTTP response code =400 s3fs: Failed to access bucket.

kerem commented 2026-03-04 01:42:22 +03:00

Author

Owner

Copy link

@kahing commented on GitHub (Aug 11, 2015):

did you mean to do -ouse_sse=/etc/passwd-s3fs or -o passwd_file?

<!-- gh-comment-id:130047376 --> @kahing commented on GitHub (Aug 11, 2015): did you mean to do -ouse_sse=/etc/passwd-s3fs or -o passwd_file?

kerem commented 2026-03-04 01:42:22 +03:00

Author

Owner

Copy link

@novoxd commented on GitHub (Aug 11, 2015):

you are right, changed -ouse_sse to -opasswd_file, nofing changes

<!-- gh-comment-id:130049831 --> @novoxd commented on GitHub (Aug 11, 2015): you are right, changed -ouse_sse to -opasswd_file, nofing changes

kerem commented 2026-03-04 01:42:22 +03:00

Author

Owner

Copy link

@kahing commented on GitHub (Aug 11, 2015):

Have you double checked your access keys? It should be in the format of

BUCKET:BUCKET_ACCESSKEY:BUCKET_CREDENTIAL
DEFAULT_ACCESSKEY:DEFAULT_CREDENTIAL

<!-- gh-comment-id:130050682 --> @kahing commented on GitHub (Aug 11, 2015): Have you double checked your access keys? It should be in the format of ``` BUCKET:BUCKET_ACCESSKEY:BUCKET_CREDENTIAL DEFAULT_ACCESSKEY:DEFAULT_CREDENTIAL ```

kerem commented 2026-03-04 01:42:23 +03:00

Author

Owner

Copy link

@novoxd commented on GitHub (Aug 11, 2015):

my ~/.passwd-s3fs (permissions 600):
koshka-owncloud:my_BUCKET_ACCESSKEY:my_BUCKET_CREDENTIAL
my_BUCKET_ACCESSKEY:my_BUCKET_CREDENTIAL

<!-- gh-comment-id:130056328 --> @novoxd commented on GitHub (Aug 11, 2015): my ~/.passwd-s3fs (permissions 600): koshka-owncloud:my_BUCKET_ACCESSKEY:my_BUCKET_CREDENTIAL my_BUCKET_ACCESSKEY:my_BUCKET_CREDENTIAL

kerem commented 2026-03-04 01:42:23 +03:00

Author

Owner

Copy link

@kahing commented on GitHub (Aug 11, 2015):

could you try specifying -d -d to get more debug output?

<!-- gh-comment-id:130056872 --> @kahing commented on GitHub (Aug 11, 2015): could you try specifying -d -d to get more debug output?

kerem commented 2026-03-04 01:42:23 +03:00

Author

Owner

Copy link

@novoxd commented on GitHub (Aug 11, 2015):

s3fs koshka-owncloud /s3mnt -ouse_cache=/tmp/cache -ourl=http://s3.eu-central-1.amazonaws.com -d -d -f
set_moutpoint_attribute(3291): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40777)
FUSE library version: 2.9.2
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
INIT: 7.22
flags=0x0000f7fb
max_readahead=0x00020000
s3fs_init(2595): init
s3fs_check_service(2894): check services.
CheckBucket(2228): check a bucket.
RequestPerform(1467): connecting to URL http://koshka-owncloud.s3.eu-central-1.amazonaws.com/
RequestPerform(1595): ### CURLE_HTTP_RETURNED_ERROR
RequestPerform(1600): HTTP response code =400
s3fs: Failed to access bucket.

<!-- gh-comment-id:130057089 --> @novoxd commented on GitHub (Aug 11, 2015): s3fs koshka-owncloud /s3mnt -ouse_cache=/tmp/cache -ourl=http://s3.eu-central-1.amazonaws.com -d -d -f set_moutpoint_attribute(3291): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40777) FUSE library version: 2.9.2 nullpath_ok: 0 nopath: 0 utime_omit_ok: 0 unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0 INIT: 7.22 flags=0x0000f7fb max_readahead=0x00020000 s3fs_init(2595): init s3fs_check_service(2894): check services. CheckBucket(2228): check a bucket. RequestPerform(1467): connecting to URL http://koshka-owncloud.s3.eu-central-1.amazonaws.com/ RequestPerform(1595): ### CURLE_HTTP_RETURNED_ERROR RequestPerform(1600): HTTP response code =400 s3fs: Failed to access bucket.

kerem commented 2026-03-04 01:42:23 +03:00

Author

Owner

Copy link

@novoxd commented on GitHub (Aug 11, 2015):

I will try to catch the http reqest to see what's happening

<!-- gh-comment-id:130057512 --> @novoxd commented on GitHub (Aug 11, 2015): I will try to catch the http reqest to see what's happening

kerem commented 2026-03-04 01:42:23 +03:00

Author

Owner

Copy link

@gaul commented on GitHub (Aug 11, 2015):

@novoxudonoser Can you add -o curldbg to dump the HTTP request?

<!-- gh-comment-id:130057906 --> @gaul commented on GitHub (Aug 11, 2015): @novoxudonoser Can you add `-o curldbg` to dump the HTTP request?

kerem commented 2026-03-04 01:42:23 +03:00

Author

Owner

Copy link

@novoxd commented on GitHub (Aug 11, 2015):

s3fs koshka-owncloud /s3mnt -ouse_cache=/tmp/cache -ourl=http://s3.eu-central-1.amazonaws.com -d -d -f -o curldbg
set_moutpoint_attribute(3291): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40777)
FUSE library version: 2.9.2
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
INIT: 7.22
flags=0x0000f7fb
max_readahead=0x00020000
s3fs_init(2595): init
s3fs_check_service(2894): check services.
CheckBucket(2228): check a bucket.
RequestPerform(1467): connecting to URL http://koshka-owncloud.s3.eu-central-1.amazonaws.com/

• Hostname was NOT found in DNS cache

• Trying 54.231.194.50...

• Connected to koshka-owncloud.s3.eu-central-1.amazonaws.com (54.231.194.50) port 80 (#0)

  GET / HTTP/1.1
  Host: koshka-owncloud.s3.eu-central-1.amazonaws.com
  Accept: /
  Authorization: AWS AKIAJDIBWADNFCHS5EIA:gym3UoxBTCki7TBP0LQkbpmUvT8=
  Date: Tue, 11 Aug 2015 20:33:28 GMT

• The requested URL returned error: 400 Bad Request

• Closing connection 0
  RequestPerform(1595): ### CURLE_HTTP_RETURNED_ERROR
  RequestPerform(1600): HTTP response code =400
  s3fs: Failed to access bucket.

<!-- gh-comment-id:130058639 --> @novoxd commented on GitHub (Aug 11, 2015): s3fs koshka-owncloud /s3mnt -ouse_cache=/tmp/cache -ourl=http://s3.eu-central-1.amazonaws.com -d -d -f -o curldbg set_moutpoint_attribute(3291): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40777) FUSE library version: 2.9.2 nullpath_ok: 0 nopath: 0 utime_omit_ok: 0 unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0 INIT: 7.22 flags=0x0000f7fb max_readahead=0x00020000 s3fs_init(2595): init s3fs_check_service(2894): check services. CheckBucket(2228): check a bucket. RequestPerform(1467): connecting to URL http://koshka-owncloud.s3.eu-central-1.amazonaws.com/ - Hostname was NOT found in DNS cache - Trying 54.231.194.50... - Connected to koshka-owncloud.s3.eu-central-1.amazonaws.com (54.231.194.50) port 80 (#0) > GET / HTTP/1.1 > Host: koshka-owncloud.s3.eu-central-1.amazonaws.com > Accept: _/_ > Authorization: AWS AKIAJDIBWADNFCHS5EIA:gym3UoxBTCki7TBP0LQkbpmUvT8= > Date: Tue, 11 Aug 2015 20:33:28 GMT - The requested URL returned error: 400 Bad Request - Closing connection 0 RequestPerform(1595): ### CURLE_HTTP_RETURNED_ERROR RequestPerform(1600): HTTP response code =400 s3fs: Failed to access bucket.

kerem commented 2026-03-04 01:42:23 +03:00

Author

Owner

Copy link

@novoxd commented on GitHub (Aug 11, 2015):

that is strange my BUCKET_CREDENTIAL is not gym3UoxBTCki7TBP0LQkbpmUvT8= , it is the crypto hash?

<!-- gh-comment-id:130058998 --> @novoxd commented on GitHub (Aug 11, 2015): that is strange my BUCKET_CREDENTIAL is not gym3UoxBTCki7TBP0LQkbpmUvT8= , it is the crypto hash?

kerem commented 2026-03-04 01:42:23 +03:00

Author

Owner

Copy link

@gaul commented on GitHub (Aug 11, 2015):

@novoxudonoser gym3UoxBTCki7TBP0LQkbpmUvT8= is the HMAC signature, not your secret key. Each request derives its unique signature from the key but does not include it in the request.

<!-- gh-comment-id:130060316 --> @gaul commented on GitHub (Aug 11, 2015): @novoxudonoser `gym3UoxBTCki7TBP0LQkbpmUvT8=` is the HMAC signature, not your secret key. Each request derives its unique signature from the key but does not include it in the request.

kerem commented 2026-03-04 01:42:23 +03:00

Author

Owner

Copy link

@novoxd commented on GitHub (Aug 11, 2015):

@andrewgaul ok, any idea what to do next?

<!-- gh-comment-id:130060788 --> @novoxd commented on GitHub (Aug 11, 2015): @andrewgaul ok, any idea what to do next?

kerem commented 2026-03-04 01:42:23 +03:00

Author

Owner

Copy link

@kahing commented on GitHub (Aug 11, 2015):

double check that you are using s3fs from git. It's doing v2 auth but frankfurt only supports v4.

<!-- gh-comment-id:130062320 --> @kahing commented on GitHub (Aug 11, 2015): double check that you are using s3fs from git. It's doing v2 auth but frankfurt only supports v4.

kerem commented 2026-03-04 01:42:23 +03:00

Author

Owner

Copy link

@kahing commented on GitHub (Aug 11, 2015):

what does which s3fs return?

<!-- gh-comment-id:130064566 --> @kahing commented on GitHub (Aug 11, 2015): what does `which s3fs` return?

kerem commented 2026-03-04 01:42:23 +03:00

Author

Owner

Copy link

@novoxd commented on GitHub (Aug 11, 2015):

@kahing I uset this to install:

sudo apt-get install build-essential git libfuse-dev libcurl4-openssl-dev libxml2-dev mime-support >automake libtool
sudo apt-get install pkg-config libssl-dev # See (_3)
git clone https://github.com/s3fs-fuse/s3fs-fuse
cd s3fs-fuse/
./autogen.sh
./configure --prefix=/usr --with-openssl # See (_1)
make
sudo make install

<!-- gh-comment-id:130064926 --> @novoxd commented on GitHub (Aug 11, 2015): @kahing I uset this to install: > sudo apt-get install build-essential git libfuse-dev libcurl4-openssl-dev libxml2-dev mime-support >automake libtool > sudo apt-get install pkg-config libssl-dev # See (_3) > git clone https://github.com/s3fs-fuse/s3fs-fuse > cd s3fs-fuse/ > ./autogen.sh > ./configure --prefix=/usr --with-openssl # See (_1) > make > sudo make install

kerem commented 2026-03-04 01:42:23 +03:00

Author

Owner

Copy link

@novoxd commented on GitHub (Aug 11, 2015):

@kahing

which s3fs
/usr/local/bin/s3fs

<!-- gh-comment-id:130065288 --> @novoxd commented on GitHub (Aug 11, 2015): @kahing > which s3fs > /usr/local/bin/s3fs

kerem commented 2026-03-04 01:42:24 +03:00

Author

Owner

Copy link

@novoxd commented on GitHub (Aug 11, 2015):

s3fs --version
Amazon Simple Storage Service File System 1.74
Copyright (C) 2010 Randy Rizun rrizun@gmail.com
License GPL2: GNU GPL version 2 http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

<!-- gh-comment-id:130065776 --> @novoxd commented on GitHub (Aug 11, 2015): s3fs --version Amazon Simple Storage Service File System 1.74 Copyright (C) 2010 Randy Rizun rrizun@gmail.com License GPL2: GNU GPL version 2 http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.

kerem commented 2026-03-04 01:42:24 +03:00

Author

Owner

Copy link

@kahing commented on GitHub (Aug 11, 2015):

you are using s3fs from /usr/local/bin/s3fs but you are installing s3fs to /usr/bin. Either remove the copy from /usr/local/bin or overwrite that with the new version.

<!-- gh-comment-id:130067834 --> @kahing commented on GitHub (Aug 11, 2015): you are using s3fs from `/usr/local/bin/s3fs` but you are installing `s3fs` to /usr/bin. Either remove the copy from `/usr/local/bin` or overwrite that with the new version.

kerem commented 2026-03-04 01:42:24 +03:00

Author

Owner

Copy link

@novoxd commented on GitHub (Aug 11, 2015):

That it! Thank you a lot man, it is time to laugh at me.

<!-- gh-comment-id:130074693 --> @novoxd commented on GitHub (Aug 11, 2015): That it! Thank you a lot man, it is time to laugh at me. 

kerem commented 2026-03-04 01:42:24 +03:00

Author

Owner

Copy link

@novoxd commented on GitHub (Aug 11, 2015):

By the way, what is the bigest filesize now? and what about metadata caching?

<!-- gh-comment-id:130078113 --> @novoxd commented on GitHub (Aug 11, 2015): By the way, what is the bigest filesize now? and what about metadata caching?

kerem commented 2026-03-04 01:42:24 +03:00

Author

Owner

Copy link

@kahing commented on GitHub (Aug 11, 2015):

there are max_stat_cache_size and stat_cache_expire options to control metadata caching. It's been tested with files over 5GB but I am not sure what's the biggest file size it would actually work with. Renaming large files doesn't currently work, pending https://github.com/s3fs-fuse/s3fs-fuse/pull/213

<!-- gh-comment-id:130079315 --> @kahing commented on GitHub (Aug 11, 2015): there are max_stat_cache_size and stat_cache_expire options to control metadata caching. It's been tested with files over 5GB but I am not sure what's the biggest file size it would actually work with. Renaming large files doesn't currently work, pending https://github.com/s3fs-fuse/s3fs-fuse/pull/213

kerem commented 2026-03-04 01:42:24 +03:00

Author

Owner

Copy link

@gaul commented on GitHub (Aug 21, 2015):

@novoxudonoser Can you close this issue?

<!-- gh-comment-id:133283685 --> @gaul commented on GitHub (Aug 21, 2015): @novoxudonoser Can you close this issue?

kerem commented 2026-03-04 01:42:24 +03:00

Author

Owner

Copy link

@goelmk commented on GitHub (May 21, 2017):

Hi @kahing,

I 'm facing the same issue and followed your conversation with @novoxudonoser. It's been very helpful until towards the end where you concluded the location / version of s3fs is incorrect for being referenced from a wrong location. That's not the case with me and hence my problem remains unresolved. But, it seems I'm very close to it. If you can help me in this regard, it will be much appreciated.

I'm getting AuthorizedHeaderMalformed error. Here is the curl response:

< Content-Type: application/xml
< Transfer-Encoding: chunked
< Date: Sun, 21 May 2017 02:42:45 GMT
< Connection: close
* Server AmazonS3 is not blacklisted
< Server: AmazonS3
<
* Closing connection 0
[INF]       curl.cpp:RequestPerform(1952): HTTP response code 400 was returned, returning EIO.
[ERR] curl.cpp:CheckBucket(2953): 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 'us-east-2'</Message><Region>us-east-2</Region><RequestId>43EF790094C0617E</RequestId><HostId>2vdXX9VcRTMRuWyVVaKR3l2SSWvUEyMy6qblbjn0wIBdDrxLWGdcyb94l3+t27v/DwplBpKMrtM=</HostId></Error>
[CRT] s3fs.cpp:s3fs_check_service(3775): Could not connect wrong region us-east-1, so retry to connect region us-east-2.
[INF]       curl.cpp:CheckBucket(2914): check a bucket.
[INF]       curl.cpp:prepare_url(4205): URL is http://s3.us-east-2.amazonaws.com/mybucket/
[INF]       curl.cpp:prepare_url(4237): URL changed is http://mybucket.s3.us-east-2.amazonaws.com/
[INF]       curl.cpp:insertV4Headers(2267): computing signature [GET] [/] [] []
[INF]       curl.cpp:url_to_host(100): url is http://s3.us-east-2.amazonaws.com
* Hostname was found in DNS cache
*   Trying 52.92.77.16...
* Connected to mybucket.s3.us-east-2.amazonaws.com (52.92.77.16) port 80 (#1)
> GET / HTTP/1.1
User-Agent: s3fs/1.82 (commit hash ae4caa9; OpenSSL)

Look forward to your guidance and help in this regard.

Thanks,
Manoj

<!-- gh-comment-id:302911880 --> @goelmk commented on GitHub (May 21, 2017): Hi @kahing, I 'm facing the same issue and followed your conversation with @novoxudonoser. It's been very helpful until towards the end where you concluded the location / version of s3fs is incorrect for being referenced from a wrong location. That's not the case with me and hence my problem remains unresolved. But, it seems I'm very close to it. If you can help me in this regard, it will be much appreciated. I'm getting AuthorizedHeaderMalformed error. Here is the curl response: ``` < Content-Type: application/xml < Transfer-Encoding: chunked < Date: Sun, 21 May 2017 02:42:45 GMT < Connection: close * Server AmazonS3 is not blacklisted < Server: AmazonS3 < * Closing connection 0 [INF] curl.cpp:RequestPerform(1952): HTTP response code 400 was returned, returning EIO. [ERR] curl.cpp:CheckBucket(2953): 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 'us-east-2'</Message><Region>us-east-2</Region><RequestId>43EF790094C0617E</RequestId><HostId>2vdXX9VcRTMRuWyVVaKR3l2SSWvUEyMy6qblbjn0wIBdDrxLWGdcyb94l3+t27v/DwplBpKMrtM=</HostId></Error> [CRT] s3fs.cpp:s3fs_check_service(3775): Could not connect wrong region us-east-1, so retry to connect region us-east-2. [INF] curl.cpp:CheckBucket(2914): check a bucket. [INF] curl.cpp:prepare_url(4205): URL is http://s3.us-east-2.amazonaws.com/mybucket/ [INF] curl.cpp:prepare_url(4237): URL changed is http://mybucket.s3.us-east-2.amazonaws.com/ [INF] curl.cpp:insertV4Headers(2267): computing signature [GET] [/] [] [] [INF] curl.cpp:url_to_host(100): url is http://s3.us-east-2.amazonaws.com * Hostname was found in DNS cache * Trying 52.92.77.16... * Connected to mybucket.s3.us-east-2.amazonaws.com (52.92.77.16) port 80 (#1) > GET / HTTP/1.1 User-Agent: s3fs/1.82 (commit hash ae4caa9; OpenSSL) ``` Look forward to your guidance and help in this regard. Thanks, Manoj

kerem commented 2026-03-04 01:42:24 +03:00

Author

Owner

Copy link

@gaul commented on GitHub (May 21, 2017):

@goelmk Please open a new issue and include the flags you launched s3fs with.

<!-- gh-comment-id:302915307 --> @gaul commented on GitHub (May 21, 2017): @goelmk Please open a new issue and include the flags you launched s3fs with.

kerem referenced this issue 2026-03-04 01:44:47 +03:00

[GH-ISSUE #643] With unnecessary equal in POST uploads url argment #366

kerem referenced this issue 2026-03-04 01:53:33 +03:00

[PR #134] [MERGED] Include Content-Type in complete MPU V2 signature #1356

kerem referenced this issue 2026-03-04 02:01:01 +03:00

[PR #567] [MERGED] Do not send ACL unless overridden #1552

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

Subscribe

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#125

No description provided.