Check whether a colleague, deployment service or your own transfer client is active. Record the suspicious session’s username, source address and time before terminating it so the provider can correlate logs.

1. Open Hosting Features > FTP > Sessions and review the active entries.
2. Compare the username and source with authorised users and automation. A shared network or VPN address may differ from a device’s local address.
3. For a confirmed unwanted session, use its trash action or select that session and choose Terminate. Avoid selecting every transfer unless that is the intended scope.
4. Refresh the list to confirm it ended. Disable or rotate the affected FTP credential if access is no longer authorised.
5. Inspect recently changed files, other account access and deployment logs. Ask the provider for investigation if the session returns or files were modified unexpectedly.

The selected connection should disappear and authorised transfers should remain available. Confirm that any interrupted upload did not leave a partial live file.

A client can reconnect automatically with a still-valid password, so terminating a session is not credential revocation. This screen also does not prove that SSH/SFTP or other application sessions are absent; inspect the relevant service separately.

No. Files already written remain. Compare them with a trusted deployment or backup and recover only after understanding the affected scope.

• Deactivating a SiteWorx user while preserving the account
• Changing SiteWorx file permissions for a specific application
• Following SiteWorx web-server logs during a reproducible error
• Changing a SiteWorx database-user password

• InterWorx: How To Manage FTP Sessions