After ordering an ArkHost Linux VPS, check its service status in the Client Area. We will notify you when it is ready. Provisioning time can vary; there is no guaranteed number of minutes.
Find the connection details
- Open Services > My Services and select the VPS.
- Use the IP address and username shown in its connection details. Do not substitute an address from an old email or another service.
- Use the Password control to request the password when needed.
- Connect with your SSH client. Verify the server fingerprint before accepting a new host key.
The browser console is also available from the VPS details page. Confirm you can use it before changing SSH or firewall settings.
If you cannot connect by SSH
- Check the VPS service status and current connection details first. Use the configured SSH port and username; a timeout is different from a rejected password. Keep any working session open.
- Timeout: check the address, port and your local network. If appropriate, try another trusted network once. A timeout alone does not prove the VPS is down.
- Connection refused: the destination may be reachable but SSH may not be listening on that port, or a firewall may reject it. Check the configured port rather than repeatedly resetting the password.
- Permission denied: confirm the username and selected SSH key or supported password method. Repeated guesses can trigger access restrictions. Never send a private key to support.
- Host-key warning: stop and verify the server fingerprint through a trusted route. Do not remove the saved key merely to silence the warning, even if you recently reinstalled.
If network access still fails, try the browser console from this VPS's details page. If you can log in, inspect the SSH service, configuration and recent firewall changes before changing anything. Follow the SSH hardening guide for syntax validation and separate-session testing. Do not reset all firewall rules.
If the console will not open or you cannot safely identify the cause, stop and contact support with the service, timestamp, exact error and whether the console opens and accepts login. Reinstall and restore overwrite data; neither is a first troubleshooting step.
Before deploying your application
- Install operating-system updates.
- Create a named administrator account and test SSH key login in a separate session.
- Allow the correct SSH port before enabling or restricting the firewall.
- Install only the software your application needs.
- Monitor disk space, memory and application health.
- Keep an independent off-server backup of important files and databases.
Reinstalling the operating system
You choose an operating system during ordering. To start again later, open Actions > Reinstall in the Client Area and choose an available operating system.
Reinstalling erases the current disk data. Save anything you need elsewhere and check your backup before confirming. Follow the operation status rather than assuming that a running VPS means installation has finished. Refresh the service details afterwards and request the current password when needed.
Backups and restore
The current VPS range includes 7 backup slots. The Client Area shows available backups and schedules. You can restore an available backup to the same VPS; restoring overwrites its current disk contents.
The Client Area does not provide manual backup creation, deletion or schedule editing. Check which backups actually exist before relying on one for recovery. Keep a separate copy of important data.
If you need help or more resources
Contact support for VPS service or access problems. Include the service name and the error, but do not paste passwords or private keys into ordinary messages. You remain responsible for the software you install and its maintenance.
Resource changes are arranged through support. There is no self-service package upgrade.
View the current Linux VPS plans. Older services may have different controls and terms.
