Frequently Asked Questions

The NearlyFreeSpeech.NET FAQ (*)

Uploading (*)

What is the connection information to upload files to my web site?

How do I upload my content to my site?

Can I access my web site via ssh?

What directory do I upload my web site's files to?

What hostname should I use for SFTP?

What program should I use to connect via ssh?

Why do I have to enable FTP in two places to get it to work?

What is SFTP?

Can I configure my ssh connection to use a public key?

I tried to SFTP to ftp.xxx.nearlyfreespeech.net and it failed. Why?

What are the fingerprints for the NearlyFreeSpeech.NET ssh keys?

I am having trouble uploading with FTP. What could be wrong?

First, please consider using an uploading method other than FTP, such as SFTP or SCP. FTP is a complex, insecure protocol that does not work very well on the modern Internet. If you have an alternative, use it.

Please also keep in mind that, as of May 2010, memberships now come with FTP disabled by default, so if you must use it, you'll need to make sure it's properly enabled first.

With that said, almost all FTP problems are caused by NAT devices (especially cheap residential gateway routers) incorrectly processing FTP connections, or by personal firewall software blocking FTP access. These problems generally manifest as being able to connect to the FTP server, but not to upload or download any files. FTP has two operating modes, active and passive. The first response to any FTP connection problem should be to switch your FTP client from active mode to passive mode, or vice versa. Switching modes almost always clears up FTP issues.

Other potential problem areas for FTP include your local firewall configuration (hardware or software) and incorrect FTP connection information.

What if I think the name of your ssh server is too long?

I can connect to NearlyFreeSpeech.NET just fine, so why is your FTP or ssh server unreachable or timing out?

Is automated SSH/FTP access to the system allowed?