Cannot read container configuration. (Amazon S3) error on public folders

[igorschlum]

When attempting to access S3 buckets through Cyberduck, the application incorrectly handles public vs private folders, leading to DNS lookup errors.

Specifically:

Public folders (e.g., agorapass) display incorrect URLs, causing DNS lookup failures.
Private folders (e.g., local_agorapass) are accessible without issues.
The error message displayed is: "Cannot read container configuration. (Amazon S3)"
DNS lookup for agorapass.storage.vicem.com failed. DNS is the network service that translates a server name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing access to the network.

My s3 is not responding to agorapass.storage.vicem.com as agorapass is a forder in storage.vicem.com

Environment
Operating System: [Mac OS 15.2
Cyberduck Version: [9.1.1]
S3 Provider: [storage.vicem.com]

Thank you for your attention to this matter. Any assistance in resolving this issue would be greatly appreciated.

cyberduck.log.zip

[dkocher]

Please use the connection profile using deprecated path-style access for buckets as documented in Connecting using Deprecated Path Style Requests.

bq. Attempting to connect using the regular S3 connection profile to a server with no support for virtual host style requests will cause the error Cannot read container configuration.

[dkocher]

Also in #16590.

[igorschlum]

Thank you. it works well !