The Virtual Domain Setup
Put a live domain on a web server you already run, pointed at your folders or apps (up to five paths), with its own logs and redirects, your SSL certificate installed, and PHP wired up where your site needs it. Priced per domain: book one, or as many as you need.
You've got the server running; now you need your sites live on it. We point each domain at the right place, a folder for your static pages or the port of an app you already run, and make it a working site. You don't edit config by hand or reload production with your fingers crossed.
Each domain gets its own access and error logs, www and HTTPS redirects, a raised upload limit, and up to five paths pointed at folders, app ports or both. If your site runs on PHP, like WordPress or Laravel, we wire it to the PHP already on your server. Got an SSL certificate for the domain? We install it and switch you to HTTPS; we don't issue or renew certificates, so renewals stay in your hands.
You pay per domain and add as many as you need: one today, three more next month. Each domain runs on its own delivery clock and comes back checked and confirmed working.
What's included
Each domain set up as a working site, pointed at the right folders and apps, with its own logs and a sensible upload limit
Up to five paths per domain, so one site can serve static pages and a live app side by side
PHP sites like WordPress and Laravel wired to the runtime already on your server, and skipped if your site doesn't use PHP
www, HTTPS and pretty-URL redirects handled, so your links resolve the way visitors and search engines expect
Your SSL certificate installed and the site switched to HTTPS, while issuing and renewing stay with you
Optional on request: password-protect a path, force HTTPS with HSTS, or drop in your own error pages
Every domain checked and confirmed working before it's handed back
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
SSH access with sudo or root to a server already running Caddy, Nginx or Apache
For each domain: its name, whether visitors land on the bare domain or www, and up to five paths, each pointing at a folder or at the local port of an app that is already running
The SSL certificate and private key for each domain you want on HTTPS, uploaded or already on the server
Your own error pages, or the path and login to protect, if you choose those options
How it works
Book it — pay the fixed price and tell us the target environment. No scoping call first.
We deliver — an experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in the portal.
Hand-off — you get the deliverables, the documentation, a rollback snapshot, and a walkthrough if you want one.
Who does it
A salaried Support Resort specialist with more than ten years in the field, working from a runbook we've been refining since 2003 — supervised by senior management, never a marketplace contractor. You'll see who is assigned and can message them about this task directly in your portal.
FAQ
Ask about this task
Our assistant knows the scope document and runbook behind this service. Ask what's covered, what isn't, or whether it's the right task for your situation.
Answers come from our published scope documents. Prefer a person? Switch to the "Email us" tab — a senior manager replies personally, usually the same weekday.
Related services
The Web Server Install
We turn a fresh Linux server into a secured, fast web server — Caddy, Nginx, or Apache — closed off to the exposures attackers scan for and sized to handle real traffic, ready for the sites you put on it next.
The Reverse Proxy Setup
A hardened front door for up to three applications you already run — HTTPS ends at the proxy, scanner probes are turned away, and traffic is balanced across your backends while the apps behind it stay exactly as they are.
The Web Server Migration
Up to five sites moved to a new server with their configuration and databases, proven working there before a single visitor is sent across — and the old server left untouched, so going back is one DNS change.