ftp

FTP / FTPS

Name: Nexoxa Bridge
Author: Nexoxa

Remote file transfer over ftp://, ftpes, and ftps:// with the dual-pane studio.

FTPftp://user:password@host:21/var/www

The story

These pages use illustrative scenarios (sample names and timelines) to explain real Nexoxa Bridge features. Connection URLs, sidebar panels, and vault behavior match the product; story details are teaching examples, not customer case studies.

Legacy hosting still means FTP — shared cPanel boxes, old agency servers, and that one client who never enabled SFTP. Frontend dev Lee used FileZilla until passwords lived in Site Manager plain text and FTPS modes were guesswork every connect.

Lee saved ftp://legacy-client with ?secure=explicit for port 21 FTPES and ftps://archive:990 for implicit TLS. Dual-pane studio matches SFTP: local build left, remote /var/www right, queue for 200 assets, chmod from context menu. Plain FTP works when the host is air-gapped and ugly — but TLS modes are documented in the connect panel.

FTP is legacy; your workflow does not have to be.

Connection URL

Scheme: ftp://

Parameters

Plain FTPstringvaultrequired

ftp://user:password@host:21/var/www

FTP with explicit TLS (FTPES)stringvaultrequired

ftp://user:password@host:21/uploads?secure=true — Use ?secure=true or ?secure=explicit on port 21.

Implicit TLS (FTPS)stringvaultrequired

ftps://user:password@host:990/var/www — ftps:// uses implicit TLS — typically port 990.

Paste the URL in Nexoxa Bridge → New connection. Save a human-readable name — MCP references that name, not the raw URL with embedded passwords.

Step 1

Dual-pane studio

Lee drags dist/ to remote public_html, watches the queue, and chmods 755 on assets folder from the right-click menu. Same UX as sftp:// — muscle memory intact.
Remote path in the URL seeds the initial right pane directory.

ftp://user:pass@host:21/path with optional ?secure=true for FTPES. ftps:// for implicit TLS on port 990. Dual-pane file manager with transfer queue and permission edits.

Step 2

TLS modes

A host rejects implicit FTPS on 990 but accepts explicit on 21 — Lee toggles ?secure=explicit, reconnects green, and ships. No third-party wiki tab hunt.
Connect dialog documents explicit vs implicit with port hints.

FTPES via ?secure=true or ?secure=explicit on port 21. ftps:// scheme for implicit TLS typically on 990. Plain ftp:// when required for local dev only.

Explore the full feature guide: FTP dual-pane feature