Skip to content
kaiport

Storage connections

Connect kaiport to FTP and FTPS servers, S3-compatible object storage, WebDAV (Nextcloud, ownCloud) and Azure Blob Storage.

Storage connections reach file servers and object storage: FTP and FTPS, S3-compatible storage, WebDAV and Azure Blob Storage. They don't open a terminal but the transfer view – your computer on the left, the storage on the right. This page explains the fields of each type, the start directories and what kaiport does when it connects.

Create a storage connection

  1. In the start window, click New connection.
  2. Choose the tile FTP / FTPS, S3 storage, WebDAV or Azure Blob.
  3. Fill in the fields of the type, described below, and the start directories if you like.
  4. Click Create.
  5. Click the new card. The connection opens in a tab with the transfer view.

Storage connections have the tabs General and Advanced; the Advanced tab only holds your Notes. There is no AI tab, but AI Pilot still works in the transfer view, see AI Pilot for files and storage. Color, tags, group and favorite work as for every connection, see Common fields.

FTP and FTPS

FieldDescription
HostThe server, for example ftp.example.com. Required.
UsernameLeave empty for anonymous access.
Port21, or 990 for implicit FTPS.
PasswordStored encrypted.
EncryptionPlain FTP or one of the two FTPS modes, see below.
Verify certificateOnly for FTPS. On by default.

Without a name, the connection is called user@host, or anonymous@host for anonymous access.

Encryption

OptionPortWhat happens
FTP (unencrypted)21Everything, including the password, travels in plain text. Use it only in networks you trust.
FTPS explicit (AUTH TLS)21kaiport connects like FTP and switches to TLS before the login.
FTPS implicit (port 990)990TLS from the first byte, on a port of its own.

When you switch the encryption, kaiport changes the port between 21 and 990 for you, as long as the port is one of the two.

Certificate check

With Verify certificate on, kaiport only connects when the server's certificate is valid and belongs to the host name you entered. Turn it off for servers with a self-signed certificate that you trust. If the certificate belongs to another name, enter that name as the host instead.

Anonymous access

Leave Username empty to log in as anonymous. If you also leave the password empty, kaiport sends anonymous@ as the password, as anonymous FTP servers expect.

Passive mode

kaiport transfers data in passive mode: for every listing and transfer it opens a data connection to the port the server names, always at the server address of the main connection. If the login works but listings or transfers fail, a firewall or NAT usually blocks the data ports – the server has to open its passive port range.

While the connection is open, kaiport sends a NOOP every 30 seconds so that the server doesn't close it as idle.

S3-compatible storage

FieldDescription
ProviderFills in endpoint, region and addressing for a known provider.
EndpointEmpty for Amazon S3. Otherwise the provider's address, for example https://minio.example.com.
RegionThe region of your bucket, for example eu-central-1. Empty means us-east-1.
BucketLeave empty to list all buckets.
Access key IDRequired.
Secret access keyStored encrypted.
Path-style addressingPuts the bucket in the path instead of the host name.

Without a name, the connection is called after the bucket, or after the endpoint's host name.

Provider presets

ProviderEndpointRegionPath-style
Amazon S3(empty)us-east-1off
Cloudflare R2https://<ACCOUNT_ID>.r2.cloudflarestorage.comautooff
Backblaze B2https://s3.<REGION>.backblazeb2.comus-west-004off
Wasabihttps://s3.<REGION>.wasabisys.comus-east-1off
DigitalOcean Spaceshttps://<REGION>.digitaloceanspaces.comus-east-1off
Google Cloud Storagehttps://storage.googleapis.comautoon
Hetzner Object Storagehttps://<LOCATION>.your-objectstorage.comeu-centraloff
Scalewayhttps://s3.<REGION>.scw.cloudfr-paroff
OVHcloudhttps://s3.<REGION>.io.cloud.ovh.netgraoff
MinIO / self-hostedhttp://localhost:9000us-east-1on

Replace the placeholders in angle brackets with your values and set Region to match, for example endpoint https://s3.eu-central-1.wasabisys.com with region eu-central-1. The provider field only fills in the other fields and is not saved: once you change endpoint or region, it shows “—” again.

Path-style addressing

Normally the bucket is part of the host name (my-bucket.s3.example.com). With Path-style addressing, it goes into the path instead (s3.example.com/my-bucket). MinIO, Ceph and most self-hosted servers need path-style addressing. If the connection fails because the host name with the bucket in front can't be resolved, turn it on.

Buckets and folders

  • With a Bucket set, the top level of the storage is that bucket. Without one, the top level lists all buckets as folders – your key then needs the right to list buckets.
  • kaiport can't create, rename or delete buckets (“Buckets cannot be created here.”). Manage buckets in your provider's console.
  • S3 has no real folders; a folder is the shared beginning of object names. New folder creates an empty object whose name ends with /. Renaming a folder copies every object below it and deletes the originals, which takes a while for large folders.
  • When connecting, kaiport checks your access with one small request: it lists one object of the bucket, or the buckets if none is set.

WebDAV

FieldDescription
Server URLThe full WebDAV address, starting with https:// or http://. Required.
UsernameYour user name on the server.
PasswordStored encrypted.
Verify certificateOn by default. Turn it off for self-signed certificates on servers you trust.

Without a name, the connection is called after the host name of the URL.

ServerServer URL
Nextcloudhttps://cloud.example.com/remote.php/dav/files/USER/ – replace USER with your user name.
ownCloud and other serversThe WebDAV address that the server's web interface or documentation shows.
  • kaiport logs in with HTTP Basic authentication. Use an https:// address so the password travels encrypted.
  • If your Nextcloud or ownCloud account uses two-factor login, create an app password in the account settings of the server and use it as the password.
  • Paths in the transfer view and the remote start directory are relative to the server URL.
  • If the URL points to the web interface instead of the WebDAV address, the connection fails. The possible causes then say that the server doesn't answer with WebDAV.

Azure Blob Storage

FieldDescription
Storage accountThe name of the storage account, for example mystorageaccount. Required.
Access keyOne of the account's access keys: the complete base64 key, not a SAS token. Stored encrypted.
ContainerLeave empty to list all containers.
EndpointLeave empty for Azure; kaiport then uses https://<account>.blob.core.windows.net. For the Azurite emulator, for example http://127.0.0.1:10000/devstoreaccount1.

Without a name, the connection is called after the container, or after the storage account.

Containers work like S3 buckets: without a container, the top level lists all containers; folders are the shared beginning of blob names. kaiport can't create, rename or delete containers – the message then speaks of buckets.

Start directories

FieldDescription
Remote start directoryThe folder the right side opens in, for example /www. Empty: the login directory on FTP, the top level on the other types. Without a fixed bucket or container, the path starts with its name, for example /my-bucket/backups.
Local start directoryThe folder the left side opens in. Empty: your home directory. Choose picks a folder.

The export contains both start directories; adjust the local one after an import on another computer.

Open a storage connection

Click the card. kaiport opens a tab with the transfer view and shows Connecting … until the storage answers. If the connection fails, the right side shows Connection failed with the reason, a list of Possible causes, Try again and AI diagnosis. See Transfer view and Troubleshooting.