All-Inkl FTP: Upload a Website with FileZilla

At All-Inkl, a German web host, you upload your website via encrypted FTP (FTPS). The access details are in the KAS, All-Inkl's technical admin panel, under "FTP": the server is <your-login>.kasserver.com, the user is your KAS login, and in your FTP client you choose explicit FTP over TLS. SFTP on port 22 is only available from the Premium plan (€9.95 a month). Then you point the domain to the website folder in the KAS and switch on the Let’s Encrypt certificate, which is included from Privat+ (€7.95) and costs extra on Privat. Sources are All-Inkl's German guides and plan comparison, retrieved on 8 November 2026 (English tutorials exist too); German labels are in quotes.

My own setup: kevinwelter.com does not run on All-Inkl but on my own servers at Hetzner. I use All-Inkl for domains and for sending my newsletter, and in October 2026 I moved two client websites, built as static files with a little PHP, from my server to All-Inkl web space. Claude Code handled the upload (see below).

Which All-Inkl plan is enough for uploading

According to the plan comparison from All-Inkl* (prices include 19 percent German VAT, the first month is free, no minimum term):

WebFTP in the browser and additional FTP users, "also on subdirectories", come with every plan. For a small static business site, Privat+ is enough: HTTPS is included and you can set DNS records, e.g. for a mailbox elsewhere. Premium is for SFTP with a key or SSH. Other hosts' prices are in the Web Hosting Comparison: Prices, Space, SFTP.

Before ordering, you can try FTP, upload and SSH in All-Inkl's free one-week test account, equipped like Premium but with fewer resources (about 2,500 MB).

Step 1: find your FTP access in the KAS

After ordering, log in to the KAS at kas.all-inkl.com. According to All-Inkl, you find the FTP access details of your main user under "FTP". The login looks like w0…, so the server is w0….kasserver.com.

Decide two things first:

• One FTP user per website. I create an extra FTP user per website, limited to its folder. A contractor or AI employee gets that user, not your main login.
• Domain or account. In the KAS you either attach a new domain to a folder of your account under "Domain", or you create a separate account under "Accounts". Per All-Inkl, an account is a separate web space with its own KAS and FTP access. That is cleaner for sites you will hand over.

Step 2: upload your website via FTPS with FileZilla

All-Inkl's FileZilla guide:

1. File, Site Manager, new site.
2. Protocol FTP, server <your-login>.kasserver.com, user <your-login>, leave the port field empty. FTP then uses its standard port 21.
3. Encryption "use explicit FTP over TLS if available". FileZilla then uses TLS whenever the server supports it, and All-Inkl's server does.
4. Logon type "ask for password". All-Inkl advises against saving the password locally.
5. Connect, enter the password, confirm the server's certificate with OK. If that prompt appears, the connection is encrypted.
6. On the right, open the website folder; if it doesn't exist yet, create it, e.g. mydomain.com. The domain will point to it in step 4. On the left, select the files, right-click, upload.

Upload the folder's contents, not the folder. According to All-Inkl, the start file should be named index.html, index.htm or index.php, otherwise the server shows "Forbidden". For the Mac, All-Inkl describes the same route with Cyberduck ("FTP-SSL (Explicit AUTH TLS)"), on Windows with WinSCP (explicit TLS/SSL). For single files, WebFTP in the browser (webftp.all-inkl.com) is enough.

Step 3: SFTP from Premium, with a key instead of a password

SFTP runs over SSH and allows key login; at All-Inkl only "from the ALL-INKL Premium plan":

1. Switch on SSH: in the KAS of the main account under "Tools", "SSH-Zugänge" (SSH access), edit the account and choose "aktiv". The SSH user is called ssh-w0…, the password is that of the main FTP user.
2. Create a key, on a Mac in Terminal with ssh-keygen -t ed25519 -a 100. On Windows, per All-Inkl, you create the key in WinSCP with PuTTYgen and copy the public key from there.
3. Show the public key (cat ~/.ssh/id_ed25519.pub, the .pub file), paste it into the "SSH-Schlüssel" (SSH key) field of the SSH user in the KAS, one key per line, and save.
4. Connect with ssh ssh-<your-login>@<your-login>.kasserver.com; for SFTP use port 22 and the same user in your client.

Your files are under /www/htdocs/w0…; with SSH, the server also has rsync for uploading only changes.

Upload your website to All-Inkl with Claude Code

For my two client websites, Claude Code wrote and ran a small upload script, one FTP user per site. SFTP with a key is the better route (step 3), but Privat and Privat+ only have FTPS. Three rules worked well:

• Credentials never in the chat, never unencrypted in the repository. My script reads server, user and password from a .env file that never goes into Git, or from its encrypted version, which may. On a Mac, the keychain works too, as in the example below.
• Enforce encryption. With ftp:ssl-force, lftp refuses to send the password in clear text; --env-password takes it from the environment, not the command line.
• Check locally, then upload, then check online. My script builds the site, checks it locally in a Docker container, uploads nothing on errors, and fetches the pages online afterwards.

An example of the core, here with the keychain, for an FTP user limited to the website folder:

# once: store the password in the keychain, macOS prompts for it
security add-generic-password -a <ftp-user> -s allinkl-ftp -w

# upload: first with --dry-run, then without
LFTP_PASSWORD="$(security find-generic-password -a <ftp-user> -s allinkl-ftp -w)" \
lftp --env-password -u <ftp-user> <server-from-the-kas> -e "
  set ftp:ssl-force true; set ftp:ssl-protect-data true; set ssl:verify-certificate true;
  mirror -R --dry-run --delete --no-perms out <target-folder>;
  bye"

mirror -R uploads the local folder out, --delete removes on the server what no longer exists locally, --no-perms sets no file permissions. <target-folder> is the folder as the FTP user sees it, so . for a limited user. Never use the main user: with it and . as target, a --delete run would remove everything not in out, including other websites. --dry-run shows beforehand what would be transferred and deleted. My script uploads new assets such as scripts, stylesheets and images first, then the pages, and deletes last. So no page points to a missing file. On Premium the same works via SFTP with a key, without any password.

You don't have to write this yourself: tell Claude Code where the credentials are and which folder goes up, and ask for the dry run first. Only upload after you approve. For building the site, see Build a Website With Claude Code: A Guide.

Step 4: point the domain to the folder

In the KAS, under "Domain", click edit ("Bearbeiten") next to your domain. In the "Ziel" (target) field, enter the website folder under "Webspace". The folder name doesn't show in the address bar. Set up both, with and without www, as I did for my client websites. Until the domain points to All-Inkl, the temporary domain ("Übergangsdomain") shown there, plus the folder name, reaches the site.

If your domain is registered elsewhere, you still add it in the KAS ("Neue Domain anlegen", with the website folder) and then connect it to the All-Inkl server via DNS at your registrar, or transfer it. For one of my client websites, the A record pointed to the IP address of <your-login>.kasserver.com. What an A record does and how a transfer with an auth code works is in How to Buy a Domain Name Forever and Keep It. If you move an existing site with its mailboxes, see Website Migration Without Losing Your Domain.

Step 5: switch on Let’s Encrypt

In the KAS under "Domain", "Bearbeiten" (edit), then "bearbeiten" next to "SSL-Schutz" (SSL protection). Under "SSL Zertifikat (Let’s Encrypt)", tick "Haftungsausschluss akzeptieren" (accept disclaimer) and click "jetzt ein Let’s Encrypt Zertifikat beziehen und einbinden" (obtain and install now). Per All-Inkl, HTTPS works within about 10 minutes. The guide only applies to domains that point to All-Inkl via DNS. Get the certificate for both, with and without www. The certificates are currently valid for 90 days and are renewed automatically about 30 days before they expire. On Privat, you first order Let’s Encrypt as an add-on in the Members Area.

You can enable HSTS in the same window. It makes browsers open your site only via HTTPS for a set time. All-Inkl warns: if you switch the certificate off later, visitors may no longer be able to open the site. As an example, All-Inkl gives 600,000 seconds, about one week. Check certificate and headers with Check Your Website Security Online.

Common upload mistakes

• "Forbidden" instead of the home page: no index.html in the target folder, often because the folder was uploaded instead of its contents.
• 404 right after switching: In my case, a newly assigned folder was only served a few minutes later. Wait before searching.
• Let’s Encrypt fails: the domain does not point to All-Inkl via DNS yet.
• SFTP won't connect: Privat and Privat+ have no SFTP. Use FTPS or move to Premium.
• DNS record can't be changed: Privat has no DNS settings (plan comparison).

For your specific case, we'll look at it together.

Frequently asked questions

Which port does All-Inkl use for FTP?

For FTP and FTPS, leave the port empty; the client uses standard port 21. SFTP runs on port 22 with the SSH user ssh-w0…, per All-Inkl only on plans with SSH, i.e. from Premium.

Does All-Inkl offer SFTP?

Yes, from Premium (€9.95 a month). Privat and Privat+ have FTPS and WebFTP, but no SFTP or SSH.

Is the SSL certificate free at All-Inkl?

The Let’s Encrypt certificate is included from Privat+; on Privat it costs extra according to the plan comparison and is ordered as an add-on in the Members Area. A validated certificate costs extra on Privat, Privat+ and Premium, €59 for six months according to the price list; the Business plan includes one.

Can I upload to All-Inkl without an FTP program?

Yes, with WebFTP in the browser, on every plan. For whole websites, a client or script is easier.

What to do next

Try FTP, upload and SSH in the free test account from All-Inkl*, then go through the steps in your plan: separate FTP user, upload, domain to folder, Let’s Encrypt. All routes to your own website are in Build Your Own Website: A Guide With AI. To hand build and upload to an AI employee and keep the approval, see how Ralf works. Ralf is a ready-made template in my community Claude Practitioners, in the Premium tier at 149 US dollars a month (as of 18.10.2026, per his page).

* Affiliate link: if you book a plan through this link, I earn a commission. Your price stays the same.