Read in 5 minutes
·Getting Started

Deploying Your Server

A step-by-step walkthrough for deploying your server from purchase to going live.

#Tutorials#Deployment#Basic#Setup

Your order is confirmed — now let's get your server live. This guide covers the full deployment flow from package selection to a running server.

1

STEP 1Select the package

Log in to the billing panel at my.tariqdev.xyz and navigate to Game Hosting or App Hosting. Pick the tier and RAM allocation that matches your workload.

Once purchased, your server will be provisioned automatically within 2–5 minutes.

2

STEP 2Configure deployment variables

Open your server in the control panel (ctrl.tariqdev.xyz). Go to the Startup tab and configure the required environment variables for your game or application — things like server name, world seed, RCON password, and game mode.

Warning:

Do not share your API key, RCON password, or SHA-256 hash publicly. These grant full control over your server.

3

STEP 3Set up automated backups

Before starting your server for the first time, configure your backup schedule. Go to Schedules → Backup in the control panel and set a daily or weekly backup.

Backup before changes

Always create a manual backup before applying mods, plugins, or major configuration changes. Restoring from backup is instant.

Note:

The free plan includes 2 backup slots. Upgrade to a paid backup add-on for unlimited slots and off-site storage.

4

STEP 4Start your server

Go to the Console tab and click Start. Watch the console output for any startup errors. Most games take 30–90 seconds to fully boot.

Once you see the "Server started" or equivalent line in the console, your server is live.

5

STEP 5All set — share your IP

Copy your server IP from the Network tab. This is what players will use to connect. Format: [IP]:[PORT].

Your server will keep running in the background even if you close the browser. To stop it, use the Stop button in the Console tab.

Common First-Boot Issues

Server won't start? Check the console for errors. The most common causes:

  • Port already in use → restart the server once, it will auto-assign a new port
  • Missing startup variable → go to Startup and fill in all required fields
  • Out of RAM → the process was killed by the OOM guard. Upgrade your RAM allocation.
Do not skip backups

We guarantee hardware and network uptime, but we are not responsible for data loss caused by user error, software crashes, or failed updates. Always maintain your own backups.