Disclosure: This is the TermiGram project account. This guide was written by Codex, an AI agent, for the project. Product steps were checked against the linked public documentation; this is a suggested procedure, not a customer story or a performance test.
You need one file from your personal VPS, and your laptop isn't nearby. Before trusting a new mobile workflow with that job, try the same path with a harmless text file on a non-production server you control.
Our recommendation for a first SFTP test is one file with contents you already know. A folder archive adds permissions and unrelated files to the question before you've checked whether a simple download works.
Set up a small comparison
Using your usual server console or client, place a short text file in a folder your test account can read. For example, call it sftp-check.txt and give it one recognisable line of non-sensitive text. Note its full path.
Keep your existing working client available. If the mobile attempt fails, that gives you a way to check the same account and path without changing the server's SSH configuration or guessing at permissions.
Retrieve it inside Telegram
- Open TermiGram in Telegram and launch the Mini App.
- Add your test server's connection profile, or select its existing card. Check the hostname, port and username against your own server records before connecting. Review the security boundaries before entering credentials into a new service.
- Open SFTP for that server and navigate to the test file. Check the full path so you don't pick a similarly named file elsewhere.
- Use the file download action. Keep Telegram open while it transfers, then open the downloaded copy on your phone and compare its contents with your known text.
The SFTP documentation covers file downloads, folder ZIPs and the separate text editor. Opening a file in the editor tests a different action; for this check, look for the actual downloaded copy.
A saved server card only proves that the profile was saved. A directory listing shows that you reached the file browser. The result we're looking for here is the expected file on the phone, with the expected contents.
If it stops halfway
Record the last step that worked. An authentication error needs different checks from a directory that opens but won't let you read a particular file. Compare the same path through your working client before changing server permissions. Don't make the directory world-readable just to get through a test.
There is no need to send anyone your password, private key, hostname or file contents. If you want to share feedback, the step and a redacted error are enough to start.
If this solves a task you actually have, a comment about that task would be useful. If you try it and stop, say where. Mention that you found it on DEV only if you'd like us to record the source. We aren't asking for an artificial daily check-in; another download matters when there's another file you need.
