2019: Empty directory listing on Amazon S3

2019: Empty directory listing on Amazon S3

When using WebDrive to connect to an Amazon S3 bucket, sometimes the directory listing is empty.

This could happen if the bucket is located in a different Amazon S3 Availability Zone. To correct this issue, run WebDrive and edit the Site Profile Settings for the S3 Site you have configured. Go to the Amazon S3 Settings view and toggle the setting for 'Use Virtual Hosting Syntax'; you may need to try both enabled and disabled to see which one works.


Save the changes and then remount the S3 volume.


    • Related Articles

    • FTP or FTPS Connection Fails

      FTP or FTPS Connection Failing or Listing as Empty Contents Question Using WebDrive, my FTP(S) connection is failing. What should I do? Answer Below are some items to test to try to resolve a failed FTP or FTPS connection.  Steps Verify the URL/IP ...

    • Amazon S3 Connection Fails with an Error

      If your Amazon S3 connection fails with an error such as NoSuchBucket or other connect failed error, here are some possibilities:  1. Verify your Amazon connection information, bucket name, and credentials to use 2. Attempt to connect to the top ...

    • Getting Started: Connecting to an Amazon S3 Server

      Click the “+” icon and select “Amazon S3” Connection Name: Enter the name you would like to give your connection.             You can name this as you choose, or accept the default name Access Key: Enter the Access Key provided for the account to ...

    • 2019: Empty Folder Listings for SharePoint

      If using WebDrive to connect to SharePoint and you are seeing empty listings, here are items to check:  SharePoint via WebDAV:  1. Ensure you are using the proper URL and that it is entered correctly, without web encoded characters (e.g. Remove any ...

    • Unable to generate a directory listing on my FTP mapped drive

      Question: I have set up an FTP Site Profile in WebDrive to point to my FTP server. I can map the drive but no information appears; why? Solution: It's probable that you, or the FTP server that you are connecting to, is behind a firewall. When this ...