Get instant answers with RunRacks AI

Use RunRacks AI at /ai for setup and troubleshooting questions at any time, learn how to ask questions that get useful answers, and know when to open a support ticket instead.

  • Beginner
  • All
  • 4 min read

By RunRacks Team · Published

RunRacks AI answers questions about servers, setup and troubleshooting at any time of day. It is the quickest way to get unstuck on a "how do I…" question, understand an error message or plan your next step. This guide shows how to use it well, what to keep out of your questions, and when a support ticket is the better choice.

Before you start

  • Open RunRacks AI in your browser.
  • Have the details of your question ready: your server type (Linux VPS, Windows VPS or Admin RDP), the operating system if you know it, and any exact error text.

What RunRacks AI is good at

Use it for questions like these:

  • Setup: "How do I install Nginx on Ubuntu 24.04?" or "How do I open a port in Windows Firewall?"
  • Explaining errors: paste an error and ask what it means and what usually causes it.
  • Choosing an approach: "Should I use a Linux VPS or a Windows VPS for a Python bot?"
  • Commands: "What does chmod 755 do?" or "How do I check free disk space in PowerShell?"
  • RunRacks basics: where to find your login details in the Dashboard, or which port to use for Remote Desktop.

It is available any time, so it is useful at 3 a.m. when a small question blocks you.

Ask good questions

The more context you give, the more useful the answer. Compare:

  • Weak: "my site doesn't work"
  • Strong: "Ubuntu 24.04 Linux VPS with Nginx. example.com shows 502 Bad Gateway since I updated PHP. How do I find the cause?"

A good question includes:

  1. The system: Linux distribution and version, or Windows Server version.
  2. What you are trying to do.
  3. What happened, with the exact error message.
  4. What you already tried.

Ask follow-up questions in the same conversation. "That command says permission denied" gives it the context it needs to suggest the next step.

Keep secrets out of your questions

The same goes for personal data about other people, such as customer lists from a database.

Check the answer before you act

AI answers are a strong starting point, but they can be wrong or out of date. Before you run anything on a live server:

  • Read each command and make sure you understand what it changes.
  • Take a backup, or a copy of the config file you are about to edit.
  • Be extra careful with anything that touches the firewall, SSH or Remote Desktop settings, disks, or user accounts. A mistake there can lock you out.

If you do lock yourself out, the browser console in the control panel of your Dashboard still works.

When to open a ticket instead

RunRacks AI cannot look inside your account or your server. Open a support ticket when:

  • The server does not respond and the basic checks did not help.
  • You need something changed on the RunRacks side, such as a service, an invoice or an account setting.
  • You have a billing question about your own invoices, refunds or cancellations.
  • You suspect a problem with the network or the hardware.

Check it works

You are using it well when:

  • Your answers come back specific to your OS and situation, not generic.
  • You test suggested commands on a safe target first, or understand them before running them.
  • You switch to a ticket when the question is about your account, billing or an outage.

Troubleshooting

  • The answer is too generic: add your OS version, the exact error and what you tried, then ask again.
  • The command fails: paste the full error back into the same conversation and ask what it means.
  • The answer conflicts with a RunRacks guide: follow the guide for RunRacks-specific details, such as RDP on port 12230, and ask support if you are unsure.
  • You need a decision about your account: RunRacks AI can point you to /terms and /refund, but a ticket gives you an answer from the team.

Next steps

Was this guide helpful?

Still stuck?

Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.

Getting started

Edit files with nano: a beginner's guide

Open, edit, search and save files with the nano text editor on a Linux server, including cutting and pasting lines, showing line numbers and safely editing system config files with sudo.

  • Beginner
  • Linux VPS
  • 5 min read

Getting started

Your first hour with a new RunRacks server

A step-by-step roadmap for the first hour after your RunRacks server is delivered, from finding your login details to changing the password, updating the OS and picking your next guides.

  • Beginner
  • All
  • 5 min read

Getting started

How to choose a server location

Pick a data center location based on where your users, broker or team are, confirm it with ping tests, and weigh the legal and latency points that come with each choice.

  • Beginner
  • All
  • 4 min read