How to host your own website on your own server
Plan a self-hosted website: choose a server, configure DNS and networking, verify HTTPS and prepare backups before going live.
Choose a small first project
A static website is a useful first self-hosting project because it has no application database to maintain. Start with a test page on a dedicated machine or VM, confirm it works locally, then make it publicly reachable only when you are ready.
Owning the server gives you control of files and software. It also makes you responsible for availability, updates, network exposure and recovery. A hosted VM is still self-hosting when you operate the server yourself; you do not need to own physical hardware.
- A server that can stay powered on, with enough storage for the site and logs.
- A maintained operating system and web server compatible with your application.
- Local or SSH recovery access and a backup destination separate from the host.
- A reachable network address if the site needs to be public.
From a local page to a public website
Work through the layers in order. This makes it easier to distinguish an application problem from a DNS or network problem.
Prepare the host
Back up existing data, install or use a supported server environment and keep a recovery route. With Dexlinkx, approved beta users add the server and follow Dexlinkx Manager before checking status in the portal.
Publish a test page
Create a static site through an available hosting workflow and check it at the configured address. Confirm the right content appears before connecting your production domain.
Connect DNS
Point the domain's A record to the public IPv4 address, or use an AAAA record only when the server is reachable over IPv6. Check existing records and avoid leaving an unreachable IPv6 target in place.
Check the network path
For a home server, review router forwarding, firewall rules and your provider's address arrangement. Carrier-grade NAT can prevent inbound connections even when local port forwarding is configured.
Verify HTTPS
Follow the site's available certificate workflow. Check that the certificate matches the domain and that the HTTPS page loads from an external connection before directing visitors to it.
Test recovery
Store copies of the site and any database outside the server. Restore to a test location and verify the result, then document how to recover if the host fails.
Diagnose common hosting problems
Test from a second connection, such as a mobile network, as well as your local network. A working local page does not prove that public visitors can reach it.
- Domain does not resolve: check its authoritative DNS records and recently changed addresses.
- Domain points to the server but times out: inspect inbound routing and firewall rules before changing website files.
- Wrong site appears: check the site's configured hostname and the web server's routing.
- HTTPS warning: check the requested hostname, certificate names and certificate validity.
- Dynamic site fails: check its application logs, database connection and runtime requirements.
Where Dexlinkx helps
Dexlinkx provides guided server installation and portal workflows for supported websites, domains, databases and server status. The available actions depend on beta access and the server's access profile.
Start with the public getting started guide, then use the signed-in beta documentation for exact installation details. Application files and databases stay on your server; maintain your own tested backup plan.
Realistic expectations
- A home server's uptime depends on your power, connection and equipment.
- Dexlinkx beta support must be checked for the selected host and application; it does not replace site maintenance.
Apply for the closed beta
Apply for access and install your first server with Dexlinkx Manager once approved.