HELP & SUPPORT

Support

Getting started

Prepare an authorized frps server and configuration, create a profile in FerryPorts, save it, and enable the connection. Review status and logs in profile details. Grant location access only if you want location labels for connection records.

Connection troubleshooting

If a connection fails, check the server address, port, credentials, server availability, and network access. Temporary failures may trigger limited retries. Use Retry Now after correcting a configuration. Background connectivity depends on iOS, permissions, and network conditions.

What if the connection drops when the app goes into the background?

We recommend allowing background location access for FerryPorts. Open iOS Settings → Privacy & Security (Privacy on older iOS versions) → Location Services → FerryPorts, then select Always. If Always is not available yet, grant location access when prompted in the app, then check Settings again.

Background location labels active connection records with approximate locations and may help connections stay active longer in the background. The app’s ability to remain running still depends on iOS scheduling and network conditions. Avoid force quitting the app from the app switcher. If a connection drops, return to the app, review its status and logs, and use Retry Now.

How do I import client certificates and private keys?

Open More → Certificates and Keys → Import Files to select PEM certificates, unencrypted private keys, and CA files. You can also share or open files from Files in FerryPorts. If iOS does not offer FerryPorts for a .key file, rename it to .pem or use the in-app importer.

Each file is limited to 1 MiB. PKCS#12 and encrypted private keys are not supported. On a trusted computer, use openssl pkey -in encrypted.key -out private.pem to remove the password before importing.

Tap a certificate or key and select a profile in Apply to… to replace its corresponding TLS setting. Certificates, private keys and CA files configure certFile, keyFile and trustedCaFile respectively; combined files configure both certificate and key. Swipe left to rename or delete. Renaming preserves the extension and updates profile references. Restart affected profiles after replacing a file.

Private keys are stored as plaintext PEM inside the app container, protected by iOS Data Protection after first unlock and excluded from iCloud and Finder backups. There is no application-level encryption or export feature. You manage the original external files. Before deletion, the app warns about profiles that reference the file.

Feedback and privacy questions

Send feedback through GitHub Issues or email eric_kwoc@icloud.com. GitHub Issues are public; email goes directly to the author and is not displayed publicly. Include your app and iOS versions, reproduction steps, and sanitized errors. Never post credentials, full configurations, private keys, personal locations, or sensitive logs. For privacy questions, please contact the author by email. See our Privacy Policy for storage and deletion information.