[GH-ISSUE #653] Cannot mount a bucket that has a dot(.) in its name even though I use "use_path_request_style" #370

Closed
opened 2026-03-04 01:44:52 +03:00 by kerem · 5 comments
Owner

Originally created by @MariusStanciu95 on GitHub (Oct 3, 2017).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/653

I'm using 1.82 or newer and I keep getting unknown option "use_path_request_style" or "endpoint".

I've read that if my bucket has a dot(.) inside its name , I should use the "use_path_request_style" option.

My call when I try mounting:

s3fs bucket.name /mnt/s3 -o passwd_file=/etc/passwd-s3fs -endpoint=eu-west-2 -o use_path_request_style

Did anyone encounter this problem? Any suggestions (besides renaming the bucket, because I'm not allowed to do that) ?

Originally created by @MariusStanciu95 on GitHub (Oct 3, 2017). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/653 I'm using 1.82 or newer and I keep getting unknown option "use_path_request_style" or "endpoint". I've read that if my bucket has a dot(.) inside its name , I should use the "use_path_request_style" option. My call when I try mounting: s3fs bucket.name /mnt/s3 -o passwd_file=/etc/passwd-s3fs -endpoint=eu-west-2 -o use_path_request_style Did anyone encounter this problem? Any suggestions (besides renaming the bucket, because I'm not allowed to do that) ?
kerem closed this issue 2026-03-04 01:44:52 +03:00
Author
Owner

@gaul commented on GitHub (Oct 3, 2017):

Please post the logs from the failed command.

<!-- gh-comment-id:333916854 --> @gaul commented on GitHub (Oct 3, 2017): Please post the logs from the failed command.
Author
Owner

@djdevin commented on GitHub (Nov 6, 2017):

I posted logs in #626

<!-- gh-comment-id:342217046 --> @djdevin commented on GitHub (Nov 6, 2017): I posted logs in #626
Author
Owner

@Vacilando commented on GitHub (Nov 9, 2017):

Same problem here. If the bucket name contains a dot, s3fs mount fails (no error message).

<!-- gh-comment-id:343295329 --> @Vacilando commented on GitHub (Nov 9, 2017): Same problem here. If the bucket name contains a dot, s3fs mount fails (no error message).
Author
Owner

@stevesuh commented on GitHub (Dec 6, 2017):

Same here. This worked back in August.

<!-- gh-comment-id:349691607 --> @stevesuh commented on GitHub (Dec 6, 2017): Same here. This worked back in August.
Author
Owner

@ggtakec commented on GitHub (Mar 29, 2019):

We kept this issue open for a long time.
Please try again with the latest version and you can see https://github.com/s3fs-fuse/s3fs-fuse/wiki/FAQ#q-https-connecting-failed-if-bucket-name-includes-dot- .

I will close this, but if the problem persists, please reopen or post a new issue.

<!-- gh-comment-id:477831236 --> @ggtakec commented on GitHub (Mar 29, 2019): We kept this issue open for a long time. Please try again with the latest version and you can see https://github.com/s3fs-fuse/s3fs-fuse/wiki/FAQ#q-https-connecting-failed-if-bucket-name-includes-dot- . I will close this, but if the problem persists, please reopen or post a new issue.
Sign in to join this conversation.
No milestone
No project
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#370
No description provided.