Getting startedGhostVPS editorial

How to use your free 30-minute VPS trial: order, deploy and connect

Follow the real GhostVPS Console flow after ordering: find Free Test VPS, deploy a Linux server, set a password, connect over SSH and use the time left for one useful test.

The most important thing to know about the GhostVPS free trial is that the free order and the server are two separate steps. Ordering Free Test VPS activates the service, but leaves its instance list empty. The 30-minute countdown begins when the service activates, before you click Deploy New VPS. Prepare your test first, then deploy promptly.

Before you order: prepare one useful test

Create or sign in to your Console account and verify your email. Have an SSH client, a small disposable test file and a place for notes ready. Choose one question you can answer quickly: Can you reach a location from your network? Can a small Linux application start with the available memory? Do the service controls meet your needs? Never upload production secrets or the only copy of a file.

The free trial is Linux only. An eligible account can make up to three test deployments, with one instance active at a time; Console shows the remaining count. The service timer is 30 minutes from activation, not a new 30-minute period after every deployment. Review the current free-trial guide before checkout.

After the $0 order: open your test service

In Services → My Services, open the row called Free Test VPS. Seeing an Active service with no VPS yet is normal: the order has activated the service, but has not deployed an instance. Scroll to Cloud Compute Instances and click Deploy New VPS. Do this immediately; the countdown is running.

Real Console My Services table showing the active Free Test VPS service, with private identifiers hidden
The Free Test VPS row in My Services. Other products and private identifiers were removed from this real screenshot.

Deploy your Linux VPS

In the current form, select Discovery, then D2-2, an available region, a Linux image and a hostname. The form unlocks each later choice after the earlier choice is made. Click Deploy Server Instance once and wait. Available regions and images may change, so follow the choices in your account.

Real Free Test VPS deployment form showing plan, region, Linux image, hostname and deployment button
The deployment form is inside the active service. Completing the $0 order alone does not create a server.

Stay in the Free Test VPS service. You do not need to add cloud credit to begin this free test. The checkout used for this walkthrough showed $0 due; if you see a charge, check the cart before placing an order.

Wait for Running and find your connection details

The instance appears in Cloud Compute Instances. Use Refresh Status if needed and wait for Running. Copy its Primary IP. In the Actions column, click the gear icon labelled Manage, then open Overview. This panel shows the IPv4 address and username. If the Password row says Set Password, set a password there before connecting. Keep it private.

Actual Cloud Compute Instances table with Running status, Primary IP and Manage action; IP replaced with an example address
Wait for Running. The IP in this screenshot is a documentation example, not an address to connect to.
Actual Manage Instance Overview showing IPv4, username and Set Password control with private addresses replaced
Manage → Overview shows the connection fields. Private addresses and instance identifiers were replaced with examples.

From your computer, replace the placeholders with the values shown in your Overview panel:

ssh USER@SERVER_IP

The username depends on the selected Linux image. In our Debian 12 example it was debian; do not assume root for every image. Investigate a warning about a changed SSH host key before accepting it. If SSH fails, check that the status is Running, that you copied the correct IP and username, and that you set a password if the panel required one. Our practical tutorials cover connection basics in more detail.

Use the remaining time for one real question

After connecting, confirm the environment with a few quick commands. They show the available resources; they are not performance benchmarks:

uname -s
nproc
free -h
df -h /

For a network question, test from the network your users will use. A short ping sample from a Linux or macOS client can show round-trip delay:

ping -c 5 SERVER_IP

ICMP may be blocked, so a failed ping alone does not prove the VPS is unreachable. Confirm SSH or a small HTTP endpoint as well. Compare locations using the same client network and method; record the range, not only the best result. The locations page helps shortlist regions, but its markers are not latency measurements.

For an application question, run one small disposable task resembling your real workload. Observe memory with free -h and CPU activity with top if available. Record the task, its duration and any errors. Avoid sustained load and broad network scans on a temporary shared server.

Before the countdown ends: save and decide

Save notes and any test files outside the server. The instance is deleted automatically when the timer ends. It is not a backup or evidence of long-term uptime, support response time or every paid plan’s performance.

Record Your observation
Region and Linux image Exact choices shown in Console
Connection SSH worked, failed, or needed investigation
Resources CPU count, available memory and free disk
One test task What ran, how long it took and any error
Decision Suitable, unsuitable or inconclusive for the question you set

If the result is inconclusive and your account has a deployment left, change one important variable on the next test. Compare the exact paid configuration in the Cloud VPS catalog or server finder. The free test uses a specific Linux plan; paid plans can differ in CPU, storage, network and software options.

Back to journalExplore servers