Getting Started with Your Nexelya VPS

Nexelya is VPS and dedicated hosting. When you order a KVM virtual machine, it is provisioned on our multi-node Proxmox cluster with full access through the Nexelya client panel—power controls, browser KVM, ISO reimage, and usage visibility.

This guide walks you through the first hour after provisioning: confirming access, securing the instance, and orienting yourself to the dashboard so you can deploy applications with confidence.

After checkout, open your Nexelya dashboard and select the new VPS service. Note the primary IPv4 address, hostname, and any root or cloud-init credentials shown on the service detail page. If you uploaded an SSH public key at registration, key-based login should work immediately on port 22.

Test connectivity with ssh root@YOUR_IP from a trusted workstation. If password authentication was issued for first boot, change it before exposing any services to the public internet.

• Verify the VM status shows running in the panel before attempting SSH.
• Use ssh -v for verbose output if the connection times out—often a local firewall or wrong IP.
• Pin the host key on first successful login to detect future MITM attempts.

The Nexelya VPS panel mirrors what you would expect from enterprise Proxmox operations, simplified for self-service. Start, graceful shutdown, hard stop, and reboot are available without opening a support ticket. When an OS install fails or you need recovery access, launch the noVNC KVM console from the same page—useful when SSH is not yet configured or networking is misconfigured.

Approved ISOs can be attached for reimage workflows. Treat reimage as destructive: snapshot or back up data first unless you are performing a clean install intentionally.

Before hosting production traffic, apply baseline hardening. Update packages (apt update && apt upgrade on Debian/Ubuntu, dnf upgrade on RHEL derivatives), create a non-root sudo user, disable root SSH login, and configure UFW or firewalld to allow only required ports.

Nexelya is. Enable automatic security updates where your workload permits.

• Restrict SSH to key-only authentication.
• Set up fail2ban or equivalent brute-force protection.
• Configure timezone and NTP (chrony or systemd-timesyncd).
• Document which ports each service uses before enabling the firewall.

Continue with our VPS security hardening guide for defense in depth, the backups guide before running databases in production, and the KVM console guide if you need out-of-band access during OS setup. For capacity changes, see scaling CPU, RAM, and disk.

Provisioning time depends on image availability and cluster load; most Linux VPS instances are reachable within minutes. If your service stays in a pending state beyond an hour, check billing status in the dashboard before contacting support.

You can run multiple VPS instances under one Nexelya account. Each service is billed independently according to its plan. Organizations often pair a small staging VPS with a larger production instance—both managed from the same panel backed by Nexelya operations practices.

Nexelya does not replace your application monitoring stack. Install agents such as Prometheus node_exporter, Datadog, or Uptime Kuma on the guest and alert on sustained resource saturation rather than waiting for customer-visible outages.

• Can I change hostname after provisioning? Yes, set it inside the guest and update DNS separately.
• Is IPv6 included? Availability varies by plan; check your service detail page.
• Do you offer Windows VPS? Select plans support Windows—verify ISO availability before ordering.