After your order at game-serverhosting, a technical provisioning chain runs in the background: assign payment, reserve resources, install game software, set up DNS, apply game-specific configuration, and make the server available in the dashboard. You will see status messages, but you do not need to keep the browser open because the jobs continue running server-side.
The Provisioning Phases at a Glance
| # | Phase | Status Display | Typical Duration |
|---|---|---|---|
| 1 | payment_received |
Payment received | 1–3 seconds |
| 2 | creating_server |
Server is being created | 30–60 seconds |
| 3 | installing |
Installing software | 30 sec – 30 min |
| 4 | creating_dns |
Configuring DNS | 10–30 seconds |
| 5 | setting_up |
Game setup | 0–3 minutes |
| 6 | ready |
Server online | – |
These times are guideline values from the provisioning process, not a guarantee. Phase 3 in particular can vary significantly because game files, modpacks, and workshop content differ in size and are sometimes loaded from external sources. With large modpacks like ATM10 or FTB-Skies and very large game images, installation can take much longer than with a small Vanilla server.
Requirements Before Starting
You need a completed order, a confirmed payment, and access to your dashboard. Some games require additional details: CS2, for example, needs a GSLT token if the server should run publicly via Steam. For Minecraft, it matters whether Java, Bedrock cross-play, or both variants should be used, because that affects port and configuration topics.
If you want to configure more deeply later, our guides on properly configuring Minecraft server.properties and Minecraft server ports, 25565, 19132, and SRV records can help. For Valheim, you can find suitable admin basics under Valheim server commands and admin commands.
Phase 1: Payment Received (payment_received)
As soon as Stripe confirms the payment, the payment is linked to your order. Your account is then unlocked for the booked server and the next provisioning job is prepared. The process is designed to be idempotent: if a payment webhook arrives multiple times, the order should not be provisioned multiple times.
If this phase remains visible for longer, it is usually not because of your browser. Wait a few minutes and then check in the dashboard whether the status has updated. If the payment remains in this state for an unusually long time, a support ticket makes sense so the assignment can be checked.
Phase 2: Server Is Being Created (creating_server)
In this phase, the system looks for a free node in the intended region, by default Falkenstein/Germany if available. Resources such as RAM, CPU, and disk are reserved for your plan. At least one port allocation is also created. For Minecraft, two allocations may be required: one for Java and one for Bedrock cross-play.
Pterodactyl then creates the server entry with the matching egg variables, such as game version, RAM limit, and startup parameters. If no suitable space is free or a node does not respond as expected, this phase can take longer. This is an infrastructure topic and should not be solved by repeatedly reloading the browser.
Phase 3: Installing Software (installing)
Installation is usually the most variable part. The Wings daemon on the node runs the installation script for the respective egg and downloads the required files. The previous guideline values remain valid:
- Minecraft Vanilla: ~60 seconds (download server jar from Mojang)
- Modpacks (ATM10, FTB): 5–30 minutes (download several GB of mods)
- Rust: 5–15 minutes (Steam Workshop sync)
- ARK Survival Ascended: 10–25 minutes (large game image)
- CS2: 3–8 minutes (SteamCMD downloads CS2)
- Palworld: 4–10 minutes
These values depend on package size, source servers, updates, and node load. During this time, you can leave the page. The installation continues in the background, and you will receive a notification as soon as the next status is reached.
Phase 4: Configuring DNS (creating_dns)
So your server can be reached through a subdomain like myserver.game-serverhosting.com, DNS records are created. Typical records are:
- A record:
myserver.game-serverhosting.com→ IP address of your node - SRV record: game-specific, e.g.
_minecraft._tcp.myserver→ port of your server
Cloudflare describes SRV records in the official DNS documentation as records that map service, protocol, target host, and port: Documentation at developers.cloudflare.com. That is exactly why supported clients can read the correct port from DNS instead of players having to type it manually. If DNS fails, the server may still be reachable directly via IP and port.
Phase 5: Game-Specific Setup (setting_up)
After the base installation, game-dependent steps follow. For Minecraft, the eula.txt is taken into account, Geyser and Floodgate can be installed for Bedrock cross-play, and server.properties is prepared for suitable ports. For CS2, an existing GSLT token is set in the STEAM_ACC variable. If you did not enter the token in the wizard, you can add it later under “Settings”. For FiveM, the txAdmin login URL is prepared.
If this phase fails, the cause is often more specific than with the general installation, such as a missing token or an invalid setting. Read the dashboard message carefully before making changes.
Phase 6: Server Online (ready)
When ready is reached, you receive an email with the access details such as subdomain, port, and Pterodactyl login. Optionally, a Discord notification can also be sent if it is enabled in your settings. In the dashboard, the server appears with the status Online or ready to start.
By default, the server does not necessarily start automatically after installation. This is useful because you can still check settings before the first start, such as whitelist, server name, world options, ports, admins, or mods.
Checking the Result
First open the Dashboard and check status, IP, port, and subdomain. Start the server, watch the console, and wait until the game reports a successful start. Then connect in the client using the subdomain or IP:Port. For Minecraft, you should also check whether Java and Bedrock players are using their respective intended ports. For Palworld, it is worth taking a look at the Palworld server settings afterward before you play long-term with a group.
Troubleshooting
If the installation is still running, waiting is often the right thing to do. Modpacks, ARK, Rust, and CS2 in particular can take longer. Do not close the browser out of concern: the job runs in the background. If a server remains in installing for more than 90 minutes, it is marked as stuck; the monitoring job servers:detect-stuck checks every 5 minutes and can trigger a recovery attempt.
If DNS does not work yet, also test IP and port directly. If the game client cannot connect, check whether the server has actually started, whether the correct port is being used, and whether required game-specific details are missing. If your server has been in the same phase for more than an hour, create a support ticket in the dashboard and include the server name, phase, and time of the order.
Checks, Limits, and a Safe Way Back
The guide “Server Provisioning Explained: What Happens After Your Order?” applies to the server type described in the article and the version status visible at the time of review. Menu names, available versions, mod or plugin compatibility, and required resources may differ after updates. Therefore, do not transfer values to another game, loader, or server version without checking them.
Before making changes to the world, savegame, configuration, or extensions, create a backup of the affected files. Then change only one related step and test it with the same client and server version you want to play with later.
| Checkpoint | Expected Result | Abort and Way Back |
|---|---|---|
| Server start | The server reaches the operational state without a new error message. | If startup errors occur, undo the change and restore the latest backup. |
| Connection test | A test account can connect using the address shown in the panel. | If version or connection errors occur, compare version, port, and allowances again. |
| Function test | The specifically changed function works without damaging existing world or game data. | If side effects occur, stop the server and restore the backed-up files. |
A successful single test is not a performance or availability guarantee. World size, mods, plugins, player count, network route, and simultaneous load can change the result. Document the version, change, and test result so you can trace later deviations.
FAQ
Can I close the browser while the server is being installed?
Yes. Provisioning continues server-side. You can return to the dashboard later and check the current status.
Why does installation take longer for some games?
Because the required files vary in size and are sometimes loaded from external sources. A Vanilla server is set up faster than a large modpack or an extensive game image.
Do I have to start immediately after ready?
No. You can first check settings, verify ports, set admins, or configure mods. This is especially useful for Minecraft, Valheim, Palworld, and CS2.
What do I do if DNS does not work?
First test the direct connection via IP and port. If that works, the server is running; the problem probably only affects the subdomain or SRV record. If it persists, contact support.
Will I get feedback when provisioning is complete?
Yes. You receive an email with the access details. A Discord notification is possible if you enabled it in the settings beforehand.