Skip to content
VORQUL
Documentation

Reference material, not marketing copy

Installation, configuration, subsystems and the failure modes that actually happen. Every reference page stands on its own and can be read without the rest.

·

Vorqul documentation covers requirements, installation and first setup for both products, followed by a reference page for each subsystem: moderation, automod and analytics for VorqulBOT, and web hosting, DNS, mail, databases, SFTP, firewall and monitoring for VorqulPanel.

01 Requirements

VorqulPanel expects a clean Debian 12, Ubuntu 22.04+ or AlmaLinux 9 server with root access, at least 2 GB RAM and Java 17 or newer. VorqulBOT expects Node.js 18+ (22 LTS) and a Discord application with the message content and server members intents enabled.

  • Linux server with root access
  • Java 17+ for the panel
  • Node.js 18+ (22 LTS) for the bot
  • A container runtime is optional, not required

02 Installation

The panel ships as a thin JAR plus a lib/ directory and a helper script that registers the systemd unit, creates the service user and opens the panel port. The bot ships as a repository you clone, configure through .env and run with npm, a Pterodactyl egg or the bundled launcher.

Step-by-step guides live at /docs/install: VorqulBOT in about ten minutes, VorqulPanel in 15 to 30.

03 First setup

For the panel: open the web UI on the port printed by the installer, create the admin account, add your first domain and run the built-in config test. For the bot: invite it with the recommended permission set, enable the modules you need, then set a staff role and a log channel before anything else.

04 Troubleshooting

  • Package installs fail: almost always RestrictSUIDSGID=yes in the systemd unit breaking post-install scripts.
  • Panel unreachable: the firewall needs an explicit rule for the panel port, and for SSH on a custom port.
  • Certificates issued but the site still serves HTTP: an adopted vhost needs a confirmed takeover before the panel rewrites it.
  • Slash commands missing: re-run the deploy step and confirm the applications.commands scope was in the invite.