FTP Troubleshooting: Tips and Tricks

Are you having problems connecting?

As you know, we’ve been hard at work upgrading our architecture, and part of that work involves moving accounts from our older servers to our new servers. For most of our customers, this is a smooth transition, and everything works just fine after the move. Sometimes, though, a connection you’ve relied on for a while just stops working.

We’ve collected some of the most common speedbumps here, along with the answers for how to get unstuck. Check below for the problem you’re running into:

Problem: The login form displays an error that says “Please log in at ….”

ExaVault file sharing log in page

If you’re trying to connect to the SWFT File Manager, and you see an error message that starts with “Please log in at …”, this means you’re trying to log into the old servers. Here’s how to fix it:

If you’re used to logging in https://swft.exavault.com use your account name’s address instead. For this example, we’re logging into the “superftp” account, so we need to visit https://superftp.exavault.com.

If this solved your problem, great! Make sure to bookmark your account name URL and always use that to log in instead of the swft.exavault.com address. In fact, if you have the old address bookmarked, delete that bookmark.

If this didn’t solve your problem, meaning you went to your account name url and still got the message, contact ExaVault support for help. There’s probably something related to DNS that needs to be solved.

Problem: My FTP Program Can’t Connect

If you’re using a separate program, such as Filezilla, WS_FTP, Core FTP, or Cyberduck, you may find that your connection which worked just fine yesterday no longer connects today. Here’s what to look for:

Step 1: Make sure you’re connecting to the right address.

Whenever possible, you should use the account name address for your server. If you’re not sure if you’re using the right address, check to see if you’re using one of these options:

  • fermion.exavault.com
  • hadron.exavault.com
  • neutron.exavault.com
  • proton.exavault.com
  • 67.208.64.235
  • 67.208.64.237
  • 67.208.93.227
  • 67.208.93.225

None of those addresses will work for any account that has been moved to the new servers.

If you’re trying to log into the “superftp” account, you’ll want to use the server address: superftp.exavault.com.

You might have an FTP connection through a device or custom program that only allows for a numeric IP address. In this case (and this case only), use the address 67.208.93.232 for your server.

Step 2: Update your FTP Program

If you’ve already made sure that your program is connecting to the new server, but it doesn’t even seem to get as far as checking your password, it’s possible that your FTP program isn’t compatible with our new servers. ExaVault’s new servers no longer support some older, insecure connection types, which are the default for old versions of some FTP programs. Make sure that your FTP program is the most current version available.

Bonus info for super-admin types: The list of accepted key exchange ciphers supported by our SFTP service can be found at http://www.proftpd.org/docs/contrib/mod_sftp.html#SFTPCiphers

Step 3: Accept the Host Key

FTP Troubleshooting - unknown host key

If your account has been moved to the new servers, then you may get an error message from your SFTP program telling you that there is a host key mismatch or that the host key has changed. The error message may contain many concerned upper-cased words and exclamation points shouting that THIS MAY BE AN ATTACK! Don’t panic. The host key for your account changes with the new server; that’s part of the process. If you have an option to trust the key and continue connecting, choose that option.

Step 4: Check your firewall settings

You made sure the address information is correct, your FTP client is up-to-date, and you’re not getting any errors about the host key, but the connection is just … not reaching the server. If you’re connecting from a corporate location, it’s possible your IT department only allowed traffic to your previous ExaVault server. Contact the person in charge of your firewall to find out if this is the case. For a list of the ports and addresses used by ExaVault servers, see https://www.exavault.com/docs/help/01-firewalls/01-firewall-setup

If none of this solved your problem, get in touch with ExaVault support, and we’ll help.

Problem: The login page says “Uh oh. You’re looking for a page that doesn’t exist or has been moved”  URL error page with angry beaver

If you’ve had the login page bookmarked for a few years and one day it suddenly stops working, take a look at the address that is saved.  Take off anything that shows up after “exavault.com” and save your bookmark again. This should update the page and display the login correctly for you.

If you’re still seeing an error page when you try to connect, give us a shout at ExaVault support.

Problem: None of this stuff helped me

Well, that’s frustrating, and we’re sorry to hear that. Please get in touch with ExaVault support, and we’ll get you up and running as fast as possible.