n8n-nodes-rcon

A production-ready n8n community node for remote game server administration via RCON (Remote Console) protocol.

⚠️ Security Warning: RCON transmits passwords in plaintext over TCP. Only use this node in secure network environments with VPN connections, SSH tunnels, or when n8n runs on the same machine as your game server. Never expose RCON ports directly to the internet.

ℹ️ Self-Hosted Only: This node requires TCP socket access and can only be used with self-hosted n8n instances. It will not work on n8n Cloud.

Control and manage your game servers directly from n8n workflows - execute commands, retrieve status, automate server management, and integrate with other n8n nodes for powerful automation scenarios.

RCON Protocol is a network protocol for remote server administration in Source Engine games and other compatible game servers.

n8n is a fair-code licensed workflow automation platform.

Features

✅ Multiple Protocol Support - Source RCON (TCP) and BattlEye RCON (UDP)
🎮 Wide Game Support - Minecraft, Source games (CS:GO, CS2, TF2), Rust, ARK, DayZ, ARMA 2/3, and more
🔒 Secure Authentication - Password-based authentication with proper error handling
📦 Multi-Packet Responses - Correctly handles responses larger than 4KB (Source RCON)
⚡ Async Operation - Non-blocking command execution
🛡️ Type-Safe - Built with TypeScript for reliability
⏱️ Configurable Timeouts - Customize connection and I/O timeouts
🎪 Error Handling - Comprehensive error types with continueOnFail support
🔄 Workflow Integration - Seamlessly integrate server management into n8n workflows
🎯 BattlEye Support - Full UDP-based protocol with CRC32 validation and heartbeat

Installation

Via n8n Community Nodes

In n8n, go to Settings > Community Nodes
Click Install a community node
Enter: n8n-nodes-rcon
Click Install

Manual Installation (Self-Hosted)

cd ~/.n8n/nodes
npm install n8n-nodes-rcon

Restart n8n to load the new nodes.

Verify Installation

After installation, look for the RCON node in the nodes panel under the "Transform" category.

Quick Start

1. Set Up Credentials

Before using the RCON node, you need to configure credentials:

Open any workflow in n8n
Add the RCON node to your workflow
Click on Credential to connect with
Click Create New
Fill in the connection details:
- Protocol: Select protocol type (Source RCON for most games, BattlEye RCON for DayZ/ARMA)
- Host: Your server's IP address or hostname (e.g., 192.168.1.100 or game.example.com)
- Port: RCON port (Source: 25575 for Minecraft, 27015 for Source games; BattlEye: typically game port like 2305 for DayZ)
- Password: Your RCON password
- Connection Timeout: Optional, defaults to 5000ms

2. Send Your First Command

Add the RCON node to your workflow
Select your configured credentials
Choose operation: Send Command
Enter a command (e.g., list for Minecraft)
Execute the workflow

Usage Examples

Example 1: Monitor Server Status

Create a workflow that checks your Minecraft server status every 5 minutes:

Schedule Trigger (every 5 min)
  → RCON: "list"
  → IF (player count > 0)
    → Send notification to Discord/Slack

Example 2: Automated Server Announcements

Announce scheduled maintenance to players:

Schedule Trigger (specific time)
  → RCON: "say Server restart in 30 minutes"
  → Wait 15 minutes
  → RCON: "say Server restart in 15 minutes"
  → Wait 10 minutes
  → RCON: "say Server restart in 5 minutes"
  → Wait 5 minutes
  → RCON: "stop"

Example 3: Webhook-Triggered Commands

Allow external systems to trigger server commands:

Webhook Trigger
  → Function: Validate request
  → RCON: Execute command from webhook payload
  → Respond to webhook with result

Example 4: Automated Backups

Create backups before executing maintenance commands:

Schedule Trigger
  → RCON: "save-off" (disable autosave)
  → RCON: "save-all" (force save)
  → Execute File Operations: Backup world files
  → RCON: "save-on" (enable autosave)
  → Send notification: Backup complete

Example 5: Dynamic Server Management

Adjust server settings based on time of day:

Schedule Trigger (every hour)
  → Get Current Time
  → Switch (time-based):
    Case "Night (00:00-06:00)":
      → RCON: "difficulty peaceful"
    Case "Day (06:00-22:00)":
      → RCON: "difficulty normal"
    Case "Prime Time (18:00-22:00)":
      → RCON: "difficulty hard"

Supported Games & Servers

Source RCON Protocol (TCP)

Minecraft (Java & Bedrock)

Protocol: Source RCON
Default Port: 25575
Example Commands: list, say <message>, give <player> <item>, weather clear, time set day

Source Engine Games

Protocol: Source RCON
Default Port: 27015
Supported: CS:GO, Counter-Strike 2, Team Fortress 2, Garry's Mod, Left 4 Dead 2
Example Commands: status, changelevel <map>, kick <player>, sv_cheats <0|1>

Rust

Protocol: Source RCON
Default Port: 28016
Example Commands: save, quit, global.ban <player>, weather.rain 0

ARK: Survival Evolved

Protocol: Source RCON
Default Port: 27020
Example Commands: SaveWorld, DestroyWildDinos, Broadcast <message>

Other Source RCON Compatible Games

Eco
Conan Exiles
7 Days to Die
Satisfactory
Space Engineers
Valheim (with mods)

BattlEye RCON Protocol (UDP)

DayZ

Protocol: BattlEye RCON
Default Port: 2305 (or game port)
Example Commands: players, kick <player>, say -1 <message>, loadScripts, #shutdown

ARMA 2

Protocol: BattlEye RCON
Default Port: 2302 (or game port)
Example Commands: players, kick <player>, admins, missions

ARMA 3

Protocol: BattlEye RCON
Default Port: 2302 (or game port)
Example Commands: players, kick <player>, say -1 <message>, loadScripts

Arma Reforger

Protocol: BattlEye RCON
Default Port: 2001 (or game port)
Example Commands: players, kick <player>, say -1 <message>

Configuration Options

Node Parameters

Operation: Send Command

Parameter	Description	Required
Command	The RCON command to execute	Yes

Credential Options

Field	Type	Default	Description
Host	String	-	Server hostname or IP address
Port	Number	25575	RCON port number
Password	String	-	RCON password (stored encrypted)
Connection Timeout	Number	5000	Connection timeout in milliseconds

Troubleshooting

Connection Issues

Problem: "Connection timeout" or "Connection failed"

Solutions:

Verify the server is running and accessible
Check firewall rules allow connections to the RCON port
Ensure the RCON port is correctly configured in server.properties
Try increasing the connection timeout in credentials

Authentication Issues

Problem: "Authentication failed - incorrect password"

Solutions:

Double-check your RCON password
Ensure RCON is enabled on the server
Check for typos or extra spaces in the password field
Verify the password in your server configuration file

Warning: Multiple failed authentication attempts may result in a temporary IP ban!

Command Execution Issues

Problem: "Command failed" or empty responses

Solutions:

Verify the command syntax is correct for your game/server
Check if you have permission to execute the command
Some commands may not return output (this is normal)
Use continueOnFail option if commands may legitimately fail

Multi-Packet Response Issues

Problem: Truncated or incomplete responses

Solution: This node automatically handles multi-packet responses. If you're still experiencing issues:

Increase the I/O timeout in your credentials
Check your network connection stability
Report the issue with server type and command details

Node Not Appearing

Problem: RCON node doesn't appear after installation

Solutions:

Restart n8n: sudo systemctl restart n8n
Clear browser cache and reload
Check n8n logs for installation errors: ~/.n8n/logs/
Reinstall the node: npm uninstall n8n-nodes-rcon && npm install n8n-nodes-rcon

Getting Help

🐛 Bug Reports: GitHub Issues
💡 Feature Requests: GitHub Issues
💬 Questions: GitHub Discussions
📖 n8n Community: n8n Forum

Security Warnings

Critical Security Considerations

1. Unencrypted Connection (CRITICAL)

The RCON protocol transmits passwords in plaintext over TCP. This is the most important security consideration.

Recommended secure configurations:

✅ Best: Run n8n on the same machine as your game server (localhost connection)
✅ Good: Use VPN connections to your game servers
✅ Good: Use SSH tunneling for remote connections (ssh -L port forwarding)
✅ Keep RCON ports firewalled and only accessible from trusted IPs
❌ NEVER expose RCON ports directly to the internet
❌ NEVER use RCON over untrusted networks without encryption

2. IP Ban Risk

After multiple failed authentication attempts, the server will ban your IP address:

Use strong, correct passwords
Test credentials before deploying workflows
Consider the impact of workflow errors that retry authentication

3. Strong Passwords

Use long, random passwords (20+ characters)
Never use the same password as other server credentials
Store passwords securely in n8n (they are encrypted at rest)
Rotate passwords regularly

4. Command Validation

Validate and sanitize any user input used in commands
Be cautious with commands that can modify server state
Use workflow permissions to restrict who can execute server commands
Log all command executions for audit purposes

5. n8n Security Best Practices

Restrict access to n8n workflows containing RCON nodes
Use webhook authentication for external triggers
Enable n8n audit logging
Keep n8n and this node updated to the latest versions

Error Handling

The RCON node supports n8n's continueOnFail option. When enabled, execution errors won't stop the workflow:

// Success response
{
  "command": "list",
  "response": "There are 3 players online: Alice, Bob, Charlie",
  "success": true,
  "timestamp": "2025-10-30T22:15:00.000Z"
}

// Error response (with continueOnFail enabled)
{
  "error": "Connection timeout",
  "success": false,
  "timestamp": "2025-10-30T22:15:00.000Z"
}

Contributing

Contributions are welcome! Here's how you can help:

Report Bugs: Open an issue with details about the problem
Suggest Features: Share your ideas for improvements
Submit Pull Requests: Follow the development setup below

Development Setup

# Clone the repository
git clone https://github.com/goevexx/n8n-nodes-rcon.git
cd n8n-nodes-rcon

# Install dependencies
npm install

# Build the project
npm run build

# Run tests
npm test

# Lint and format code
npm run lint
npm run format

Local Testing with Docker

The repository includes Docker Compose configurations for local testing with real game servers:

# Start test environment (n8n + game servers)
docker-compose up -d

# Access n8n at http://localhost:9001

Available Test Servers:

Source RCON (TCP) - Minecraft Server
- Host: minecraft-rcon-test
- Port: 25575
- Password: minecraft_rcon_password
- Protocol: Source RCON (TCP)
BattlEye RCON (UDP) - Authentic Protocol Implementation
- Host: battleye-rcon-test
- Port: 2305
- Password: dayz_rcon_password
- Protocol: BattlEye RCON (UDP)
- Implements the complete BattlEye RCON protocol with CRC32 validation, sequence numbers, and heartbeat
- Compatible with DayZ, ARMA 2, ARMA 3, Arma Reforger protocol specs
- Responds to standard commands like players, empty heartbeat commands

Both test servers implement authentic protocol specifications and can be used to verify RCON functionality without needing external game servers.

Project Structure

n8n-nodes-rcon/
├── credentials/
│   └── RconApi.credentials.ts    # Credential type definition
├── nodes/
│   └── Rcon/
│       ├── Rcon.node.ts         # Main node implementation
│       ├── RconClient.ts        # RCON protocol client
│       ├── RconTypes.ts         # TypeScript types
│       ├── helpers.ts           # Helper functions
│       └── rcon.svg             # Node icon
├── src/
│   └── index.ts                 # Package exports
├── dist/                        # Compiled JavaScript (generated)
└── README.md

Project Status

This project is actively maintained. Current focus:

✅ Core RCON protocol implementation complete
✅ Full multi-packet response handling
✅ Production-ready error handling
🔄 Adding more usage examples
🔄 Expanding test coverage
📋 Planning additional features

See ROADMAP.md for detailed plans.

License

MIT - Free to use, modify, and distribute.

Acknowledgments

Built for the n8n community
Based on Source RCON Protocol Specification by Valve
Thanks to all contributors and users

Support

Need help? Here's how to get support:

Roadmap

Future enhancements being considered:

Additional operations (batch commands, server info)
Connection pooling for high-volume workflows
UDP RCON support (for GoldSrc games)
Challenge protocol support
Retry mechanism with exponential backoff
Server status monitoring operation
Multi-server operation support

Built with ❤️ for the n8n and gaming communities

Documentation · Issues · Discussions

Name		Name	Last commit message	Last commit date
.github		.github
bin		bin
credentials		credentials
examples		examples
nodes/Rcon		nodes/Rcon
src		src
tests		tests
.gitignore		.gitignore
.prettierrc.js		.prettierrc.js
CHANGELOG.md		CHANGELOG.md
CLAUDE.md		CLAUDE.md
LICENSE		LICENSE
README.md		README.md
TESTING.md		TESTING.md
docker-compose.yml		docker-compose.yml
eslint.config.mjs		eslint.config.mjs
jest.config.js		jest.config.js
package-lock.json		package-lock.json
package.json		package.json
tsconfig.json		tsconfig.json

Latest commit

History

Folders and files

Repository files navigation

n8n-nodes-rcon

Table of Contents

Features

Installation

Via n8n Community Nodes

Manual Installation (Self-Hosted)

Verify Installation

Quick Start

1. Set Up Credentials

2. Send Your First Command

Usage Examples

Example 1: Monitor Server Status

Example 2: Automated Server Announcements

Example 3: Webhook-Triggered Commands

Example 4: Automated Backups

Example 5: Dynamic Server Management

Supported Games & Servers

Source RCON Protocol (TCP)

Minecraft (Java & Bedrock)

Source Engine Games

Rust

ARK: Survival Evolved

Other Source RCON Compatible Games

BattlEye RCON Protocol (UDP)

DayZ

ARMA 2

ARMA 3

Arma Reforger

Configuration Options

Node Parameters

Operation: Send Command

Credential Options

Troubleshooting

Connection Issues

Authentication Issues

Command Execution Issues

Multi-Packet Response Issues

Node Not Appearing

Getting Help

Security Warnings

Critical Security Considerations

1. Unencrypted Connection (CRITICAL)

2. IP Ban Risk

3. Strong Passwords

4. Command Validation

5. n8n Security Best Practices

Error Handling

Contributing

Development Setup

Local Testing with Docker

Project Structure

Project Status

License

Acknowledgments

Support

Roadmap

About

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages