[Bug 811324] New: I can't connect to an own FTP server with VSFTPD
https://bugzilla.novell.com/show_bug.cgi?id=811324 https://bugzilla.novell.com/show_bug.cgi?id=811324#c0 Summary: I can't connect to an own FTP server with VSFTPD Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: edu.rm.85@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 Well, the people became crazy in the forum because we can't put running VSFTPD. We tried everything, stopping the firewall, create an user with it own home folder, almost every combination possible in the /etc/vsftpd.conf file... And the result is always the same, when I try to connect with Filezilla it gives me an 530 error. VSFTPD allow to access me with an anonymous connection, but when I try to access with my own FTP user the server doesn't allow me to access. I configured VSFTPD many times in Fedora and it's easy, but in OpenSuse is simply a nightmare. I had to switch to pure-FTPd to get an FTP server because I need it. What's the origin of the problem? An error migrating to systemd? Now I'll install OpenSuse 12.3 in a VirtualBox machine to follow your instructions. This is the link of the forum. https://forums.opensuse.org/english/get-technical-help-here/network-internet... I repeat the topic in another thread, I'm ColdDistance in the forum. https://forums.opensuse.org/english/get-technical-help-here/network-internet... Reproducible: Always Steps to Reproduce: 1. I configure VSFTP. 2. Every time 3. Actual Results: I can't access to my own FTP server :-( . -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=811324
https://bugzilla.novell.com/show_bug.cgi?id=811324#c
Eduardo Rayas
https://bugzilla.novell.com/show_bug.cgi?id=811324
https://bugzilla.novell.com/show_bug.cgi?id=811324#c1
--- Comment #1 from Eduardo Rayas
https://bugzilla.novell.com/show_bug.cgi?id=811324
https://bugzilla.novell.com/show_bug.cgi?id=811324#c
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=811324
https://bugzilla.novell.com/show_bug.cgi?id=811324#c2
Cristian Rodríguez
https://bugzilla.novell.com/show_bug.cgi?id=811324
https://bugzilla.novell.com/show_bug.cgi?id=811324#c3
Ioannis Theodoridis
https://bugzilla.novell.com/show_bug.cgi?id=811324
https://bugzilla.novell.com/show_bug.cgi?id=811324#c4
--- Comment #4 from Cristian Rodríguez
It can be very misleading to mark a bug as resolved just because there is a duplicate bug. As far as I know from the 786024 bug, it is not yet resolved.
This is how bugzilla works, duplicated bugs are "resolved" as duplicate, nothing strange and part of the (awful) workflow thing has. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com