Arma 3 Server FTP Access: Setup and Key Directories

Why FTP Matters for Arma 3

Running a dedicated Arma 3 server is more than hitting start and walking away. Sooner or later you will want to install mods, edit configs, pull logs, or rebuild a broken file, and all of that happens at the file level. The fastest route into those files is FTP (File Transfer Protocol), which is built into the HolyHosting server panel and also works with any standard desktop FTP client.

This guide walks through both connection methods, highlights the directories that actually matter, and covers the issues that tend to trip up new server owners.

Two Ways to Connect

You have two practical options for opening an FTP session on your Arma 3 server. The first is the built-in panel access, which lives inside your control panel and is the path of least resistance. The second is an external FTP client running on your own machine, which gives you more headroom for large transfers and bulk operations.

Both options reach the same files. The difference is mostly about scale and convenience.

Method 1: Built-in Panel Access

The in-panel option only asks for your password. No host, no port, no username to type out, so it is the quickest way to peek inside the server when you just want to tweak a config or check a file. The trade-off is that the web interface is not designed for very large uploads or downloads, and big transfers can drag.

Once connected, you can browse the directory tree, open editable files with the Edit button, and grab smaller files without leaving the browser.

To connect through the panel:

• Log into the HolyHosting server panel and open the FTP file manager from the panel sidebar.

• Type your password into the field and press Login.

• You should now see the server files, ready to view, download, upload, or edit. Confirm the active Server Profile is the one you intend to work with.

Method 2: External FTP Client

For heavier work, a desktop FTP client is the better tool. Two solid choices are FileZilla and Cyberduck. Both are free, well maintained, and behave themselves on most networks. Other clients will technically work, but if a project demands a specific one, double-check that it is reputable before installing it.

The external route shines for large modpacks, full backups, and anything that arrives as a zip. The catch is that most clients do not include a built-in text editor, so editing a file usually means downloading it, changing it locally, and uploading it back.

To set up the connection:

• Download and install your client of choice. FileZilla is a fine default.

• Open the application and keep it on screen.

• In your server panel, open the FTP section and copy the FTP Address, Port, Username, and Password.

• Paste those four values into the matching fields in the client, then hit Quickconnect or its equivalent.

• If the credentials check out, the remote pane fills up with your server files and you are ready to transfer.

Files and Folders Worth Knowing

Once you are inside, the directory tree can feel a bit busy. Most owners only really need to understand a handful of locations.

Before going hunting in FTP, remember that your panel's config editor and server settings sections already expose the most common options: server password, MOTD, slot count, and similar tweaks. Those panel sections write to the same files you can reach through FTP, just with a friendlier interface. If you prefer to edit it raw, the actual file is `server.cfg`, sitting in the server root.

The `/keys` folder is the one to know if you plan to run mods. Each mod ships with a `.bikey` file that has to live in this directory so the server accepts clients running that mod. Most mod managers copy these files into place automatically, but when installing manually, this is where to drop them. Skip this step and the mod simply will not load.

The `/logs` directory keeps a record of past sessions and is useful when investigating a crash, a banned player, or a mystery disconnect. You do not need to read logs every day, but knowing they exist saves a lot of pain when something breaks. Nearby, the `mpmissions` folder holds the multiplayer scenarios available to your server. New missions go here, in `.pbo` form.

Common Issues

Connection refused or login fails. Nine times out of ten this is wrong credentials. Re-copy the FTP Address, Port, Username, and Password from the panel, then paste them in fresh. If those are correct, check that a local firewall or antivirus is not blocking the FTP client.

Uploads or downloads stall. Single large files often choke. Zip them first. The in-panel interface has a built-in compress action you can use on existing files; for an external client, a desktop tool like 7-Zip or WinRAR will do the same on your computer before you upload.

Files appear to be missing. This is almost always a Server Profile mix-up. Each profile has its own directory, so uploading to profile A and looking in profile B will produce a very convincing magic trick. Confirm the correct profile is selected both when uploading and when verifying.

Related Reading

• Adding mods to an Arma 3 server
• Becoming an admin on Arma 3 servers
• Arma 3 optimization
• More Arma 3 guides on HolyHosting