Common error messages

Errors shown in form banners, toasts and inline field hints, grouped by area.

Server connection

Message	Meaning	Fix
A value is required	A required connection field was left blank.	Fill the field in.
Port must be a number	RCON port or SFTP port holds something that isn’t a plain decimal number.	Enter digits only — no spaces, no 0x prefix.
Address must not point into a private network	The RCON host or SFTP host you typed is itself a private address.	Use the server’s public IP or a public hostname.
Server limit reached (N)	Your organization already has as many running servers as your current allowance (N) — from your subscription, an active trial, or a granted allowance.	Pause one of them (Settings → Servers → the server → toggle Enabled off) to free the slot without losing its data, or raise the allowance in Settings → Billing. Retiring also frees the slot, but is permanent.
Server creation is frozen (N)	Server creation is frozen platform-wide.	Wait, or contact heliana support.
Could not save the server	Creating the server failed for a reason other than a limit or a freeze.	Retry; if it keeps failing, contact heliana support.
Could not save the connection	Saving the server’s connection details failed unexpectedly, for a reason with no message of its own.	Retry; if it keeps failing, contact heliana support.
The collector reaches the server from outside — this address points inside a private network.	The banner of a refused save: the RCON host or SFTP host you typed is a private address, and nothing was saved; the field shows the same rule.	Use the server’s public IP or a public hostname.
The saved connection could not be read — set the credentials again.	The stored credentials of the connection could not be decrypted or parsed.	Open the server’s settings and enter the credentials again.
The saved connection does not match this game.	The saved connection belongs to a different game than the server.	Re-enter the connection details for this server.
Server limit reached (N) — pause another server or add servers in Billing	Resume is refused because the organization already runs as many servers as its allowance covers.	Pause another server, or raise the allowance in Settings → Billing. See Plans and limits.
This server was retired — it cannot be paused or resumed.	A retired server can no longer change state.	Add a new server instead.
Could not change the server state	Pausing or resuming failed for a reason with no message of its own.	Retry; if it keeps failing, contact heliana support.
address points to a private network: <host>	The tooltip of the RCON row when its dot is red: the host resolves into a private network, which the collector does not connect to.	Use the server’s public IP or a public hostname.

Only the two address fields are examined for a private network, and only as you typed them: a hostname that resolves into a private range is saved without complaint, and shows up later as a red RCON dot.

For what the channel statuses report after saving, see Server won’t connect.

Automations

Message	Meaning	Fix
Could not save automation	Saving the automation failed.	Retry; check your connection.
Could not load automations	The Automations table failed to load.	Refresh the page.
Cron expression is invalid or never runs	The Cron schedule cannot be parsed, or no moment ever matches it.	Fix the expression; see Cron syntax.
Interval must be a positive number followed by d, h, m or s	The Interval value is not a positive whole number with a unit.	Use a value like 30m.
Not found	The automation you tried to open, edit, or run doesn’t exist or isn’t visible to you.	Confirm the automation still exists and that you have access to it.

Fetch actions

Message	Meaning	Fix
Fetch URL must use http:// or https://	The URL passed to ctx.fetch is empty or uses another scheme.	Use a full http:// or https:// address.
Fetch URL must not point into a private network	The URL, or a redirect it followed, resolves into a private network.	Use a publicly reachable endpoint.
Fetch host could not be resolved	The hostname has no DNS record heliana can resolve.	Check the hostname for typos.
Fetch redirected more than 5 times	The endpoint kept redirecting; heliana follows at most five redirects.	Point the URL at the final address.
Fetch timed out after 30 seconds	The endpoint did not answer in time, redirects included.	Check that the endpoint responds quickly.
Fetch response is larger than 4 MB	The response body is over the limit heliana reads.	Request a smaller answer from the endpoint.
Invalid fetch request	The arguments of ctx.fetch are not a URL string and an optional { method, headers, body } with string values.	Pass strings only.

An HTTP status of 400 or above is not an error of the action: ctx.fetch returns it as the answer with ok true, and the module decides what to do. A fetch that times out or is refused is recorded as a failed run; heliana doesn’t retry it or stop the rest of the automation’s actions.

Ban source sync

Message	Meaning	Fix
source answered <status>	The Ban Source’s endpoint responded with an unexpected HTTP status.	Check the source’s URL and whether the remote service is having problems.
A sync is already running for this source	A sync of this Ban Source is in progress.	Wait for it to finish, then run it again.

Players

Message	Meaning	Fix
Could not load players	The Players table failed to load and has no rows to show yet.	Refresh the page; if it keeps failing, contact heliana support.
Could not load more	The table already shows rows, but loading the next page of them failed. Appears under Load more in the lists that page, such as Players.	Press Load more again, or refresh the page.

Roles and members

Message	Meaning	Fix
You can only grant what your own role already has.	You tried to give a role a permission your own role doesn’t hold.	Ask someone whose role already has that permission to grant it.
The name “<name>” is already taken	A role or access list with that name already exists.	Pick another name.
The last owner cannot be demoted or removed — transfer ownership to another member first.	Every organization has exactly one Owner.	Transfer ownership to another member first: assign them the Owner role, and you become an Admin.