Files and SFTP
Each server has a data directory: maps, configs, saves, plugins. There are two ways to work with it — the panel's file manager or SFTP.
File manager
The Files tab on the server's page:
- + File, + Folder, Upload file;
- open a text file (a config,
server.properties) and edit it right in the browser; - Rename, Copy, delete;
- tick several files and pack them into a
.tar.gzarchive; - Extract — unpack an archive into the current folder or another one.
Non-text files are opened with Download.
Most games read their configs at start, so restart the server after editing.
SFTP
For large files and bulk uploads an SFTP client is handier: FileZilla, WinSCP or sftp in a terminal. The login details are in the Direct SFTP access block on the Files tab: Host, Port, Login and Password, plus a ready-made terminal command.
- The default port is 22. If the node uses another SFTP port, use that one.
- Each server has its own login, which sees only that server's data directory.
- Generate new — issue a new password. The old one stops working at once; sessions already open aren't dropped.
- Set your own… — your own password: 8–128 characters, Latin letters, digits and symbols, no spaces.
SFTP access can be turned off in the plan (Disable SFTP, see Plans). Logins are then blocked within a few seconds while the panel's file manager keeps working. The password and files are kept, and everything works as before when it's turned back on.
The node must have the SFTP port open (usually 22/tcp), see Connect a node.
Restrictions for customers
The file manager settings are in Modules → File manager → Settings. They take effect immediately, no restart needed.
File size — how much can be opened in the editor or uploaded through the browser at once. 512 KB by default, 16 MB at most. Upload larger files over SFTP.
A file travels to the node through NATS as a single message, a third larger than the original. With NATS' standard max_payload of 1 MB, files over ~700 KB won't get through. If you set a larger size, raise max_payload in the NATS config — the panel shows the required value below the field.
Protected paths — files and folders the customer can't change, delete, rename, move or overwrite. They can still see and download them. Patterns go one per line, relative to the server's file root:
*.so— a name without/matches at any depth;bin/*— a pattern with/counts from the root;**— any number of folders;- a folder protects everything inside it.
For all games patterns apply to every server. Under For individual games you can add patterns for a specific game — they're added to the common ones. For example, for Counter-Strike 1.6:
hlds_linux cstrike/liblist.gam
Blocked extensions — files with these extensions can't be uploaded or created by the customer: not by upload, rename, copy or archive extraction. Separate extensions with spaces or commas; case doesn't matter. Add the standard set adds .exe .bat .cmd .ps1 .sh .so .dll. If customers install BepInEx mods, Oxide or SourceMod plugins themselves, remove .dll and .so from the list.
The restrictions apply to server owners and co-owners. Admins and staff allowed to manage all servers work without them.
These rules don't cover SFTP. If protection matters, turn SFTP off in the plan.
What's inside folders and archives (say, a protected file in a folder being deleted, or an .exe in an archive being extracted) is checked by the node's agent. An older agent checks only the paths named explicitly — update your agents, see Updates.
Files and maps/mods
Install catalog add-ons from the Maps and mods tab — that way the panel knows what's installed and can update or remove an add-on cleanly. Files uploaded by hand aren't tracked. If you edited an add-on's files over SFTP, Verify against the server on the Maps and mods tab shows what changed.