Fails with curlCode: 51 msg: SSL peer certificate or SSH remote key was not OK.
I suppose this is valid following the RFC for wildcard certificates.
Would this leave me with the PR #190 fix?
[root@vagrant-centos65 var]# s3fs abc.example.com:/dev/web1 /var/www -o url=https://s3.amazonaws.com -d -d -f -o f2 -o curldbg
set_moutpoint_attribute(3379): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755)
FUSE library version: 2.9.3
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
INIT: 7.13
flags=0x0000b07b
max_readahead=0x00020000
s3fs_init(2650): init
s3fs_check_service(2968): check services.
CheckBucket(2367): check a bucket.
prepare_url(174): URL is https://s3.amazonaws.com/abc.example.com/dev/web1/
prepare_url(204): URL changed is https://abc.example.com.s3.amazonaws.com/dev/web1/
RequestPerform(1572): connecting to URL https://abc.example.com.s3.amazonaws.com/dev/web1/
You could try -o use_path_request_style.
Thanks Robbkistler, would that use the https://s3.amazonaws.com/abc.example.com/dev/web1/ path.
I get a perm redirect at that address.
PermanentRedirect
The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
@neilmillard you need to combine -o use_path_request_style and -o url=https://s3-${region}.amazonaws.com using the appropriate regional endpoint hostname for S3.
Path request style requires use of the correct regional endpoint hostname when the bucket is not in US Standard (us-east-1).
Most helpful comment
You could try
-o use_path_request_style.