A complete tour of the ServerNet client area

When you purchase your first hosting or server service, nearly all administrative tasks — from paying invoices and renewing services to submitting support requests and changing your domain's nameservers — are done from a single place: the Client Area. Many new users confuse the client area with the hosting control panel (such as cPanel or DirectAdmin), and this leads to confusion, unnecessary tickets, and even unintended service suspension. In this guide, we will go through the main sections of the ServerNet client area one by one so you know exactly where to perform each task.

What Is the Client Area and How Does It Differ from the Hosting Control Panel?

The client area is the management panel for your account with the hosting company; that is, everything related to your financial and administrative relationship with the provider is managed from here. In contrast, the hosting control panel is the tool for managing the service itself: creating email accounts, uploading files, creating MySQL databases, and the like.

A simple rule for telling them apart:

• If your task relates to "money, ownership, renewal, or support" → Client Area
• If your task relates to "files, databases, email, or technical site settings" → Hosting Control Panel

For example, to reset your cPanel password you should go to the client area (since service ownership is defined there), but to create the email info@yourdomain.com you need to log in to cPanel itself.

The Services Section: The Heart of the Client Area

In the "My Services" section, a list of all your active, suspended, and expired services is displayed. Clicking on any service opens its details page, which usually includes the following:

• Service status: Active, Suspended, or Cancelled
• Next due date: the most important number you need to keep an eye on
• Login details: control panel address, username, and the ability to change the password
• Direct login button (SSO): log in to the control panel without entering a password
• Request an upgrade or plan change

Service Suspended — What Should You Do?

If you see the word Suspended next to a service, in more than 90 percent of cases the cause is one of these two: an unpaid renewal invoice or an abuse report (such as spam being sent from a hacked site). In the first case, paying the invoice usually reactivates the service automatically within a few minutes. In the second case, be sure to follow up via a ticket and do not request unsuspension before fixing the security issue.

Invoices and Payments in the Client Area

The billing section usually consists of three parts:

1. Invoices: a list of paid and unpaid invoices with a unique invoice number. Mention this number in any billing-related ticket follow-up.
2. Account credit: you can top up your account so that future invoices are automatically deducted from your credit — a reliable way to prevent unwanted downtime.
3. Transaction history: the bank gateway reference number for each payment is recorded here.

A Common Mistake: Ignoring the Renewal Invoice Email

The renewal invoice is usually issued and emailed a few days before the due date. The most common scenario for losing a site is this: the invoice email goes to the Spam folder, the user doesn't notice, the service gets suspended and, after a set grace period, deleted. To prevent this:

• Add ServerNet's sending email address to your email whitelist.
• Register a valid mobile number in your profile so you also receive SMS notifications.
• If you have a critical service, choose an annual renewal cycle instead of monthly to reduce the number of risk occasions.

Support Tickets: How to Write a Ticket That Gets a Fast Reply

The ticketing system is the official, trackable channel for communicating with support, and unlike a phone call, all correspondence in it stays on record. The quality of your ticket directly affects the response speed. A good ticket has this structure:

• The right department: don't send a technical issue to the billing department; it only wastes time.
• A precise subject: instead of "My site has a problem," write "508 Resource Limit error on domain example.com since 2 PM."
• A step-by-step description: what you did, what you expected, and what you saw.
• The full error message: attach the exact error text or a screenshot. For example, the output of this command is very helpful for an SSH connection issue:

ssh -v user@your-server-ip
# Copy the last three or four lines of the output into the ticket

Important tip: open a separate ticket for each topic, and instead of creating a new ticket to follow up, reply on the same existing ticket. Opening multiple simultaneous tickets for one issue pushes you further back in the response queue, not forward.

Managing Domains in the Client Area

If you registered your domain there as well, the "Domains" section gives you the following capabilities:

• Viewing the domain's expiration date and renewing it (separate from hosting renewal!)
• Changing nameservers (NS)
• Enabling or disabling the Transfer Lock
• Obtaining the transfer code (EPP/Auth Code) for transferring the domain elsewhere
• Editing WHOIS contact information

Changing Nameservers and Verifying the Change Has Taken Effect

After purchasing hosting, you need to enter the nameservers you received in the service delivery email into your domain settings. Once saved, the changes do not take effect across the internet immediately; depending on the TLD and DNS caching, it usually takes between 1 and 24 hours (and in rare cases up to 48 hours). To check the status, in the terminal:

dig +short NS example.com
# Or query a public DNS directly to bypass the local cache:
dig @8.8.8.8 +short NS example.com

If the output still shows the old nameservers, be patient; submitting a ticket within the first hour will not change the DNS propagation process.

A common mistake: many users purchase their domain and hosting at the same time and assume that renewing the hosting also renews the domain. These are two separate services with two separate invoices. Domain expiration means the site and email become completely inaccessible, even if the hosting is active.

Profile and Account Security

The profile section is where the identity of the service owner is defined; so accuracy here is critical:

• Genuine identity information: during account recovery or an ownership dispute, the only means of proof is matching this information. An account with fake information is effectively unrecoverable.
• A valid primary email: all critical notifications (invoices, expirations, security alerts) go to this address. Do not use an email on the same domain you are hosting; if the service goes down, you won't receive the alert emails either.
• Sub-accounts: if you work with a developer or colleague, instead of giving them the main password, create a sub-account for them with limited access (for example, technical tickets only).

Enabling Two-Factor Authentication (2FA)

Anyone who gains access to your client area effectively becomes the owner of all your services and domains; they can change the control panel password or transfer the domain. Therefore:

1. In the profile security section, enable the Two-Factor Authentication option.
2. Scan the QR code with an app like Google Authenticator.
3. Keep the Backup Codes somewhere safe and offline — not in the same email account you use to log in.

Also choose a unique password of at least 16 characters for the account and do not reuse it on any other service.

Conclusion

The client area is the command center of your relationship with the hosting company: you monitor your services from there, pay invoices, manage domains, and stay in touch with support via tickets. If you take three simple habits seriously — enabling 2FA, registering a valid email and mobile number, and paying renewal invoices on time — you will be safe from most of the common problems that catch users off guard. If you don't have an account yet, after signing up with ServerNet, go through these sections step by step so that when the time comes, you know exactly where to perform each task.