Can't connect to S3 Compatible Cloud Storage

[john-4645]

Hello,

I’m trying to connect to S3 Compatible Storage (Polycloud/CrowdStorage) but cannot establish a connection.

In the ‘Add a Personal Drive Window’ I have selected S3 as the storage type. After clicking ‘Connect’ I enter ‘https://polycloud.crowdapis.com’ as the server address and my AWS ID and SECRET. I haven’t been able to make a connection yet and was wondering if NetDrive supported S3 compatible storage?

Thanks for your help

[jyyoon]

Hello.

Thank you for using NetDrive.

Did you enter AWS ID and SECRET? You should enter your polycloud id and secret key.

I will create an account of polycloud and try it. Then I will feedback to you.

Regards.

[john-4645]

Hi jyyoon, thanks for the response. I did enter my AWS ID and Secret. If you want to try it out yourself the platform I’m using is https://crowdstorage.com/.

[jyyoon]

I got a account of crowdstorage.com

Please configure like below to connect to polycloud.

Regards.

[john-4645]

Thanks for making the account and trying the connection. Were you able to get the connection to work successfully and upload/download anything? I’m entering the correct information in those fields and am getting a ‘please check server information’ error.

[jyyoon]

Sure, I can connect, download and upload a file and create a folder.

To figure out what happned, please attach debug log files.

After setting the log level to VERBOSE, please reproduce the problem and send us the debug log file :

How to attach a log file

1. Change Log Level First, check your settings and change log level to VERBOSE. 1A. If you cannot login At your login screen: [image] Click SETTINGS at the lower right corner. Change Log level to VERBOSE and go back to login screen to apply the change: [image] 1B. If you can login Go to Settings: [image] Change log level to VERBOSE: [22] Set to DEBUG if you use old version because there is no VERBOSE log level. Go back to DRIVES screen. Changed log level takes effect when you leave …

There is no login related credential information in the log files.

If the issue persists, we can have a remote session.

First of all, let me show your debug log files.

Regards.