Knowledgebase

Published WWKNOW guidance for hosting, servers, infrastructure operations, and dependable digital services.

← Back to Knowledgebase

Server delivery and your first secure login

Start here after purchasing a server. Check the existing order and service record before submitting another order. Payment received, server provisioning and application readiness are different states.

1. Read the service handover

Sign in to the WWKNOW account used for the order and open the relevant service. Match the product, location and billing term to your confirmation. Use the service's assigned IP address, operating system and access details. Do not assume that a successful payment means an application is already installed.

Your order defines whether delivery includes an operating system, a preconfigured application or installation assistance. This guide does not remove any service included in your purchase. If an included application URL or credential is missing, report the service as incomplete rather than purchasing again.

2. Connect to Linux

From Windows Terminal, macOS Terminal or a Linux terminal, connect using the actual username and IP shown for your service:

Run each command separately:

ssh YOUR_USERNAME@YOUR_SERVER_IP

Replace both placeholders. Verify the host fingerprint using a trusted service handover or console before accepting it. Enter the password only in the local SSH prompt. If you use a key, keep its private part on your own device.

After login, these read-only commands help confirm the system:

Run each command separately:

hostname

cat /etc/os-release

df -h

free -h

Keep your first session open while testing any new SSH key or firewall rule from a second session. Do not disable your working authentication method before confirming the replacement.

3. Connect to Windows

Use Remote Desktop with the service's IP and supplied Windows account. Check the destination before entering credentials. A refused connection can mean the operating system is still starting, RDP is disabled or the network/firewall is blocking access; it does not by itself prove the password is wrong.

4. Continue with your application

A server account, control-panel account and application administrator are separate. Use the relevant guide only on the intended server:

If delivery is delayed, keep the existing order reference and check its status. Do not repeatedly pay or request reinstallation. For help, provide the service ID, time and exact redacted error; never include passwords or private keys.

Reference: Ubuntu OpenSSH documentation.

Technical guidance reviewed: 28 October 2026. Match instructions to your actual service and application version.

Was this article useful?

Enterprise Grade Components