OPS HubOPS Academy · free for everyone Sign in

Cloud servers & website migration

Set up customers' OPS Cloud servers and move their websites onto them.

Overview

An OPS Cloud server (VM) runs on OPS Data hardware and has its own public IP and firewall. To host a website on it: the VM must be running, ports 80/443 open, the site hosted on the VM's IP, and the domain pointing at that IP. 'Move to another server' in the site editor moves a site and updates the DNS for you.

Jobs this covers

web_cloud_setup, web_cloud_migrate — certificate: Cloud operations (recommended)

The equipment — what everything does

Cloud console

Create, start/stop, resize, firewall, snapshots, console log.

In game: Browser → opscloud.sa → Console.

Move to another server

Moves a site between OPS Web hosting, a cloud server and the customer's own line.

In game: opsweb.sa → the site → Move to another server…

Tools & PPE

Engineer laptop & console cable

Configures routers, NVRs and servers, runs speed tests and opens OPS Hub.

Standalone servers: tools are in your van (OPS Work → My van & tools). Items servers: collect them — and the job’s parts — at an OPS depot.

Step by step

1
Check the customer's server

opscloud.sa → Console. Your job's customer appears under the job reference. It should be Running.

Engineer laptop & console cable Browser → opscloud.sa type
2
Open the firewall

Open ports 80 and 443.

Engineer laptop & console cable VM → Firewall → Edit type
3
Put the site on it

opsweb.sa → the site → Move to another server → the VM's IP (or create the site on that IP).

Engineer laptop & console cable opsweb.sa type
4
Publish & test

Make sure the site is Live and visit the domain.

Engineer laptop & console cable Browser inspect
5
Check

Press Check on the job.

OPS Work → the job phone

Health & safety

Customer data & privacy

Risk: Router settings, passwords and camera footage are private.

Control: Only change what the job needs. Never share Wi-Fi passwords or footage, and log out of customer systems when you finish.

Downtime

Risk: Moving a site at the wrong moment takes it offline.

Control: Snapshot first, and move when the VM is running.

In game you confirm these in a risk assessment before starting. Skipping them on risky work can cause a fall or a shock — and it’s logged as a safety incident.

When it’s not done correctly

Ports 80/443 closed

Visitors get 'connection refused' and the check fails.

VM stopped or host down

The site times out.

Domain still pointing at OPS Web

Visitors keep seeing the old copy and the check fails.