Provisioning Databases and Additional Port Allocations in DustBowl Warden

Databases and Network Allocations in DustBowl Warden

Modern multiplayer game servers often require auxiliary services: relational databases for plugin state persistence (e.g., CoreProtect, LuckPerms, LiteBans) and secondary network ports for web maps, RCON, voice bridges, or cross-play proxies. DustBowl Warden provides managed, isolated database provisioning and self-service port assignment directly from the instance dashboard.

---

Provisioning Managed Databases

Every DustBowl game server tier includes access to managed relational database services (MariaDB and PostgreSQL) hosted on high-speed NVMe database clusters.

Creating a New Database

1. Open your server instance in Warden and click the Databases tab.
2. Click New Database.
3. Enter a descriptive database name (e.g., luckperms or coreprotect).
4. Select the connection origin:
   • Internal Only (% or 10.0.0.0/8): Recommended for maximum security. Allows connections only from within the internal host network.
   • Specific IP / Any: Allows remote external tools (e.g., HeidiSQL, DBeaver) to connect.
5. Click Create Database.

Retrieving Connection Parameters

Once created, your database card displays all connection values:

• Host / Endpoint: The internal database cluster endpoint (e.g., db.internal.dustbowl.games or node IP).
• Port: 3306 (MariaDB / MySQL) or 5432 (PostgreSQL).
• Database Name: Generated isolated database identifier (e.g., s123_luckperms).
• Username: Assigned instance database user (e.g., u123_luckperms).
• Password: Click the eye icon to reveal the secure cryptographically generated password.

Copy these parameters directly into your plugin's config.yml or database properties file.

Rotating Database Passwords

If a database password is leaked:

1. Click the action menu on the database card.
2. Select Rotate Password.
3. Update the newly generated secret in your plugin configuration and reload the plugin.

---

Managing Network Port Allocations

Each game server has a primary port (such as 25565 for Minecraft Java, 27015 for CS2/Source, or 7777 for Unreal Engine games). However, many plugins and extensions require additional ports:

Common Uses for Secondary Ports

• Web Maps: Dynmap, BlueMap, Pl3xMap (typically HTTP port 8123 or assigned high port).
• Cross-Play: GeyserMC / Floodgate (UDP port for Bedrock players).
• Voting Listeners: Votifier / NuVotifier (typically port 8192 or assigned).
• Voice Integrations: Simple Voice Chat, Plasmo Voice.
• RCON / Query: Remote administration and status pingers.

Assigning an Additional Port

1. Navigate to the Network or Settings > Port Allocations tab.
2. Click Create Allocation.
3. Warden will assign an available high port from the host node's pool.
4. Note the allocated port number (e.g., 25580).
5. Configure your plugin to bind to this assigned port (e.g., set webserver-port: 25580 in your map plugin config).
6. Set the bind address to 0.0.0.0.
7. Restart your server instance.

---

Setting the Primary Connection Port

If your server has multiple port allocations:

• The port designated as Primary is what players use to connect and what is displayed on the public status card.
• To change the primary port, click the three dots next to the desired allocation and select Set as Primary.