RemarkableCloud

Managing Your Server: Start, Stop, Console, Snapshots & Backups

How to manage your RemarkableCloud VPS from the client area: start, stop, and reboot, access the console, take snapshots, restore from backup, reinstall the OS, and monitor resources.

Every RemarkableCloud Cloud Cube comes with a self-service server management interface. You can start, stop, and reboot your server, access the VNC console, take and restore snapshots, and request backups: all without opening a support ticket.

Accessing server management

  • Log into your client area at manager.remarkablecloud.com.
  • Go to Services → My Services and click your Cloud Cube.
  • In the Quick Links section, click Server Management.
    •

    This opens your server’s management dashboard where all the controls below are available.

    Start, stop, and reboot

    Stop performs a graceful shutdown: the OS shuts down cleanly before the VM is powered off. Reboot restarts the OS. Use Force Stop only if the server is completely unresponsive: it's the equivalent of pulling the power cable and can cause filesystem issues.

    Reboot your server

    From the server management dashboard:

    1. Click Reboot
    2. Confirm the action in the dialog
    3. The server shuts down and starts back up: typically takes 30-60 seconds
    4. The status indicator turns green when the server is back online

    Stop your server

    1. Click Stop
    2. Confirm the action
    3. The OS performs a graceful shutdown
    4. Your server stops billing for compute while powered off: storage billing continues

    Start your server

    If your server is stopped:

    1. Click Start
    2. The server boots: typically takes 20-40 seconds
    3. The status indicator turns green when ready

    Force stop (last resort)

    If the server is completely unresponsive and a normal stop doesn’t work:

    1. Click Force Stop
    2. Confirm: this immediately kills the VM without a clean shutdown
    3. Run a filesystem check after restart by booting into rescue mode if needed

    Console access (VNC)

    The console gives you direct keyboard access to your server: useful when SSH is not reachable (misconfigured firewall, broken network config, forgot SSH port).

  • From the server management dashboard, click Console.
  • A browser-based VNC window opens showing your server's terminal directly.
  • Log in with your root credentials.
  • Use the console to fix network issues, reset passwords, or troubleshoot boot problems.
    •  SSH is faster and more comfortable for regular work. Use the console only when SSH is unavailable: the VNC connection is slower and doesn't support copy/paste as smoothly as a terminal.

    Snapshots

    A snapshot captures the exact state of your server’s disk at a point in time. You can restore to that state at any time: useful before making risky changes like major software upgrades or config changes.

    Snapshots are point-in-time disk images stored on the same infrastructure: fast to take and restore, but not a substitute for off-site backups. Backups are copies sent to remote storage (S3) that protect against infrastructure failure. Use both.

    Taking a snapshot

  • From the server management dashboard, go to Snapshots.
  • Click Take Snapshot.
  • Add a label (e.g. before-php-upgrade) so you can identify it later.
  • Click Confirm. The snapshot is created in the background: the server keeps running normally. Large servers may take a few minutes.
    •

    Restoring a snapshot

    Restoring a snapshot replaces your server's current disk with the snapshot. Any changes made after the snapshot was taken will be lost. Take a new snapshot of the current state first if you want to keep it.
  • Go to Snapshots and find the snapshot you want to restore.
  • Click Restore.
  • Confirm the action: the server will reboot into the snapshot state.
  • Wait for the status indicator to turn green: typically 1-3 minutes.
    •

    Deleting old snapshots

    Snapshots consume disk space. Delete snapshots you no longer need:

    1. Go to Snapshots → find the snapshot
    2. Click Delete → confirm

    Keep snapshots you took before major changes until you’re confident the change was successful, then delete them.

    Backups

    Your Cloud Cube includes automated daily backups to remote S3 storage. You can also request manual backups and restore from the management interface.

    Requesting a manual backup

  • Go to Backups in the server management dashboard.
  • Click Create Backup.
  • The backup runs in the background and is stored in your S3 allocation.
  • You'll receive an email when the backup completes.
    •

    Restoring from a backup

  • Go to Backups and find the backup date you want to restore from.
  • Click Restore.
  • Choose what to restore: full server, or specific files/databases if granular restore is available.
  • Confirm. The restore process runs in the background: you'll receive an email when complete.
    •  For restoring individual files, databases, or email accounts without a full server restore, log into cPanel or DirectAdmin and use JetBackup: it gives you file-level and database-level restore without affecting the rest of the server. See the JetBackup guide.

    Reinstalling the OS

    If you want to start fresh with a clean operating system:

    Reinstalling the OS completely destroys all data on the server: websites, databases, files, email, everything. Take a backup before proceeding if there is anything you want to keep.
  • Go to Reinstall in the server management dashboard.
  • Select the operating system and version from the dropdown.
  • Select your control panel (cPanel, DirectAdmin, RemarkablePanel, none).
  • Confirm you understand all data will be erased.
  • Click Reinstall. The process takes 5-15 minutes.
  • New credentials are emailed to you when provisioning is complete.
    •

    Resource monitoring

    The Resources tab in the server management dashboard shows:

    MetricWhat it shows
    CPU usagePercentage of allocated CPU used over time
    RAM usageCurrent memory consumption and peak
    Disk I/ORead/write operations per second
    NetworkInbound and outbound bandwidth
    Bandwidth usageMonthly transfer used vs your plan allowance

    Use this to identify resource bottlenecks before they become problems. If CPU is consistently at 80%+, it’s time to consider upgrading to a Dedicated CPU plan.

    Reverse DNS (rDNS)

    Reverse DNS maps your server’s IP address back to a hostname. This is important for mail server reputation: many mail providers reject or spam-filter mail from IPs without a valid rDNS record.

    To set your rDNS:

    1. Go to Network → Reverse DNS
    2. Enter the fully qualified hostname you want the IP to resolve to (e.g. mail.yourdomain.com)
    3. Click Save
    The hostname you set for rDNS should resolve back to the same IP in your forward DNS. For example: `mail.yourdomain.com` → `YOUR_IP` and `YOUR_IP` → `mail.yourdomain.com`. This is called a forward-confirmed reverse DNS (FCrDNS) and is required by some mail servers.

    Upgrading or resizing your plan

    If your current plan is running out of resources:

    1. Go back to the client area → Services → My Services → open your Cloud Cube
    2. Click Actions → Upgrade/Downgrade
    3. Select the new plan
    4. Review the prorated cost and click Upgrade

    The upgrade is applied at the next billing cycle. Disk and RAM are expanded: no reinstall needed.

    Next steps
    Still stuck? Ask a human, we answer in minutes.