Ambiguous/Missing error connecting to non-aws buckets
Author: andrewdscott12Created Feb 2, 2026Updated Feb 8, 2026
Additional Information
Version of s3fs being used (s3fs --version)
V1.95 and up
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse or dpkg -s fuse)
2.9.9
Provider (AWS, OVH, Hetzner, iDrive E2, ...)
IBM ICOS
Kernel information (uname -r)
5.14.0-503.40.1.el9_5.s390x
GNU/Linux Distribution, if applicable (cat /etc/os-release)
RHEL9.5
How to run s3fs, if applicable
[] command line
[X] /etc/fstab
rhui /var/lib/rhi fuse.s3fs _netdev,noatime,nonempty, allow_other,url=https://providerendpoint 0 0
s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)
Details about issue
Ambiguous/missing errors. Checked against current version of s3fs_check_service function, and omission still appears to exist. s3fs-fuse does not provide a useful error when failing to connect due to a certificate validation issue. If Certificate validation errors from curl were passed through to the error generated by s3fs-fuse, user experience would be dramatically improved. Currently, failures due to cert validations are essentially silent. It simply won't mount the bucket and the message in the log is null.
Source: s3fs-fuse/s3fs-fuse