What credentials do you receive after provisioning?
When you provision a dedicated server, there are several critical credentials and access information you’ll receive to manage the server, install software, configure services, and ensure security. These credentials are essential for both system administration and day-to-day use of the server.
Here’s a rundown of the typical credentials provided after server provisioning and what they are used for:
What You Get: A root user account, which is the highest level of administrative privilege on Linux-based servers.
Purpose: The root account allows you to perform all administrative tasks, including installing software, configuring system settings, managing user accounts, and monitoring system health.
Common Information:
Username: root
Password: A unique password provided by the hosting provider or generated during provisioning.
SSH Key (Optional): Many providers allow you to use an SSH key for secure login, which is often recommended over using a password for security reasons.
What You Get: An administrator account on Windows-based servers, which provides full control over the server's configuration and security.
Purpose: Similar to root on Linux, the Administrator account on Windows gives you unrestricted access to system settings, service management, and user administration.
Common Information:
Username: Typically Administrator (or custom if set during provisioning).
Password: A password provided by your hosting provider or set during the provisioning process.
Remote Desktop (RDP) Access: On Windows servers, you’ll often use Remote Desktop Protocol (RDP) to access the server remotely, and this credential will include the IP address, username, and password to access the desktop environment.
For Linux-based dedicated servers, SSH (Secure Shell) access is a standard way of managing and interacting with your server remotely. After provisioning, the following credentials are typically provided:
IP Address: The server’s public IP address that you'll use to connect to the server.
SSH Username: The root username (or another user account) used to connect.
SSH Password or SSH Key: Depending on your security setup, either:
Password-based authentication (less secure).
SSH Key: A more secure method using a private/public key pair to authenticate without needing to use a password.
Port Number: Typically, SSH runs on port 22, but it may be customized by your provider for security purposes.
Example Command for SSH Login:
For added security, many providers encourage or require SSH key authentication rather than password-based login.
Many hosting providers offer a web-based control panel (like cPanel, Plesk, or their custom dashboards) to simplify server management tasks. If this is the case, the following credentials will be provided:
Control Panel URL: The web address used to access the control panel (e.g., http://your-server-ip:2083 for cPanel).
Username: A user account (often the same as the root user or a custom account) with administrative rights to manage the server’s software, databases, and websites.
Password: A password provided by your hosting provider or set during provisioning.
cPanel: For managing websites, domains, email accounts, file backups, and more.
Plesk: A similar control panel that offers tools for managing WordPress, databases, DNS settings, and more.
Custom Dashboards: Some hosts have proprietary control panels designed to handle specific configurations, often simplifying advanced server tasks.
If your dedicated server is pre-configured with databases (such as MySQL, PostgreSQL, or SQL Server), you will typically be provided with the following credentials:
Database Host/IP Address: This will usually be the same as the server's IP address unless you’re using remote databases or cloud-based solutions.
Database Username: A specific user account for accessing the database.
Database Password: The password for the database account.
Depending on your configuration, your hosting provider may also provide pre-configured databases and users for applications like WordPress or Joomla.
If you're managing websites, files, or other assets, you'll likely need FTP or SFTP credentials to upload and manage files remotely.
FTP/SFTP Username: A user account with appropriate access to file directories.
FTP/SFTP Password: The password associated with the username.
Server/Host: The IP address or hostname of your server, along with the specific FTP port (usually 21 for FTP or 22 for SFTP).
Example FTP Command (using SFTP for secure file transfer):
If you're using a control panel like cPanel, FTP accounts can be created through the interface and have their own access permissions.
If your server is being used to host websites, email, or other services, you will also receive DNS configuration details to link your domain to the server:
IP Address: The server’s public IP address used for DNS record configuration.
Nameservers: If applicable, your hosting provider may assign nameservers that you can use for domain registration or DNS management.
Subdomains: Any pre-configured subdomains or additional domains linked to your server.
You'll use these details to configure your domain’s A records, MX records, and other DNS settings to point to the server.
Email Server Credentials: If your server will be used for email hosting, you may receive credentials to configure SMTP, IMAP, and POP3 email services.
Firewall/Security Configuration: Some providers may send specific firewall rules or security keys for configuring server firewalls and intrusion detection systems.
Backup Access: If your provider offers automatic backups, you may be given access credentials or URLs to manage backup options and restore data.
Cloud Integration Details: If you are using the server in combination with a cloud hosting provider (e.g., AWS, Google Cloud), you may receive API credentials or integration keys for managing resources.
Once your dedicated server is provisioned, it’s critical to keep your credentials secure. Here are a few best practices to consider:
Secure Your Credentials: Use strong, unique passwords for all accounts. For root or administrator access, consider using SSH keys for secure login instead of passwords.
Access Control: Set up and manage user accounts with the principle of least privilege, meaning give each user only the access they need to perform their tasks.
Regular Updates: Regularly update your server software and control panel to avoid security vulnerabilities.
Two-Factor Authentication (2FA): Where possible, enable 2FA for your control panel and other access points for an extra layer of security.
By managing and securing these credentials properly, you’ll ensure that your server is both functional and safe from unauthorized access.