Changing an FTP password updates the credentials for the selected file-transfer user. It should be coordinated with legitimate upload clients and deployment jobs, while preserving the user’s intended directory restriction.
IN THIS ARTICLE
01 Prepare for the change
Confirm the full FTP username and domain. Choose a strong unique password and note the current home directory before editing so access is not broadened accidentally.
02 Change a SiteWorx FTP user password
- Open Hosting Features > FTP > Accounts and locate the intended user.
- Choose the pencil or edit action. Enter and confirm the new password, leaving the home-directory path unchanged unless a separate authorised change is required.
- Save, then update the password in approved transfer clients. Use the encrypted transfer method supported by the service; FTP over TLS and SFTP are different protocols.
- Test a fresh connection and list the expected directory. Upload and remove a harmless test file in an authorised location if write access is required.
- If the old credentials were exposed, inspect unexpected uploads and review other account credentials or keys rather than treating the password change as proof the site is clean.
03 Confirm the intended access works
The new credentials should authenticate and show only the intended directory scope. Confirm the old password fails on a new connection.
04 Example: rotate one FTP credential without changing other access
A contractor used a separate FTP account to upload site files and the project has ended. Identify that FTP username and its permitted directory before changing anything. Do not rotate the main hosting login by mistake when the intention is to retire one limited credential.
After changing the password, update only the authorised applications that still need this account. A saved password in an old transfer client may continue producing failed logins. Check scheduled upload jobs and deployment tools before deciding the password change failed.
How should I confirm the change?
Disconnect the transfer client and start a new session. Test the old credential only in a controlled way, then verify that the new credential can access the intended directory. Confirm it cannot write outside its assigned scope. Do not upload customer data merely to test access; use a harmless temporary file and remove it afterwards.
If the account should no longer exist, use the separate account-removal procedure and review any option that also removes files. Contact us with the username, allowed path and exact connection error if you need help. Never include the old or new password in the support request.
Why does the SiteWorx FTP user still fail authentication after a reset?
If authentication fails, compare the username, server, protocol and port with the service settings. Do not switch to unencrypted FTP simply to bypass a TLS problem. Existing SSH access may use a different identity and requires its own review.