S3 Compatible Storage Min.io Not working

NetDrive3
1

I have a connection that worked for a while without issues but as of the last 3 versions it still authenticates OK but I get 403 Errors and I can’t see anything in the drive.

This is connected to min.io and it’s setup as an S3 connection in NetDrive.
I saw mention of an S3 Compatible option like for Wasabi but I don’t see that as an option in my list.

Thanks a ton for your help, I just purchased another perpetual license and am looking to buy a couple more. I’d rather stick with NetDrive rather than going with another program that does work but I would have to license as well.

Here is a snip of the error messages:
[2021/01/09 12:42:53.286] [ERROR ] [ 18008] [PROTOCOL ] S3::GetBucketRegion >> HTTP 403
[2021/01/09 12:42:53.286] [ERROR ] [ 18008] [PROTOCOL ] S3::Connect Location not found: bucket videos-podcasts
[2021/01/09 12:42:53.473] [ERROR ] [ 18008] [PROTOCOL ] S3::GetBucketRegion >> HTTP 403
[2021/01/09 12:42:53.473] [ERROR ] [ 18008] [PROTOCOL ] S3::Connect Location not found: bucket vtt
[2021/01/09 12:42:55.388] [ERROR ] [ 13468] [FILESYSTEM] [O:bdservicehost.exe] FileSystem::OpenDir => AERROR::FAILED :
[2021/01/09 12:42:55.388] [ERROR ] [ 16704] [FILESYSTEM] [O:bdservicehost.exe] FileSystem::OpenDir => AERROR::FAILED :
[2021/01/09 12:42:55.957] [ERROR ] [ 13476] [FILESYSTEM] [O:bdservicehost.exe] FileSystem::OpenDir => AERROR::FAILED :
[2021/01/09 12:42:55.958] [ERROR ] [ 13472] [FILESYSTEM] [O:bdservicehost.exe] FileSystem::OpenDir => AERROR::FAILED :
[2021/01/09 12:42:56.278] [ERROR ] [ 13468] [FILESYSTEM] [O:bdservicehost.exe] FileSystem::OpenDir => AERROR::FAILED :
[2021/01/09 12:42:56.279] [ERROR ] [ 16704] [FILESYSTEM] [O:bdservicehost.exe] FileSystem::OpenDir => AERROR::FAILED :
[2021/01/09 12:42:57.663] [ERROR ] [ 13476] [FILESYSTEM] [O:bdservicehost.exe] FileSystem::OpenDir => AERROR::FAILED :
[2021/01/09 12:42:57.664] [ERROR ] [ 13472] [FILESYSTEM] [O:bdservicehost.exe] FileSystem::OpenDir => AERROR::FAILED :
[2021/01/09 12:42:58.391] [ERROR ] [ 13468] [FILESYSTEM] [O:bdservicehost.exe] FileSystem::OpenDir => AERROR::FAILED :
[2021/01/09 12:42:58.392] [ERROR ] [ 16704] [FILESYSTEM] [O:bdservicehost.exe] FileSystem::OpenDir => AERROR::FAILED :
[2021/01/13 22:00:54.203] [ERROR ] [ 16704] [PROTOCOL ] S3::CreateDirectoryW >> HTTP 403
[2021/01/13 22:00:54.203] [ERROR ] [ 16704] [FILESYSTEM] [O:SearchIndexer.exe] FileSystem::MakeDir => AERROR::FAILED : \System Volume Information
[2021/01/13 22:00:54.422] [ERROR ] [ 13468] [PROTOCOL ] S3::CreateDirectoryW >> HTTP 403
[2021/01/13 22:00:54.422] [ERROR ] [ 13468] [FILESYSTEM] [O:SearchIndexer.exe] FileSystem::MakeDir => AERROR::FAILED : \System Volume Information
[2021/01/13 22:01:06.388] [ERROR ] [ 13468] [PROTOCOL ] S3::CreateDirectoryW >> HTTP 403
[2021/01/13 22:01:06.388] [ERROR ] [ 13468] [FILESYSTEM] [O:SearchIndexer.exe] FileSystem::MakeDir => AERROR::FAILED : \System Volume Information
[2021/01/13 22:01:06.599] [ERROR ] [ 13472] [PROTOCOL ] S3::CreateDirectoryW >> HTTP 403
[2021/01/13 22:01:06.600] [ERROR ] [ 13472] [FILESYSTEM] [O:SearchIndexer.exe] FileSystem::MakeDir => AERROR::FAILED : \System Volume Information
[2021/01/13 22:09:44.492] [ERROR ] [ 13476] [PROTOCOL ] S3::GetFileList_ObjectList >> SSL peer certificate or SSH remote key was not OK(60)
[2021/01/13 22:09:53.428] [ERROR ] [ 13472] [PROTOCOL ] S3::GetFileList_ObjectList >> SSL peer certificate or SSH remote key was not OK(60)

3

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

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

Sorry for the inconvenience it may caused.

4

Here you go

I see completely a empty drive when I try to access it mounted through Windows Explorer, but if I use the browse function I at least see some folders, most of which I can’t access either.
Confirmed these credentials all work using another tool similar to NetDrive3.

Thank you

5

Thanks for the log file.

The log file includes only ERROR level logs. Please change log level to VERBOSE and reproduce the issue.

6

Sorry about that, NetDrive3 is now crashing a lot after adding this S3 drive and I guess it reverted back to error level logs. Will try it again and post them.

1 Like
7

Ok here are the logs

Did a fresh restart, set to verbose
I can’t browse to it through the ND3 application and even though it said it was connected the drive was not showing up. So I disconnected it, tried to browse in the config screen (set remote path Browse) and I can at least see all the folders there and only some let me see inside them but not others. I then connected the drive again, navigated to it in file explorer and used the contextual menu to request a ND3 refresh.

Please let me know if you need anything else.

8

What is the name of your drive item?

I cannot find any VERBOSE logs in the files.

9

It is mounted to Drive letter O: Named Trove.
When I zipped the file sup it gave me an error saying some files are still in use. Is that maybe why?

10

I think you are right. Trove log file is not included in the zip file. Please unmount Trove and zip again.

11

Ok Try this one

12

Those last logs were after ND3 crashed so you may see some additional errors in there on top of that.

13

Anything else I can help with or provide?

14

We installed Minio local server, tested NetDrive with it and found what caused the problem. After some test and review I will send you a download link of patched version tomorrow.

Thanks for the feedback.

1 Like
15

Please try following version (Windows and macOS version):

NOTE: Your MinIO Server must be configured to support DNS based S3 bucket naming.

https://files.bdrive.com/netdrive/builds/fdf852d3790f4dabacf18cb9b55f9afb/NetDrive3_Setup-3.14.330.exe

https://files.bdrive.com/netdrive/builds/49553084eea94a5ebe5b06bffa83b312/NetDriveInstaller-3.14.384.dmg

16

Thanks so much for this, I have installed the version you provided and I can now at least see the first level of folders in the root directory but I can’t see any further.

I have attached new logs.
nd3log.zip (8.0 MB)

17

Confirmed we are using DNS based S3 Bucket naming.
We also updated certificates today and all of a sudden it started working perfectly with the new update version you sent me.

Tested on another computer still running the latest stable version, it still gave me issues so it seems the code you provided me certainly helped.

18

Ok so spoke a little too soon.

It seems I can create folders but I can’t upload any files. I confirmed the drive is configured to be a writable drive and that I have permissions on server side but every file I try to upload fails.

19

Anything else I can provide to help?

20

Sorry I missed your post. I will check the issue.