FTP Error 332: Need Account for Login
FTP reply code 332 indicates that the USER and PASS credentials were accepted but an additional ACCT (account) command is required before login is complete. The ACCT command provides a third level of authentication or account selection — some servers use it to select which project, department, or billing account the session should be charged to. This was more common on mainframe and multi-tenant systems. Most modern FTP servers do not use ACCT and you are unlikely to encounter 332 unless connecting to legacy or enterprise systems.
Status
332 Need Account for LoginExample
220 mainframe.example.com FTP server ready
USER alice
331 Password required for alice
PASS ****
332 Need account for login
ACCT PROJECT42
230 User alice logged inHow to Troubleshoot
Send the ACCT command
After receiving 332, send ACCT followed by the account name. If you do not know the account name, check with the FTP server administrator.
Check server documentation
The ACCT command is server-specific. Consult the FTP server's documentation or your administrator to determine what value to send with ACCT.
Common Causes
Server requires account selection
highThe server authenticated the user but needs to know which account or project to associate with the session. This is common on mainframe FTP services and some enterprise file transfer systems.
Multi-tenant system requiring billing account
mediumOn shared hosting or enterprise systems, the ACCT command selects which storage quota, billing account, or virtual host to use for the session. The user may have access to multiple accounts.
Related Error Codes
User Logged In
Authentication successful. The user is now logged in and can access the server.
User Name Okay, Need Password
The username was accepted. The server is now waiting for the password.
Not Logged In
The user is not logged in. Authentication is required before this command can be executed.
Need Account for Storing Files
The server requires an ACCT command before files can be stored or uploaded.
References
| Specification | Section |
|---|---|
| RFC 959 | RFC 959 §4.2 |
Frequently Asked Questions
This reference was compiled from official RFCs, protocol specifications, and hands-on troubleshooting experience. AI tools were used primarily for formatting and organizing the content on the page.