> For the complete documentation index, see [llms.txt](https://docs.glesys.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glesys.com/products/storage/archive-storage/how-tos/access-an-archive.md).

# Access an archive

***

To access the archive, you first need to find its address. The address can be found in the archive overview. It is listed under the username you chose when creating the archive.

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

The way you access the archive varies depending on the protocol.

{% tabs %}
{% tab title="FTPS" %}
Once you have the address, log in to the archive using FTPS. It's best to avoid the standard FTP protocol as it is completely unencrypted. FTPS uses TLS, making it much more secure.

A simple and effective program for FTPS (and also FTP) is FileZilla. It is free and open source, available for Windows, Linux, and macOS.

In Linux, it's available in most package managers and can be installed with `sudo apt install filezilla` in Debian and Ubuntu, and with `sudo dnf install filezilla` in Fedora and AlmaLinux. For Microsoft Windows and macOS, you can download it directly from the [FileZilla website](https://filezilla-project.org/).

To add the Glesys archive in FileZilla, click **File** and then **Site Manager...**.

<div align="left"><figure><img src="/files/XCpr3m3bJ1i4R4mVB0v8" alt=""><figcaption></figcaption></figure></div>

When the *Site Manager* dialog box opens, click **New Site**.

<div align="left"><figure><img src="/files/efKcidCWGviKi4JKLqCE" alt=""><figcaption></figcaption></figure></div>

In the dialog box that opens, fill in all the required details to connect to the archive. Also, give this *site* a name. Here, we'll name it *Glesys Archive*. The details to fill in are:

* **Protocol:** FTP - File Transfer Protocol
* **Host:** Enter the address of the archive. You can find this under the username for the archive in the control panel.
* **Encryption:** Use explicit FTP over TLS if available
* **Port:** 21 (the default port for FTP)
* **Logon Type:** Normal
* **User:** Enter the full username we chose when creating the archive, in the format clXXXXX\_name.
* **Password:** The password you chose when creating the archive.

Once all the details are filled in, click **Connect**. The settings will be saved, and we will be connected to the archive.

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

The first time you connect, you will be prompted to save the password for future use. If that's what you want, leave **Save passwords** checked and click **OK**. Note that this applies to all passwords in FileZilla.

The first time you connect to the Glesys archive, you will receive a warning that the certificate is unknown. FileZilla does not verify certificates against a CA in the same way a web browser does. Here, tick the checkbox **Always trust this certificate in future sessions** and click **OK**. If there were any issues with the certificate, it would not be possible to check this box.

<div align="left"><figure><img src="/files/tYOMUTmAGssh3dzmsqI4" alt="" width="478"><figcaption></figcaption></figure></div>

If you have entered the correct username and password, you are now connected to the archive and can transfer files. Files from the local computer are displayed on the left, and the archive is shown on the right.

<div align="left"><figure><img src="/files/bUg90FEbm92PWNDTgZhD" alt=""><figcaption></figcaption></figure></div>

Now, you can drag and drop files between the local computer and the archive.
{% endtab %}

{% tab title="FTP" %}
You can also connect to the archive using standard FTP, for example, with the built-in FTP client available in most operating systems. However, this should be avoided since the standard FTP protocol is completely unencrypted.

To connect, specify the archive's address as an argument to the `ftp` command. The program will then prompt for a username and password. Here, enter the username and password you created when setting up the archive. In the example below, the dollar sign (`$`) denotes the shell prompt.

<pre data-title="FTP session. Commands and prompts are highlighted."><code><strong>$ ftp archive0c.glesys.com
</strong>Trying 5.178.76.83...
Connected to archive0c.glesys.com (5.178.76.83).
220 ::ffff:5.178.76.83 FTP server ready
<strong>Name (archive0c.glesys.com:glesys): cl43212_glesys
</strong>331 Password required for cl43212_glesys
<strong>Password:
</strong>230-================================================================
   -+- a property of GleSYS Internet Services AB -+-
   ________.____     ___________ ______________.___. _________
   /  _____/|    |    \_   _____//   _____/\__  |   |/   _____/
   /   \  ___|    |     |    __)_ \_____  \  /   |   |\_____  \
   \    \_\  \    |___  |        \/        \ \____   |/        \
   \______  /_______ \/_______  /_______  / / ______/_______  /
   \/        \/        \/        \/  \/              \/
   ================================================================
230 User cl43212_glesys logged in
Remote system type is UNIX.
Using binary mode to transfer files.
<strong>ftp>
</strong></code></pre>

You are now connected to the FTP server and can list, delete, and transfer files. An example session is shown below, with `ls`, `put`, and `get` commands. The `ftp>` part indicates the prompt in the FTP client.

<pre class="language-ftp" data-title="FTP session. Commands and prompts are highlighted."><code class="lang-ftp"><strong>ftp> ls
</strong>227 Entering Passive Mode (5,178,76,83,204,128).
150 Opening ASCII mode data connection for file list
226 Transfer complete

<strong>ftp> put rat.jpg
</strong>local: rat.jpg remote: rat.jpg
227 Entering Passive Mode (5,178,76,83,214,124).
150 Opening BINARY mode data connection for rat.jpg
226 Transfer complete
119070 bytes sent in 0.0119 secs (9993.29 Kbytes/sec)

<strong>ftp> ls
</strong>227 Entering Passive Mode (5,178,76,83,210,244).
150 Opening ASCII mode data connection for file list
-rw-r--r--   1 cl43212_glesys users      119070 Nov 27 09:51 rat.jpg
226 Transfer complete

<strong>ftp> get rat.jpg
</strong>local: rat.jpg remote: rat.jpg
227 Entering Passive Mode (5,178,76,83,208,93).
150 Opening BINARY mode data connection for rat.jpg (119070 bytes)
226 Transfer complete
119070 bytes received in 0.0345 secs (3454.71 Kbytes/sec)
</code></pre>

{% endtab %}

{% tab title="SMB/CIFS" %}
The archive can also be mounted as a Windows share over the SMB protocol. Although the SMB protocol is used, CIFS tools are utilized in Linux and other operating systems.

The archive is accessible via SMB/CIFS at the address shown in the archive overview, just below the username. The name of the share is the username.

In this example, the complete address—including the share—is `\\archive0c.glesys.com\cl43212_glesys`.

## Mount the archive in Linux

Before using CIFS in Linux, you need to install the `cifs-utils` package. The package has the same name in Debian, Ubuntu, Fedora, and AlmaLinux. In Debian and Ubuntu, you install the package with `sudo apt install cifs-utils`. In Fedora and AlmaLinux, you install it with `sudo dnf install cifs-utils`.

Once the package is installed, first try mounting the archive manually. Start by creating a directory to mount the archive in using:

{% code title="Command" %}

```terminal
sudo mkdir /mnt/archive
```

{% endcode %}

Next, mount the archive using the following command: (replace the address and share name)

{% code title="Command" %}

```terminal
sudo mount -t cifs -o username=cl43212_glesys \
//archive0c.glesys.com/cl43212_glesys /mnt/archive
```

{% endcode %}

When you execute the command, it will prompt for the password. Here, enter the password set when creating the archive.

{% code title="Prompt from mount" %}

```terminal
Password for cl43212_glesys@//archive0c.glesys.com/cl43212_glesys:
```

{% endcode %}

Once you have entered the password, the archive is mounted. A listing of the filesystems should now show the archive.

{% code title="Command" %}

```terminal
df -h
```

{% endcode %}

This will yield a result similar to the following:

{% code title="Output" %}

```terminal
Filesystem                             Size  Used Avail Use% Mounted on
devtmpfs                               4.0M     0  4.0M   0% /dev
tmpfs                                  1.8G     0  1.8G   0% /dev/shm
tmpfs                                  732M  8.7M  724M   2% /run
/dev/mapper/cs-root                     37G  2.2G   35G   6% /
/dev/mapper/cs-home                     19G  162M   18G   1% /home
/dev/vda1                             1014M  288M  727M  29% /boot
tmpfs                                  366M     0  366M   0% /run/user/0
tmpfs                                  366M     0  366M   0% /run/user/1000
//archive0c.glesys.com/cl43212_glesys   11G   50M   11G   1% /mnt/archive
```

{% endcode %}

You can now unmount the archive and instead set up automatic mounting. Unmount the archive with:

{% code title="Command" %}

```terminal
sudo umount /mnt/archive
```

{% endcode %}

### Automatic mounting of the archive in Linux

To avoid placing the username and password directly in the `/etc/fstab` file, create a separate file in the user's home directory. Name the file `.archive-cred`. The content of the file should be as follows (but replace with your own username and password):

{% code title=".archive-cred" %}

```terminal
user=cl43212_glesys
password=fkRvxxxyyy
```

{% endcode %}

Then, change the permissions of the file to only allow the user to read it:

{% code title="Command" %}

```terminal
chown 600 .archive-cred
```

{% endcode %}

Now, add the following line to `/etc/fstab` to automatically mount the archive. Replace the *uid* and *gid* numbers to match the user who should have write access to the archive. You can find the *uid* and *gid* using the `id` command.

{% code title="Line in /etc/fstab" %}

```
//archive0c.glesys.com/cl43212_glesys /mnt/archive cifs credentials=/home/glesys/.archive-cred,uid=1000,gid=1000 0 0
```

{% endcode %}

Now, let's try to mount the archive:

{% code title="Command" %}

```terminal
sudo mount /mnt/archive
```

{% endcode %}

{% hint style="info" %}
If all users on the system should be able to read and write to the archive, you can replace `uid=1000,gid=1000` in `/etc/fstab` with `noperm`. However, keep in mind that with `noperm`, all users will have the ability to write and delete files.
{% endhint %}

## Mount the archive in Microsoft Windows

To mount the archive in Microsoft Windows, simply open **File Explorer** and enter the address and name of the archive in the format `\\adress\archivename` in the address bar.

<div align="left"><figure><img src="/files/lHfjfBZiMlploCQ4zDYC" alt=""><figcaption></figcaption></figure></div>

You will now be prompted to enter a username and password. Here, provide the full username (the same as the share name) and the password set when creating the archive.

If you want the archive to mount automatically in the future, check the box to save the password.

### Automatic mounting of the archive in Microsoft Windows

When inside the archive in **File Explorer**, click on the address in the address bar.

<div align="left"><figure><img src="/files/ntfMbnZSy5vtBqECshpU" alt=""><figcaption></figcaption></figure></div>

Now, right-click on the archive name and then on **Map network drive...**.

<div align="left"><figure><img src="/files/idr7fWMEwIfeMPMkXRfX" alt=""><figcaption></figcaption></figure></div>

In the next dialog box, make sure that **Reconnect at sign-in** is checked. Then, click on **Finish**.

<div align="left"><figure><img src="/files/x1uvM5TViL96rRV2SYt4" alt=""><figcaption></figcaption></figure></div>
{% endtab %}
{% endtabs %}


---

# 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.glesys.com/products/storage/archive-storage/how-tos/access-an-archive.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.