SFTP access
Website files are uploaded over SFTP. It is a secure file transfer over SSH. We don't support plain FTP.
You sign in with a key only, no password. The key is created automatically the first time you open the SFTP page. It is safer than a password and can't be guessed.
Connection details
Open "Hosting" → "SFTP". There you'll find:
- the server's host and port;
- the username – your hosting account's name;
- a link to download the private key;
- a link to download a ready FileZilla profile.
Keep the private key as safe as a password. Anyone who has it can access your files.
FileZilla
- Download the private key and the FileZilla profile. Save the key somewhere you won't delete it from.
- In FileZilla, choose "File" → "Import…" and select the downloaded profile.
- Open "File" → "Site Manager", select the imported site, and in the "Key file" field choose the downloaded private key.
- Click "Connect".
Other programs
-
WinSCP (Windows): a new site with the SFTP protocol and the host, port and username from the page. Under "Advanced" → "SSH" → "Authentication", choose the private key. WinSCP will offer to convert it to its own format.
-
Command line (Linux, macOS, Windows 10+):
sftp -i path/to/key -P <port> <username>@<host>On Linux and macOS, the key must be readable only by you:
chmod 600 path/to/key.
Where the files are
After you sign in, you see only your own account's files. Each domain and subdomain has its own folder with the website's files. Upload each website into the folder with its name. While a folder is empty, the website shows a placeholder page.
Symbolic links and .htaccess
A website follows a symbolic link (symlink) only when the link and the file it points to both belong to your account. If an .htaccess file contains Options +FollowSymLinks, the website returns error 500. Change the line to Options +SymLinksIfOwnerMatch. URL rewriting (RewriteRule) works with it as well.
A new key
If the key may have leaked, create a new one on the SFTP page. The old key stops working immediately. Every program that uses it has to be set up again with the new key.
"Too many authentication failures"
If the connection is closed with this error, your program offered the server other keys before getting to yours. Usually these are the keys of an SSH agent (Pageant on Windows, ssh-agent on Linux and macOS). The server stops after a few failed attempts.
- FileZilla: close Pageant, or start FileZilla without the agent (on Linux:
SSH_AUTH_SOCK= filezilla). - Command line: add
-o IdentitiesOnly=yes, so that only the given key is tried.
Access by technical support
When you contact us, technical support can log into your account the same way you do: over SFTP, as the account's user, and only to its files. This way we look at a problem exactly as you see it. Support's keys aren't among your keys and aren't shown on the SFTP page.