Opened 2 years ago

Closed 2 years ago

Last modified 3 months ago

#11955 closed Bug report (worksforme)

For s3 connection, FZ ignores "host:" configuration box so impossible to connect to local s3 server (min.io)

Reported by: Richard Jelbert Owned by:
Priority: normal Component: FileZilla Client
Keywords: s3, host, Cc: richard.jelbert@…
Component version: 3.43.0 Operating system type: OS X
Operating system version: Mac OS X (Darwin 18.6.0 x86_64) 10.14

Description

I am running a local min.io s3 server on my local network and FileZilla Pro can not connect to it.

I set the hostname to my min.io s3 server network IP address but I can see in the access logs that FZ ignores my host entry and simply uses an Amazon address instead which of course fails.

The host IP address is entered in the "Host:" box as 192.168.0.43 and Port: 9000 however FZ Pro shows that it is trying to access a different server:
Retrieving directory listing...
Status: Resolving address of s3.dualstack.us-east-1.amazonaws.com
Status: Connecting to 52.216.9.37:9000...
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listing
... so it looks like it has used my port number but ignored my host IP address and used something from AWS or something internal instead.
This seems to be a bug because it is entirely reasonable to expect "Host:" to allow me to connect to a s3 server at my own IP address.

My app and mac details are:
FileZilla Pro


Version: 3.43.0

Build information:

Compiled for: x86_64-apple-darwin18.6.0
Compiled on: x86_64-apple-darwin18.6.0
Build date: 2019-06-27
Compiled with: Apple LLVM version 10.0.1 (clang-1001.0.46.4)
Compiler flags: -Werror=partial-availability -Wall -g

Linked against:

wxWidgets: 3.0.5
SQLite: 3.26.0
GnuTLS: 3.6.7

Operating system:

Name: Mac OS X (Darwin 18.6.0 x86_64)
Version: 10.14
CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi2 bmi2 adx lm
Settings dir: /Users/richardj/.config/filezilla/

Attachments (5)

Screenshot 2019-07-04 22.53.43.png (488.9 KB ) - added by Richard Jelbert 2 years ago.
Screenshot 2019-07-04 22.52.40.png (516.3 KB ) - added by Richard Jelbert 2 years ago.
s3-provider-localhost.png (63.7 KB ) - added by FileKira 3 months ago.
site-manager-s3-localhost.png (39.5 KB ) - added by FileKira 3 months ago.
s3-provider-localhost-no-port.png (60.6 KB ) - added by FileKira 3 months ago.

Download all attachments as: .zip

Change History (13)

by Richard Jelbert, 2 years ago

by Richard Jelbert, 2 years ago

comment:1 by CyberCyclone, 2 years ago

I'm having the exact same issue. The host field is ignored and defaults to S3 in the US when I need it to connect to Minio via a local IP address. There's also other S3 compatible storage services out there other than S3.

comment:2 by Tim Kosse, 2 years ago

Priority: blockernormal
Resolution: worksforme
Status: newclosed

You need to configure custom S3 providers on the S3 providers page in the settings dialog.

The host field is not ignored, it is used to deduce provider and default region.

by FileKira, 3 months ago

Attachment: s3-provider-localhost.png added

by FileKira, 3 months ago

comment:3 by FileKira, 3 months ago

How to configure custom S3 provider for localhost? I've added screenshots of my configuration (not working) as attachments (see s3-provider-localhost.png​ and site-manager-s3-localhost.png).

Status:      	Retrieving directory listing...
Status:      	Resolving address of s3.dualstack.us-east-1.amazonaws.com
Status:      	Connecting to 52.216.30.22:5553...
Error:        	Connection timed out after 20 seconds of inactivity
Error:        	Failed to retrieve directory listing

comment:4 by Tim Kosse, 3 months ago

Your S3 provider needs to listen on port 443, don't specify ports in the provider configuration.

by FileKira, 3 months ago

comment:5 by FileKira, 3 months ago

Thanks, I've removed the port from the provider configuration (see s3-provider-localhost-no-port.png) and get different errors now

Status:      	Retrieving directory listing...
Status:      	Resolving address of localhost
Status:      	Connecting to [::1]:5553...
Status:      	Connection established, initializing TLS...
Error:        	GnuTLS error -15: An unexpected TLS packet was received.
Status:      	Connection attempt failed with "ECONNABORTED - Connection aborted".
Error:        	Disconnected from server: ECONNABORTED - Connection aborted
Error:        	Failed to retrieve directory listing
Status:      	Retrieving directory listing...
Status:      	Resolving address of localhost
Status:      	Connecting to [::1]:5553...
Status:      	Connection established, initializing TLS...
Error:        	GnuTLS error -15: An unexpected TLS packet was received.
Status:      	Connection attempt failed with "ECONNABORTED - Connection aborted".
Error:        	Disconnected from server: ECONNABORTED - Connection aborted
Error:        	Failed to retrieve directory listing

Is the provider configuration ok? Is the site configuration ok? How to configure MinIO to work with FZ Pro? Do I need to configure a reverse proxy for TLS? Would FZ Pro accept a self signed certificate (on localhost)?

in reply to:  2 comment:6 by FileKira, 3 months ago

Replying to Tim Kosse:

You need to configure custom S3 providers on the S3 providers page in the settings dialog.

The host field is not ignored, it is used to deduce provider and default region.

Sorry, I forgot to mention you in my response above. I guess, you didn't get notified.

comment:7 by Tim Kosse, 3 months ago

There doesn't appear to be a working HTTPS server at that port. Note that the default HTTPS port is 443.

Localhost is unlikely to work, as it typically doesn't have subdomains. Subdomains are needed to access buckets in the given region's endpoint. If the bucket name for example is "myfiles" and the endpoint is "myregion.example.com", the full hostname is "myfiles.myregion.example.com"

(Since the data is on localhost, why don't you simply access the files directly? No need to transfer them)

in reply to:  7 comment:8 by FileKira, 3 months ago

Replying to Tim Kosse:

There doesn't appear to be a working HTTPS server at that port. Note that the default HTTPS port is 443.

Localhost is unlikely to work, as it typically doesn't have subdomains. Subdomains are needed to access buckets in the given region's endpoint. If the bucket name for example is "myfiles" and the endpoint is "myregion.example.com", the full hostname is "myfiles.myregion.example.com"

(Since the data is on localhost, why don't you simply access the files directly? No need to transfer them)

I'm using MinIO in (local) development. I just change the configuration (i.e. S3 endpoint) in production. It is not necessary to change the logic/code (less error prone).

I would prefer to use one tool in development and production, but it seems to me that FileZilla Pro can not be used with a local S3 instance (like MinIO).

Note: See TracTickets for help on using tickets.