Skip to content

Configuration and Variables Updated 2026-05-27

FTP/FTPS support

Installing and using the FTP add-on for file transfer, log downloads, and configuration editing on Stack Harbor PaaS application and database containers.

FTP (File Transfer Protocol) and its TLS-wrapped sibling FTPS are still useful when you need to move files between your local machine and a container in bulk — uploading assets, pulling logs, editing configuration files. Stack Harbor PaaS offers FTP and FTPS as an add-on you can install on application servers and databases.

The add-on is not compatible with Docker containers. For Docker-based stacks, use SSH or volume mounts instead.

What FTP is good for

The honest list:

  • Uploading or downloading resources in bulk.
  • Pulling log files for offline analysis.
  • Editing configuration files directly from an editor with FTP support.
  • Syncing local files into the container with a tool like GoodSync.

The list of things FTP is not good for: deploying applications. Files dropped via FTP do not show up in the dashboard’s deployment list, which means redeploys and rollbacks will not work as expected. Use git-deploy or the Deployment Manager instead.

Prerequisites

Three things must be true before you install FTP:

  1. You have an FTP client locally (FileZilla is the standard pick).
  2. The environment has an application server or database with the FTP add-on supported.
  3. The node has a public IP attached. FTP needs a stable external address.

Installing the add-on

  1. Click Add-Ons on the application server (or database).
  2. Find FTP in the list and click Install.
  3. Confirm in the dialog.
  4. You receive an email with credentials: FTP host, login, password, IP. Keep this somewhere accessible — you will need it every time you connect.

Connecting

From an FTP client

  1. Open FileZilla (or your client of choice).
  2. Enter the host, username, and password from the install email.
  3. Connect.
  4. You see the container’s config folder tree. Download, edit, upload, delete, or drag-and-drop files as needed.
  5. Changes made through the FTP client show up in the dashboard’s configuration manager after you refresh it.

Through the browser

  1. Click Add-Ons on the server.
  2. Find FTP in the list. The available IPs are shown next to it.
  3. Click an IP link. The browser opens an FTP session.
  4. Enter your credentials. The config folder tree is shown read-only — useful for quick browsing without installing a client.

Common workflows

Transferring files

Drag and drop between the local pane and remote pane in your FTP client. For larger sets, right-click the selection and pick Upload or Download. The queue feature lets you stage transfers and run them in batches.

Directory comparison (in FileZilla, View → Directory Comparison) is useful when you want to see what is out of sync without checking every file by hand.

Downloading log files

The logs folder of the container is exposed through FTP. Navigate into it, pick the file you need, download, and open in any editor. This is the recommended way to grab logs in bulk — the dashboard log viewer is better for live tailing, FTP is better for archival pulls.

Syncing files with GoodSync

  1. Open GoodSync, click Browse on the left side.
  2. Pick the FTP tab, enter host, username, and password, click Go.
  3. Choose the folder on the server.
  4. Click Browse on the right side and pick the local folder.
  5. Analyze shows the differences. Sync copies them across.

Editing configuration files

Most editors with FTP support (Sublime Text, VS Code with the right extension, etc.) can open files directly over FTP. Connect, browse to the file, edit, save — the change is applied to the container immediately.

Switching to FTPS

For credentials and content to be encrypted in transit, use FTPS rather than plain FTP.

In FileZilla, File → Site Manager → New Site:

  • Host — your FTP host.
  • Protocol — FTP (File Transfer Protocol).
  • Encryption — Require explicit FTP over TLS.
  • Logon Type — Interactive.
  • User — your FTP user.

Click Connect, enter the password, and you are connected over FTPS.

Managing credentials

Resetting the password

  1. Click Add-Ons on the server.
  2. Find FTP, click Reset Password.
  3. A new password is emailed to you.

Setting a custom password

The auto-generated password is fine, but a custom one you control is better — especially if you share environment access with a team.

  1. Generate an SSH key and add it to your dashboard.

  2. SSH into the container with the FTP add-on.

  3. Run:

    sudo /usr/bin/passwd jelastic-ftp

  4. Enter and confirm the new password.

You may see warnings like BAD PASSWORD: it is based on a dictionary word or BAD PASSWORD: is too simple. These are advisory; the password is changed regardless. Pick something strong if you are going to ignore the warnings.

Uninstalling

Click Add-Ons → FTP → Uninstall. The credentials become inactive and the FTP service stops on the container.

Scaling behaviour

When you horizontally scale a layer that has the FTP add-on installed, the new nodes clone the FTP installation, including the same credentials. GlassFish is the exception — FTP does not clone onto newly added GlassFish nodes. If you want FTP on a multi-node GlassFish setup, uninstall and reinstall after scaling so every node ends up with the add-on.

Where to go from here

  • Log files — the dashboard’s built-in log viewer, for live tailing.
  • SSH access — for direct shell access when FTP is not enough.
  • Public IP — required for FTP to be reachable externally.
  • TLS / SSL — for encrypting transport across the platform’s surfaces.