> For the complete documentation index, see [llms.txt](https://docs.gremsy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gremsy.com/gremsy-tiny-series/lynx/software-configuration/web-setting-app/media-files.md).

# Media Files

<figure><img src="/files/yUdrkxzdk1rqAETQHgqT" alt=""><figcaption></figcaption></figure>

## File Transfer Manager – User Guide

<figure><img src="/files/CCPisQfieT2yQ2UjGRji" alt=""><figcaption></figcaption></figure>

### Overview

The **File Transfer Manager** allows users to transfer media files from the payload’s internal storage (`/sdcard`) to an external computer or server using:

* **USB Transfer** *(ORUS-L only)*
* **SSH Transfer**

This page is mainly used for exporting captured media, logs, or mission data securely over a network.

***

## SSH Transfer

The **SSH Transfer** tab enables secure file copying from the payload to a remote server using the SSH protocol.

#### Source Directory

The source path is fixed as:

```
/sdcard
```

This directory contains media files stored on the payload.

***

## Field Descriptions

### Remote Host

IP address or hostname of the destination server.

#### Example

```
192.168.1.100
```

or

```
server.example.com
```

#### Notes

* Ensure the server is reachable from the payload network.
* Verify both devices are on the same LAN or connected network.

***

### Username

SSH account username used to authenticate with the remote server.

#### Example

```
admin
```

or

```
root
```

***

### Password

SSH account password for authentication.

#### Notes

* Password is required unless the server supports key-based authentication.
* Ensure the account has write permission to the destination path.

***

### Destination Path

Full directory path on the remote server where files will be copied.

#### Example

```
/home/user/media
```

or

```
/mnt/storage/files
```

#### Notes

* The directory must already exist.
* User permissions must allow writing to this location.

***

### Port

SSH communication port.

#### Default

```
22
```

#### Notes

* Change this only if the remote SSH server uses a custom port.
* Ensure firewall rules allow access to this port.

***

## Starting the Transfer

1. Enter all required SSH connection information.
2. Verify network connectivity between the payload and remote server.
3. Click:

```
START SSH TRANSFER
```

4. The system will begin copying files from `/sdcard` to the remote destination.

***

## Advanced Settings

The **Advanced Settings** section provides additional transfer configuration options for advanced users.

Possible configurations may include:

* Transfer retry behavior
* File overwrite policy
* Compression options
* Bandwidth limitation
* Recursive directory copy

***

## Recommended Workflow

### Local Network Transfer

1. Connect payload and computer to the same network.
2. Enable SSH service on the destination machine.
3. Use the machine IP as the **Remote Host**.
4. Start transfer.

***

## Troubleshooting

### Connection Failed

Possible causes:

* Incorrect IP address
* SSH service not running
* Firewall blocking port 22
* Network disconnected

***

### Authentication Failed

Possible causes:

* Wrong username or password
* User account disabled
* Insufficient permissions

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.gremsy.com/gremsy-tiny-series/lynx/software-configuration/web-setting-app/media-files.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.