Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Serv-U Managed File Transfer & Serv-U FTP Server > Server responds with a "530 Not logged in" error

Server responds with a "530 Not logged in" error

Updated April 27, 2017

Overview

This article addresses the issue where a server responds with a 530 Not logged in error.

Environment

All Serv-U versions

Cause

The 530 error is returned when your login information is incorrect. This error comes from your server and not from FTP Voyager.

Resolution

Perform the appropriate action from the following options:

  • Contact your ISP or server administrator. This can happen when they change your password, when you forget your password, when your home directory is inaccessible, or when your account has been disabled.
  • Contact your FTP server administrator or check any material provided by your ISP to verify your login information.
  • If you can log in once but you are unable to transfer files, enable Connection Saver. Connection Saver uses only one login to transfer files. This will limit FTP Voyager's ability to browse while uploading or downloading.
    • For a single site profile, go to Advanced > Connection.
    • For all sites, go to View > Options > Connection.

If you need more information about this error, contact your FTP server administrator or ISP.

 

 

Last modified
17:38, 26 Apr 2017

Tags

Classifications

Public