Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with passive mode connectivity #1

Closed
DanielPalmer opened this issue Jan 12, 2016 · 8 comments
Closed

Issues with passive mode connectivity #1

DanielPalmer opened this issue Jan 12, 2016 · 8 comments

Comments

@DanielPalmer
Copy link

Hi,
I have setup my ftp container using the example files provided however when I login and attempt to do anything using my ftp client I have issues relating to no route to host. Below is the error message I receive. Googling this suggests having to do some config with ip tables?

I can login but cant do anything

tp> open 192.168.0.10
Connected to 192.168.0.10 (192.168.0.10).
220 (vsFTPd 3.0.2)
Name (192.168.0.10:root): admin
331 Please specify the password.
Password:
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> ls
227 Entering Passive Mode (172,17,1,21,117,241).
ftp: connect: No route to host
ftp>

Anyone able to suggest some ideas?

Thanks

@DanielPalmer
Copy link
Author

Fixed by changing the ports to the correct way round in the vsftpd.conf file which now enables passive mode to work.

@dgrant
Copy link

dgrant commented Mar 11, 2016

GRRRRR, I spent so much time on this and only noticed this ticket now. @DanielPalmer why did you close it? It's still a bug! Maintainer, please re-open this.

@DanielPalmer DanielPalmer reopened this Mar 11, 2016
@DanielPalmer
Copy link
Author

Reopened to be fixed

@pozgo
Copy link

pozgo commented Aug 16, 2016

Its easy fix ;)

in vsftpd.conf swap passive port values

it should be:

## Set passive port range
pasv_max_port=21110
pasv_min_port=21100

@fauria fauria closed this as completed Apr 13, 2018
@fauria fauria reopened this Apr 13, 2018
@fauria
Copy link
Owner

fauria commented Apr 13, 2018

Using env vars for passive port configuration at run time. Closing.

@fauria fauria closed this as completed Apr 13, 2018
fauria pushed a commit that referenced this issue Dec 26, 2018
@emper0r
Copy link

emper0r commented Mar 5, 2019

This never works... still bug!

Stato: Connessione a 192.168.7.125:21...
Stato: Connessione stabilita, in attesa del messaggio di benvenuto...
Stato: Server non sicuro, non supporta FTP su TLS.
Stato: Accesso effettuato
Stato: Lettura elenco cartelle...
Comando: PWD
Risposta: 257 "/"
Comando: TYPE I
Risposta: 200 Switching to Binary mode.
Comando: PASV
Risposta: 227 Entering Passive Mode (127,0,0,1,82,108).
Comando: LIST
Errore: La connessione dati non può essere stabilita. ECONNREFUSED - Connessione rifiutata dal server

Docker on server centos
[root@centos-7-125 ~]# docker run -d -v hosting:/home/vsftpd -p 20:20 -p 21:21 -p 21100-21110:21100-21110 -e FTP_USER=vhost -e FTP_PASS=vpassword -e PASV_ADDRESS=127.0.0.1 -e PASV_MIN_PORT=21100 -e PASV_MAX_PORT=21110 --name vsftpd --restart=always fauria/vsftpd

can't see directory only login....

Tue Mar 5 15:24:16 2019 [pid 21] CONNECT: Client "192.168.113.2"
Tue Mar 5 15:24:16 2019 [pid 20] [vhost] OK LOGIN: Client "192.168.113.2"

!! but never connect to see directories !!

Filezilla setting on pasive mode and / or active using port max/min 21110 / 21100
never hit!

@Lunaleeguo
Copy link

I have encountered the same problem with you. Can you finally solve it?
@emper0r

@rachid-aachich
Copy link

Still a problem, never works, tried all the options above but still Passive mode isn't working and can't list directory in filezilla client.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants