Servbase Error Codes: SVA and SVN Complete Reference - Servbase

Servbase exposes a mix of platform-specific codes and standard HTTP-derived failures.

Prefixes

Prefix	Meaning
`SVA-###`	dashboard-facing / API-facing Servbase errors
`SVN-###`	internal node-agent or runtime worker errors that may surface during operations

Common API codes

Code	Meaning
`SVA-101`	custom domain already exists or is already assigned
`SVA-102`	protected primary-domain action blocked
`SVA-103`	provider validation records not ready yet
`SVA-104`	provider authentication or authorization issue
`SVA-105`	provider zone access issue
`SVA-106`	generic provider API failure
`SVA-107`	too many authentication attempts
`SVA-108`	missing, invalid, or expired token
`SVA-109`	account disabled
`SVA-110`	account suspended path
`SVA-112`	application not found
`SVA-113`	domain not found for the current app or user
`SVA-115`	email validation or conflict issue
`SVA-500`	unclassified server-side failure

Common runtime and action failures

Error	Meaning
`HTTP 409` terminal unavailable	terminal is not available for that app type or deployment state
`HTTP 409` runtime logs disabled	runtime logs are not enabled in settings
`HTTP 423 Locked`	runtime action blocked because the app is paused due to overdue billing
`BILLING-CHECKOUT-PLAN-RESOLUTION`	billing settlement could not resolve the expected plan cleanly

Common node-agent codes

Code	Meaning
`SVN-101`	deploy queue saturation
`SVN-102`	internal request signature validation failed
`SVN-103`	internal bearer validation failed
`SVN-104`	invalid app, path, or archive input
`SVN-105`	unsupported archive format
`SVN-500`	unclassified node-side failure

Standard fallback forms

You may also see standard status-derived variants such as:

SVA-400
SVA-401
SVA-403
SVA-404
SVA-409
SVA-429