Finding your service credentials

You've purchased a hosting service or a VPS, the payment went through, and now you're stuck on a simple but frustrating question: where are the access details? What's the username, where did they send the password, which one is the server IP, and what's the control panel login URL anyway? This article walks you through exactly that path, step by step: from the welcome email to the client area, plus the commands you can use to verify your credentials yourself before contacting support.

What Exactly Do Service Access Details Include?

Before you start searching, know what you're looking for. Depending on the type of service, you'll need the following:

• Shared hosting: the control panel username (cPanel or DirectAdmin), the password, the panel login URL, and the server IP.
• Virtual private server (VPS): the server IP, the root username (on Linux) or Administrator (on Windows), the password, and the SSH or RDP port.
• Additional items: the nameserver addresses for connecting your domain, and sometimes FTP or database credentials, which you usually create yourself later in the control panel.

An important note: your client area username at the hosting company is different from your hosting control panel username. The former is the email address you registered with; the latter is the technical username for the service (for example, examplus), which the system generates automatically. Many support tickets begin with a mix-up between these two.

Step One: Find the Welcome Email

Almost all hosting companies, including ServerNet, send an email containing your access details immediately after your service is activated. This email usually has a subject line like "Your Hosting Service Details" or "New Account Information" and includes the following:

• The control panel username and password
• The control panel login URL (both via domain and via IP)
• The server's dedicated or shared IP address
• The nameservers, for example ns1.example-host.com and ns2.example-host.com

If you can't find the email, check these three places in order:

1. The Spam/Junk folder — emails containing passwords regularly get flagged as spam.
2. The Promotions or Updates tab in Gmail.
3. Search your inbox for phrases like "account information" or the hosting company's name.

If there's still nothing, you probably entered your email address incorrectly during registration, or the service is still in "pending activation" status. Both can be checked from inside the client area.

Step Two: Access Details in the Client Area

Even if you've lost the email, everything is available in the hosting company's client area. The general path in most client areas (which are usually based on WHMCS) is as follows:

1. Log in to the client area (with the email and password you created during registration).
2. Go to the "My Services" or Services section.
3. Click on the service in question to open its details page.

For Shared Hosting

On the service details page, you'll usually see the following:

• Username: the control panel username.
• Direct login button: an option like "Login to cPanel" that logs you into the control panel without entering a password. This is the fastest way to get started.
• Server IP and nameservers: usually in the sidebar or in a "Server Information" tab.

For security reasons, the control panel password is often not displayed in plain text, but there is almost always a "Change Password" option on the same page. If you don't have the password, set a new one right there — it's faster than submitting a ticket.

For a Virtual Private Server

For VPS services, the server IP is usually shown on the details page, and the root password was either sent in the initial email or can be reset via the "Reinstall OS" or "Reset Password" option. Note that reinstalling wipes all data on the server; if you have data on the server, use only the password reset option or coordinate with support first.

Control Panel Login URL: Know Your Ports

This is one of the most common sources of confusion. Control panels run on specific ports, and their login URLs are different from your website's address:

• cPanel: https://yourdomain.com:2083 or https://IP:2083
• DirectAdmin: https://yourdomain.com:2222
• Webmail (cPanel): https://yourdomain.com:2096
• Plesk: https://yourdomain.com:8443

If your domain was recently registered or you've just changed the nameservers, DNS may not have propagated yet (full propagation can sometimes take up to 24 hours). In that case, use the IP address instead of the domain:

https://185.xx.xx.xx:2083

In this case, the browser will show an SSL certificate warning, because the certificate was issued for the domain, not the IP. This warning is normal in this specific scenario, and you can proceed via the "Advanced" option.

Step Three: Test the Connection Yourself

Before concluding that "the access details are wrong," check the situation with a few simple commands.

Checking Whether the Server Is Reachable

ping 185.xx.xx.xx

If you get a response, the server is up and reachable. That said, some servers block ping, so not getting a response doesn't necessarily mean the server is down.

Checking That the Domain Points to the Correct IP

nslookup yourdomain.com

Compare the returned IP with the IP shown in your client area. If they differ, DNS hasn't propagated yet, or the nameservers are configured incorrectly.

Connecting to a VPS via SSH

ssh root@185.xx.xx.xx
# If SSH is not on the default port:
ssh -p 2222 root@185.xx.xx.xx

On the first connection, a "fingerprint" confirmation message is displayed; type yes. If you get a Connection refused error, the port is probably wrong; if you see Permission denied, there's a problem with the username or password.

Common Mistakes When Using Access Details

• Extra whitespace when copying the password: the most common problem. When you copy the password from the email, a space at the beginning or end often gets copied along with it. Paste the password into a plain text editor first, check it, then use it.
• Logging in with the wrong username: the registration email is for the client area; the technical username (like examplus) is for cPanel or DirectAdmin. Don't mix them up.
• Persian keyboard layout or Caps Lock: in the SSH or control panel login form, the password is not displayed, and you may not notice you're typing Persian characters. Check your keyboard language.
• IP lockout after several failed attempts: most servers, using tools like CSF or Fail2ban, temporarily block your IP after 5 to 10 failed attempts. If the login page suddenly won't load at all (not even showing a wrong-password error), you've probably been blocked. Try a different internet connection (for example, mobile data) and, if needed, ask support to remove your IP from the block list.
• Control panel ports blocked on corporate networks: some office networks block ports like 2083 and 2222. If it works from home but not from the office, the problem is your network, not the service.

After Your First Login: Three Essential Security Tasks

1. Change the password. Don't treat the password sent by email as your permanent password. Create a mixed password of at least 16 characters and store it in a password manager (like Bitwarden or KeePass) — not in a text file on your desktop.
2. Archive the welcome email securely. Note the IP and nameservers somewhere, but after changing the password, the old password in the email no longer matters.
3. On a VPS, restrict root login with a password. At the earliest opportunity, create an SSH key and disable password login so that brute-force attacks become ineffective.

To sum up: your service access details live in two places — the welcome email and the service details page in the client area. If you don't have the password, resetting it from inside the client area is the fastest route; and before submitting a ticket, use ping and nslookup to make sure the problem is with the credentials and not with DNS or your own network. With these few simple steps, most login problems can be solved in under ten minutes.