Get started with your own server and Dexlinkx

Before you install

This guide is public: you can use it to plan your setup before receiving beta access. Installation downloads and detailed beta instructions remain in the documentation for approved, signed-in users.

Choose a dedicated physical machine, a virtual machine or an existing compatible Linux server. Check the current installer instructions for supported operating systems and architecture before changing the host. A Raspberry Pi is a possible self-hosting device, but that alone does not establish Dexlinkx compatibility.

• Back up existing files and verify that you can restore them before installing or changing partitions.
• Keep local console or SSH access available so you can recover the host independently of the portal.
• Decide whether the first site will be local, private or publicly reachable. A domain is needed only when you want to use your own domain name.

Install and connect in four steps

Start with one server and one small workload. The exact installer screens and available actions may change during beta.

1. Apply for beta access

   Apply through the portal. Approved users receive access in stages; an application does not immediately unlock installation.

2. Add your server

   Once approved, sign in and create the server record for the machine or VM you want to use. Keep its purpose and identity clear so you connect the intended host.

3. Follow Dexlinkx Manager

   Use the approved installation guide and follow the guided workflow for your supported setup. Read the selected installation target and access permissions before confirming changes.

4. Check the portal

   Confirm that the intended server connects and that status and resource information update. Review its access profile before enabling management actions.

Prepare your first website

Use a simple static test site before adding a database or a production application. Create the site through an available hosting workflow and confirm that its content loads at the configured address.

For a public domain, configure DNS for the chosen server address and check the network path, firewall and HTTPS state. A home connection behind carrier-grade NAT may need an alternative network arrangement; forwarding a router port alone will not resolve that.

After the test site works, choose WordPress, PHP or Laravel if those workflows are available for your beta account and access profile. Files and application databases stay on your server. Keep a separate, tested recovery plan.

• Plan domains, networking and a first website (English)

If something does not connect

Separate connection problems from website problems. An offline portal status and a website that does not load are different symptoms.

• Server offline: check host power, local networking, internet access and the installation or pairing status.
• Works locally but not externally: check public DNS, the router, firewall rules and whether the connection uses carrier-grade NAT.
• An action is unavailable: review beta availability and the server access profile before changing host settings.
• Need recovery: use your retained local or SSH access and the beta documentation. Avoid reinstalling over existing data as a troubleshooting shortcut.