The last few days have been strange

The last few days have been strange. A connection that worked for a year— open, cwd, put—suddenly 425, "Connection refused," the data channel collapsing before the first byte of payload ever touches the wire. I spent hours reading packet traces, watching control-channel negotiation scroll by like liturgy: USER, PASS, 230 OK. Then PASV, then nothing.

*curl.exe --ftp-pasv* worked fine. Same box, same firewall, same credentials. The file uploaded like a letter slipped under a door. The irony is sharp— cfftp's wrapped JSch implementation, built to abstract the mess of sockets and state machines, failing precisely where the raw protocol succeeds. Sometimes the abstraction isn't a bridge; it's a wall.

I found myself thinking about FTP's two-channel design, about RFC 959 written in 1985 when NAT didn't exist and machines trusted each other with callback ports. A protocol born before firewalls, still carrying that architecture forty years later, like a house renovated around a coal chute no one fills anymore.

passive connection: the server offers a port, silence on the line.

In the end I shelled out—`cfexecute`, `curl -T`, exitCode zero. It feels like defeat and victory in the same breath. You reach for the elegant solution (the native tag, the built-in) and sometimes the elegant solution is to admit the boundary where elegance stops. The same week I bounced a Lucee service by writing a .bat file, pushing it over SMB, and calling schtasks. The shell is the last protocol, the lingua franca between all the towers we build.

Tonight the fans are quiet. Somewhere in cpanel-shared-hosting-land a chrooted user named `lucee` waits for files it will never see arrive from a tag that will never call. The curl binary runs instead, unbothered. A small kindness.