[GH-ISSUE #629] Cannot resolve IP address in URL option #359

New issue

Closed

opened 2026-03-04 01:44:44 +03:00 by kerem · 4 comments

kerem commented

2026-03-04 01:44:44 +03:00

Owner

Originally created by @kunallillaney on GitHub (Aug 9, 2017).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/629

Additional Information

The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.

Version of s3fs being used (s3fs --version)
1.82
Version of fuse being used (pkg-config --modversion fuse)
2.9.2
System information (uname -a)
3.10.0-514.26.2.el7.x86_64
s3fs command line used (if applicable)

s3fs testfs /data/testfs -d -o url=http://10.0.0.7:4567

s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)
if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages

CURLE_COULDNT_RESOLVE_HOST

Details about issue

Hey I am trying to mount s3fuse over s3proxy or fakes3. I have them running over a remote node (10.0.0.7). The error log shows couldn't resolve host. The same issue occurs even when I run it at localhost with url=127.0.0.1:4567. But it works correctly when I explicitly mention localhost instead of 127.0.0.1.
I think there might be an issue that it does not resolve IP addresses and requires host names. Or maybe I am missing something/doing something stupid.

Originally created by @kunallillaney on GitHub (Aug 9, 2017). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/629 #### Additional Information _The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all._ - Version of s3fs being used (s3fs --version) - 1.82 - Version of fuse being used (pkg-config --modversion fuse) - 2.9.2 - System information (uname -a) - 3.10.0-514.26.2.el7.x86_64 - s3fs command line used (if applicable) ``` s3fs testfs /data/testfs -d -o url=http://10.0.0.7:4567 ``` - s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs) _if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_ ``` CURLE_COULDNT_RESOLVE_HOST ``` #### Details about issue Hey I am trying to mount s3fuse over s3proxy or fakes3. I have them running over a remote node (10.0.0.7). The error log shows couldn't resolve host. The same issue occurs even when I run it at localhost with url=127.0.0.1:4567. But it works correctly when I explicitly mention localhost instead of 127.0.0.1. I think there might be an issue that it does not resolve IP addresses and requires host names. Or maybe I am missing something/doing something stupid.

kerem closed this issue

2026-03-04 01:44:44 +03:00

kerem commented

2026-03-04 01:44:44 +03:00

Author

Owner

@kunallillaney commented on GitHub (Aug 9, 2017):

Okay. This is resolved. I used the use_path_request_style option. How can I add this to the documentation?

@kunallillaney commented on GitHub (Aug 9, 2017): Okay. This is resolved. I used the use_path_request_style option. How can I add this to the documentation?

kerem commented

2026-03-04 01:44:45 +03:00

Author

Owner

@gaul commented on GitHub (Aug 10, 2017):

Where do you think it should be documented?

@gaul commented on GitHub (Aug 10, 2017): Where do you think it should be documented?

kerem commented

2026-03-04 01:44:45 +03:00

Author

Owner

@kunallillaney commented on GitHub (Aug 10, 2017):

@andrewgaul Maybe in the README.md in s3fs-fuse under a different section. There seems to be very little documentation (or maybe I haven't looked enough) on how to use s3fuse with s3proxy. A sample command with the corresponding s3proxy.conf (example: aws-v4 for s3proxy.authorization) might be helpful here. Alternately, you can mention this in s3proxy.

@kunallillaney commented on GitHub (Aug 10, 2017): @andrewgaul Maybe in the README.md in s3fs-fuse under a different section. There seems to be very little documentation (or maybe I haven't looked enough) on how to use s3fuse with s3proxy. A sample command with the corresponding s3proxy.conf (example: aws-v4 for s3proxy.authorization) might be helpful here. Alternately, you can mention this in s3proxy.

kerem commented

2026-03-04 01:44:45 +03:00

Author

Owner

@gaul commented on GitHub (Sep 13, 2017):

@kunallillaney Thanks for the suggestion and I opened #637 to document this. Documenting S3Proxy falls outside the scope of s3fs but the S3Proxy wiki has client compatibility instructions:

https://github.com/andrewgaul/s3proxy/wiki/Client-compatibility-list#s3fs-fuse

@gaul commented on GitHub (Sep 13, 2017): @kunallillaney Thanks for the suggestion and I opened #637 to document this. Documenting S3Proxy falls outside the scope of s3fs but the S3Proxy wiki has client compatibility instructions: https://github.com/andrewgaul/s3proxy/wiki/Client-compatibility-list#s3fs-fuse

kerem referenced this issue

2026-03-04 01:54:11 +03:00

[PR #359] [MERGED] Issue 358: Remove optional parameter from Content-Type header #1481