The table below covers errors that appear in the heliana UI — in form banners, toast
notifications, or inline field hints. Errors are grouped by area.
| Message |
Meaning |
Fix |
Invalid RCON password |
heliana connected to the RCON port but the password was rejected. |
Re-enter the password from Rcon.cfg. |
RCON connection timed out |
No response from the RCON host:port within 5 seconds. |
Check host, port, and firewall. See Configure RCON. |
RCON host points to a private/internal address |
The RCON host resolves to a private IP; heliana refuses to connect to it. |
Use a public IP address. |
RCON host could not be resolved |
DNS lookup of the RCON host failed. |
Fix the hostname or use a raw IP. |
RCON host resolves to a private/internal address |
The hostname resolves through DNS to a private IP. |
Use a different host or a public IP. |
SFTP host points to a private/internal address |
Same as above, for the SFTP host. |
Use a public IP address. |
SFTP host could not be resolved |
DNS lookup of the SFTP host failed. |
Fix the hostname or use a raw IP. |
SFTP host resolves to a private/internal address |
Same as above, for SFTP. |
Use a different host or a public IP. |
Server file check failed — ... |
heliana reached the SFTP host but couldn’t confirm it can write your admin whitelist file. The text after the dash names the reason (timeout, bad credentials, or a path/permission problem). |
See Server won’t connect. |
Server capacity reached (max N servers during the public beta). |
The overall server cap for the beta has been reached, across all organizations. |
Contact heliana support or wait for capacity to free up. |
Server limit reached (max 2 per organization). |
Your organization already has 2 servers. |
Delete an existing server before adding another. |
See Server won’t connect for the full breakdown
and fix steps.
| Message |
Meaning |
Fix |
Trigger is not runnable |
You tried to run a trigger that isn’t a Manual trigger, or a manual trigger whose Enabled toggle is off. |
Confirm the trigger’s kind is Manual and it’s enabled. |
Trigger is not available on this server |
The manual trigger you ran isn’t scoped to the server you ran it on. |
Add that server to the trigger’s scope, or set the scope to all servers. |
No access to ban across all servers |
The ban action’s scope is set to All servers, but the member running it doesn’t have access to every server in the organization. |
Have an Owner/Admin (or a member with unrestricted server access) run it, or change the ban action’s scope to This server. |
| Message |
Meaning |
Fix |
Webhook URL is not a valid URL |
The webhook URL couldn’t be parsed as a URL. |
Correct the URL format in the trigger action. |
Webhook URL must use https:// |
Only HTTPS webhook targets are allowed. |
Update the URL to start with https://. |
Webhook URL points to a private address |
The webhook URL is a literal IP that’s private. |
Use a publicly reachable HTTPS endpoint. |
Webhook URL host could not be resolved |
DNS lookup of the webhook host failed. |
Fix the hostname in the webhook URL. |
Webhook URL resolves to a private address |
The webhook hostname resolves through DNS to a private IP. |
Use a public endpoint. |
An action with an empty webhook URL fails outright — it’s recorded as a failed run, not skipped
silently.
These appear on a roster group’s ban source (BattleMetrics, Community Ban List, or Remote Ban
File) after a failed sync.
| Message |
Meaning |
Fix |
Source request failed: ... |
The request to the source’s endpoint didn’t complete (network error, DNS failure, connection refused, etc.). |
Check the source’s URL and that the endpoint is reachable from the internet. |
Source endpoint rejected credentials (HTTP <status>) |
The source rejected the API key or credentials configured for it. |
Re-check the credentials on the source. |
Source endpoint returned HTTP <status> |
The source responded with an unexpected HTTP status. |
Check the source’s URL and whether the remote service is having problems. |
| Message |
Meaning |
Fix |
Could not load players |
The live players query failed in the UI. |
The RCON connection may be down — check the server’s status, then refresh the page. |