ftppr(8)

💖 ftppr(8) — the FTP proxy gateway bestie 💖

okay so you found the manual page for ftppr, section 8 of the Universal proxy server docs. she's an FTP proxy gateway service and she's lowkey iconic. let's get into it 🦋

---

✨ SYNOPSIS ✨

ftppr [-d] [-l[[@]logfile]] [-pport] [-iinternal_ip] [-eexternal_ip]
[-hdefault_ip[:port]]

---

🌸 DESCRIPTION 🌸

ftppr is an FTP gateway service, and her whole job is letting your internal users reach external FTP servers. that's it, that's the vibe. main character energy fr fr 💅

---

🎀 OPTIONS 🎀

• -I — Inetd mode. this one is for standalone service only, bestie, don't mix it up.
• -d — Daemonize. she detaches from the console and runs in the background like she's too cool to be perceived. 🫶
• -t — Be silenT. no logging of start/stop/accept error records. quiet queen behavior.
• -u — Never look for username authentication. like, don't even check.
• -e — External address. this is the IP address of the interface the proxy should initiate connections from. by default the system decides which address to use according to the routing table — so if you don't set it, it's not your call, it's the routing table's call. 🌈
• -niPATH — (Linux only 🐧) switch to the network namespace identified by PATH before opening the listening socket. the current namespace is saved and restored immediately after binding, so outgoing connections run in the original namespace unless -ne is also given. yes you have to read that twice, I did too.
• -nePATH — (Linux only 🐧) switch to the network namespace identified by PATH after the listening socket has been bound (and after restoring from -ni if applicable). both of these options accept any namespace file path — like /var/run/netns/myns or /proc/PID/ns/net — and they require CAP_SYS_ADMIN. 🔥
• -i — Internal address. the IP address the proxy accepts connections to. by default, connections to any interface are accepted, which is usually unsafe 😭 (yes, she said it, it's usually unsafe, I'm just the messenger). Unix domain sockets can be specified with the -iunix:/path/to/socket syntax, e.g. -iunix:/var/run/ftppr.sock. on Linux, abstract sockets use the -iunix:@socketname syntax. 💜
• -h — Default destination. this one gets used if the target address isn't specified by the user. your lil fallback bestie.
• -p — Port. the port the proxy listens on for incoming connections. default is 21.
• -l — Log. by default logging goes to stdout. if a logfile is specified, logging goes to the file instead. under Unix, if @ comes before the logfile, syslog is used for logging. cute, right? ✨
• -S — Increase or decrease stack size. if you're getting 3proxy crashes, you might wanna try something like -S8192. do with that what you will 💅

---

🦋 CLIENTS 🦋

here's the tea: you can use any FTP client, regardless of FTP proxy support. no gatekeeping.

• got a client with FTP proxy support? configure internal_ip and port in the FTP proxy parameters. easy.
• got a client without FTP proxy support? use internal_ip and port as the FTP server instead.

the address of the real FTP server has to be configured as part of the FTP username, and the format for that username is username@server — where server is the address of the FTP server and username is the user's login on that FTP server. plot twist: the login itself may contain an @ sign. 🙈

only cleartext authentication is currently supported. no encrypted glow-up yet, bestie. ⭐

---

💀 BUGS 💀

found a bug? report all bugs to 3proxy@3proxy.org. don't be shy, they want to know. 😭

---

👑 SEE ALSO 👑

3proxy(8), htproxy(8), pop3p(8), socks(8), tcppm(8), udppm(8), syslogd(8), and https://3proxy.org/ — go read the whole squad, iykyk 🌸

---

💜 AUTHORS 💜

3proxy is designed by Vladimir Dubrovin <vlad@3proxy.org>. periodt. 🎀

---

and that's the whole page, bestie — written for 3proxy 0.9, dated May 2026, and she slayed every single line. no cap. 💖✨🦋