This problem occurs,
① first check the user's role name, then see if the path settings are correct, have relevant permissions, if these are all right, and then try the following action:
② FTP Service, it is best to restart from the service inside (can not be fundamentally resolved);
③ Reset the file path in the Server-u account and directory Access (if not, try the following);
④ Delete user, rebuild.
Original Su-Collation (FTP) collection
Sorted as follows:
1 Opening-Success
2 Opening-Success
3 Opening-Permission issues
4 Opening-File problem
5 Opening-Server problem
FILE:%s
Opening%s mode data connection for%s (%i64d Bytes).
Opening%s mode data connection for%s.
Opening ASCII mode data connection For/bin/ls.
Opening BINARY mode data connection for MLSD.
(end of ' index%s ')
Command Channel switched to Clear-text.
Command OK,%i64d Bytes available on%s
Command okay.
EXEC command Successful (tid=%u).
Received okay.
Mlst OPTS
MODE S OK.
MODE Z level set to%d.
MODE Z OK.
Noted.
Opened OK (but not really).
Pbsz command OK. Protection buffer size set to 0.
Pbsz=0
PORT Command successful.
Prot Command OK. Using Clear data connection.
Prot Command OK. Using Private Data connection.
Sscn:client method
Sscn:server method
Stru F OK.
Stru R OK.
Transfer progress notification is off.
Transfer progress notification is on.
Type set to A.
Type set to I.
The superfluous Command not implemented, in this site.
The superfluous Command not implemented, in this site.
210 Utc%+ld
211 End
211 End of status.
211-extension supported
211-status for user%name from%ip:
213%I64D
213%s
214 Direct comments or bugs to bugs@bugs.com.
214-the following commands are recognized (* => unimplemented).
215 UNIX Type:l8
The Service ready for new user.
Serv-u FTP Server v%s for WinSock ready ...
221 goodbye!
Abor command successful.
Transfer complete.
Transfer complete.
Transfer complete.
Entering passive Mode (%d,%d,%d,%d,%d,%d)
230 Password changed okay.
230 Switching to SYSTEM maintenance mode.
230 User logged in, proceed.
230 User logged in.
231 Switching to GROUP maintenance mode.
232 Switching to DOMAIN maintenance mode.
233 switching to read-only maintenance mode.
233 User logged in, PASSWORD expired-please change before proceeding.
234 AUTH Command OK. Already have SSL connection.
234 AUTH Command OK. Initializing SSL connection.
%%x
DELE command successful.
Directory changed to%s
.
RMD command successful.
Rnto command successful.
250-listing%s
253 Attributes changed okay.
253 Date/time changed okay.
257 '%s ' directory created.
257 '%s ' is current directory.
321 transferred%i64d Bytes.
331 Response to otp-md%d%u%s required for Skey.
331 User name Okay, need password.
331 User name Okay, please send complete e-mail address as password.
exists File or directory ready for destination name
Restarting at%I64D. Send STORE or RETRIEVE.
421 Data Connection closed (SSL/TLS negotiation failed).
421 Service closing control connection.
425 cannot open data connection.
425 cannot open data connection.
425 cannot open data connection.
425 Try Later, data connection in use.
425 Try Later, data connection in use.
425 Try Later, data connection in use.
425 Try later, out of network sockets.
425 Try later, out of network sockets.
425 Try later, out of network sockets.
425 Unable to listen, too many pending PASV-requests client IP.
425 Unable to set up passive listening socket.
426 Data Connection closed, cannot read file%s.
426 Data Connection closed, cannot write file%s-disk full?
426 data connection closed, error compressing data stream.
426 data connection closed, error decompressing data stream.
426 Data Connection closed, file transfer%s aborted by client.
426 Data Connection closed, file transfer%s aborted.
426 Data Connection closed, receive file%s aborted.
426 Data Connection closed, transfer aborted.
426 Transfer aborted.
431 account temporarily locked for other user, please try later.
431 Password not changed and no match for old Password.
431 Unable to negotiate secure command connection.
432 Password not changed, new Password should is at least%d characters in length.
432 Password not changed, new Password should contain at least one upper-case character and symbol
432 Password not changed, the old and the new passwords cannot be identical.
450 cannot open file%s for reading.
452 Sorry, insufficient disk quota-receive file%s aborted.
'%s ': Command not understood.
501%s:not a directory.
501 Cannot EXEC command line (error=%u).
501 Invalid mlst Options
501 Invalid option.
501 Not enough spaces, only%i64d Bytes available on drive%s
501 Permission denied.
501 SITE option not supported.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Syntax Error in parameters or arguments.
501 Wildcards not allowed.
502 Syntax error-use SITE pswd "<oldpassword>" "<newpassword>".
503 bad sequence of commands.
503 bad sequence of commands.
503 Secure Command connection required prior to Pbsz command.
503 Secure Command connection required prior to prot command.
504 Command not implemented for that parameter.
504 Command not implemented for that parameter.
504 Command not implemented for that parameter.
504 Unknown security mechanism.
510 cannot determine server time zone.
521 Data connection cannot is opened with this prot setting.
522 Ssl/tls Lib refuses to initiate secure data connection.
530 cannot change Anonymous password.
530 cannot change password.
530 not logged in, cannot find home directory.
530 not logged in, the home directory does not exist.
530 not logged in, need secure connection.
530 not logged in, but%d sessions from same IP allowed concurrently.
530 not logged in, but one session from same IP allowed at a time.
530 not logged in, too many tries with incorrect password.
530 not logged in, unauthorized IP address.
530 not logged in, with real e-mail address as password.
530 not logged in.
530 not logged in.
530 not logged in.
530 only the client IP address allowed the for PORT command.
530 only client IP addresses allowed to connect to PASV socket.
530 PASSWORD expired-please Change PASSWORD before proceeding.
530 Port number has to be between 1024 and 65535.
530 Sorry, no ANONYMOUS access allowed.
531 Ssl/tls Lib refuses to initiate secure command connection.
The SSL command connection required prior to the CCC command.
534 Invalid option. Secure data connection required for implicit SFTP.
534 Invalid option. Secure data connection required for implicit SFTP.
%s:cannot create file.
%s:cannot Delete directory.
%s:cannot Delete file.
%s:cannot determine Date/time.
%s:failed to create.
%s:no such file or directory.
%s:no such file or directory.
%s:no such file or directory.
%s:no such file or directory.
%s:no such file or directory.
%s:no such file or directory.
%s:no such file or directory.
%s:no such file or directory.
%s:no such file.
%s:no such file.
%s:permission denied.
%s:permission denied.
%s:permission denied.
Cannot change path to a port.
Cannot create a port.
Cannot create INDEX for ports.
Cannot create unique file name.
Cannot delete a port.
Cannot delete account home directory.
Cannot determine date/time for a port.
Cannot determine size of a port.
Cannot EXEC a port.
Cannot list port.
Cannot position file at requested starting point.
Cannot read requested number of bytes from file.
Cannot remove a port.
Cannot rename to a port.
Cannot restart at any position while appending to a file.
Cannot restart beyond End-of-file.
Cannot restart in a (new) unique Zero-length file.
Cannot restart in a new (zero-length) file.
The cannot File Date/time is set to future.
The server stop is pending, the allowed File transfer not.
The server stop is pending, the allowed File transfers not.
MDTM cannot change date/time to this server.
No files found.
No Maintenance Manager Client.
Passive mode is not allowed to this server.
Permission denied
Permission denied.
Permission denied.
Permission denied.
Permission denied.
Permission denied.
Permission denied.
Permission denied.
Permission denied.
Permission denied.
Permission denied.
Sorry, insufficient credit for Download-upload.
Sorry, maximum number of GETs reached for this session.
Sorry, maximum number of PUTs reached for this session.
553%s:cannot change attributes.
553%s:cannot Change Date/time.
553%s:unable to rename file or directory.
553 Server Edition does not support remote administration.
Sometimes ftp upload, download, always connect error, no outside for the following reasons, for reference only:
Serv-u bbsftp Prompt Information detailed
1. Enouth to download. (Bbsftp v2.6ce)
This message usually appears when you download the file. This hint indicates that your current download traffic is not enough.
2. 530 not logged in. (bbsftp v2.6ce) [ftp<202.15.29.29:21> user<rick> Db-ftpuserdown]
This message typically appears when a login fails. The hint indicates that the user Rick does not exist in the FTP 202.15.29.29:21.
3. 530 not logged in, unauthorized IP address. (Bbsftp v2.6ce)
Indicates that the IP address is not authorized, the packet traffic user or package time user generally modifies the IP address range that is allowed to log on.
Public account, you need to buy first to log in. Otherwise there will be this message. This is done to prevent the public account from being stolen.
4. 530 not logged in. (bbsftp v2.6ce) [badpassword][3]
The message is clear and the password is wrong.
5. 530 not logged in. (bbsftp v2.6ce) [Userdberror-ftp_users]
This is generally the wrong parameter settings, if you have not customized the database view ftp_users, in the settings will use the Data View set to not use.
6. 530 not logged in. (bbsftp v2.6ce) [Userdberror-ftpuserdown]
This error is generally a database problem, may be the MySQL character set caused by, if it is a free version of the BBSFTP, but also may be the optimization of MySQL settings caused.
7. 421 Your Account is expired! (Bbsftp v2.6ce)
This message usually appears when the user logs on. It means that the account has expired.
Traffic purchase account, encountered this error message, generally in the forum to update their account information on it (in the purchase of the interface to do a purchase operation).
Time to buy an account, then you need to buy account on the forum to use the time.
Public account password, rarely encountered such a hint, if you encounter this message, indicating that the public account is just more than the password update time, then the previous purchase record will be emptied, you need to buy a public account and password to log in.
8. 421 Your Account is disabled! (Bbsftp v2.6ce)
This information typically occurs when a user logs on, indicating that the account is disabled. Can only contact the administrator to resolve
9. 530 not logged in, the home directory does not exist. (Bbsftp v2.6ce)
Typically occurs when a user logs on. It means that the user's root directory does not exist.
Check the user carefully to see if the corresponding role is configured. It is obviously problematic if the persona does not exist.
Then check the settings for the FTP root directory in its corresponding role to see if the path that is filled in is present on the FTP server.
If the existence of the general is no problem. Pay attention to three points:
1 After you modify the role settings to restart the SERVU will not take effect.
2 If the path is on an NTFS-formatted disk, make sure that the FTP server has access to the path.
3 if local Directory security parameters are set. The path must be within the path set by the security directory.
10. Permission denied
Generally, the permissions for the path access rule are not set correctly.
First check the user's corresponding role name,
Then check the settings for the role to see if the group number for the path access rule is set.
Then check the path Access rule group for the corresponding group number,
See if you added access rights to the FTP root directory.
Sometimes you can try the English path name because of the database cause of the Chinese character error.
Note Modifying these settings requires restarting the SERVU.
