# Set up Packs Server > Install Packs Server on Linux and connect Oasis to it. Source: https://oasis-protection.com/docs/packs-server/setup/ Most servers don’t need this. If you aren’t sure, read [Embedded or Packs Server?](/docs/guides/embedded-or-server/) first. ## What you need * A Linux machine with one of these systems: * Debian 13 (trixie) or newer, or Ubuntu 24.04 or newer * Fedora 44 or newer, or RHEL 10 and its rebuilds, such as Rocky Linux and AlmaLinux * openSUSE Leap 16 or Tumbleweed * Arch Linux * Root access, through `sudo` or a root shell. * About 2 GB of free memory for Packs Server. You can [change that later](/docs/packs-server/operations/#give-packs-server-more-memory). The usual setup is Packs Server on the same machine as your Minecraft server, and that’s what this guide sets up. ## 1. Install Packs Server Pick your system, then the tab that matches your Oasis: Release for a release of Oasis, Dev for a [dev build](/downloads/?channel=dev). Then run the whole block as root: **Debian and Ubuntu** **Release** Terminal window ```sh mkdir -p /etc/apt/keyrings curl -fsSL https://oasis-protection.com/packs.asc -o /etc/apt/keyrings/packs.asc echo "deb [signed-by=/etc/apt/keyrings/packs.asc] https://telesphorepo.com/debian/packs-server-deb/ stable main" > /etc/apt/sources.list.d/packs.list apt update apt install packs ``` **Dev** Terminal window ```sh mkdir -p /etc/apt/keyrings curl -fsSL https://oasis-protection.com/packs.asc -o /etc/apt/keyrings/packs.asc echo "deb [signed-by=/etc/apt/keyrings/packs.asc] https://telesphorepo.com/debian/packs-server-deb-dev/ stable main" > /etc/apt/sources.list.d/packs.list apt update apt install packs ``` If `curl` is missing, install it first with `apt install curl`. **Fedora and RHEL** **Release** Terminal window ```sh cat > /etc/yum.repos.d/packs.repo <<'EOF' [packs] name=Packs Server baseurl=https://telesphorepo.com/rpm/packs-server-rpm/ gpgcheck=1 repo_gpgcheck=1 gpgkey=https://oasis-protection.com/packs.asc metadata_expire=1h EOF dnf install packs ``` **Dev** Terminal window ```sh cat > /etc/yum.repos.d/packs.repo <<'EOF' [packs] name=Packs Server baseurl=https://telesphorepo.com/rpm/packs-server-rpm-dev/ gpgcheck=1 repo_gpgcheck=1 gpgkey=https://oasis-protection.com/packs.asc metadata_expire=1h EOF dnf install packs ``` dnf asks once whether to trust the key of Packs Server. Say yes if its fingerprint is `E1BA EE0F B8E8 FD38 BD59 64ED 3515 7D66 8BB2 FA00`. **openSUSE** **Release** Terminal window ```sh rpm --import https://oasis-protection.com/packs.asc cat > /etc/zypp/repos.d/packs.repo <<'EOF' [packs] name=Packs Server baseurl=https://telesphorepo.com/rpm/packs-server-rpm/ gpgcheck=1 repo_gpgcheck=1 autorefresh=1 EOF zypper install packs ``` **Dev** Terminal window ```sh rpm --import https://oasis-protection.com/packs.asc cat > /etc/zypp/repos.d/packs.repo <<'EOF' [packs] name=Packs Server baseurl=https://telesphorepo.com/rpm/packs-server-rpm-dev/ gpgcheck=1 repo_gpgcheck=1 autorefresh=1 EOF zypper install packs ``` **Arch Linux** **Release** Terminal window ```sh curl -fsSL https://oasis-protection.com/packs.asc -o /tmp/packs.asc pacman-key --add /tmp/packs.asc pacman-key --lsign-key E1BAEE0FB8E8FD38BD5964ED35157D668BB2FA00 grep -q '^Include = /etc/pacman.d/packs.conf' /etc/pacman.conf || echo 'Include = /etc/pacman.d/packs.conf' >> /etc/pacman.conf printf '[packs-server-arch]\nSigLevel = Required\nServer = https://telesphorepo.com/arch/$repo/$arch\n' > /etc/pacman.d/packs.conf pacman -Syu packs ``` **Dev** Terminal window ```sh curl -fsSL https://oasis-protection.com/packs.asc -o /tmp/packs.asc pacman-key --add /tmp/packs.asc pacman-key --lsign-key E1BAEE0FB8E8FD38BD5964ED35157D668BB2FA00 grep -q '^Include = /etc/pacman.d/packs.conf' /etc/pacman.conf || echo 'Include = /etc/pacman.d/packs.conf' >> /etc/pacman.conf printf '[packs-server-arch-dev]\nSigLevel = Required\nServer = https://telesphorepo.com/arch/$repo/$arch\n' > /etc/pacman.d/packs.conf pacman -Syu packs ``` This installs Java 25 if you don’t have it already, then starts Packs Server. It starts again by itself whenever the machine reboots. [Run Packs Server](/docs/packs-server/operations/#update-it) shows how to update it. To switch between dev builds and releases later, run the other tab’s block. A dev build you already have stays until the next release comes out, and then the update installs it as usual. ## 2. Make a store A store holds the history of one Minecraft server. Make one, plus a key that your server uses to log in: Terminal window ```sh packs store create survival packs key add survival paper ``` The second command prints two keys: **the private key** and **the server key**. Copy both now, because Packs Server shows the private key only once. If you lose it, run `packs key add` again with a new name. [The `packs` command](/docs/packs-server/cli/) lists everything else it can do. ## 3. Connect Oasis Open `plugins/Oasis/config.yml` on your Minecraft server and fill in the `storage` section: ```yaml storage: engine: server server: address: 127.0.0.1:7650 store: survival key: "paste the private key here" server-key: "paste the server key here" ``` Restart your Minecraft server. Then run `/oasis status`. It should say **Packs Server**. ### Pterodactyl and Pelican With a panel, your Minecraft server runs inside a container. Inside that container, `127.0.0.1` means the container itself, not the machine that runs Packs Server, so Oasis needs a different address. The panel gives every container a private network that reaches the machine, and Packs Server can listen there. First, find that network’s address. Open Wings’ config file, `/etc/pterodactyl/config.yml` for Pterodactyl or `/etc/pelican/config.yml` for Pelican, and look under `docker`, then `network`, then `interface`. It’s usually `172.18.0.1`. Next, tell Packs Server to listen on it. Open [`/etc/packs/packs-server.properties`](/docs/packs-server/properties/), change the `listen` line, and restart Packs Server: ```properties listen = 172.18.0.1:7650 ``` Terminal window ```sh systemctl restart packs-server ``` Finally, use the same address in Oasis’s config: ```yaml address: 172.18.0.1:7650 ``` If you run a firewall like `ufw`, let the containers through with `ufw allow from 172.18.0.0/16 to any port 7650`. ### Packs Server on another machine Keep Packs Server on the same machine as your Minecraft server, or on the same local network, such as two VMs on one host. A longer distance makes lookups and rollbacks slower. Nothing stops you from running it further away. Two servers in the same data center may be close enough that you never notice. If you try it, test lookups and rollbacks on your own setup and decide whether the delay is acceptable to you. Set [`listen`](/docs/packs-server/properties/#listen) to an address your Minecraft server can reach, put that address in Oasis’s config, and open port 7650 in the firewall to your Minecraft server’s address only. The connection is encrypted over TCP, wherever the two run. The keys you made in step 2 prove each side to the other, and each connection gets fresh keys of its own, so nobody between the two machines can read your history or change what Oasis sends. ## 4. Bring your history along If you used Packs Embedded before, your old history is still in `plugins/Oasis/store`. Oasis reminds you about it at startup. To bring it over, run: ```plaintext /oasis move /oasis move confirm ``` Lookups and rollbacks are paused until the move finishes. `/oasis move status` shows how far it has got. If you cancel the move or it fails, the old copy stays untouched, and you’re back where you started. When the move ends, Oasis renames the old store and does not delete it. With Packs Embedded, the old copy waits in `plugins/Oasis/store-moved-