windmill-labs/windmill · error · Error
Debug signing is not configured on the server. Please contac
Error message
Debug signing is not configured on the server. Please contact your administrator.
What it means
When the /debug/sign endpoint responds non-OK and its body contains 'not initialized', the client maps it to this friendly message: the server's debug signing keys have never been initialized, so no debug session can be authorized. It is a server configuration problem, not a client bug.
Source
Thrown at frontend/src/lib/components/debug/MonacoDebugger.svelte:357
): Promise<{
token: string
code: string
}> {
if (!workspace) {
throw new Error('No workspace selected')
}
const response = await fetch(`/api/w/${workspace}/debug/sign`, {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ code: codeToSign, language: lang })
})
if (!response.ok) {
const errorText = await response.text()
// Parse specific error cases for better user messages
if (errorText.includes('not initialized')) {
throw new Error(
'Debug signing is not configured on the server. Please contact your administrator.'
)
}
throw new Error(errorText || 'Failed to authorize debug session')
}
return await response.json()
}
function getDebugErrorMessage(error: unknown): string {
const message = error instanceof Error ? error.message : String(error)
// Handle token verification errors from debugger
if (message.includes('Token verification failed') || message.includes('Debug token required')) {
if (message.includes('expired')) {
return 'Debug session expired. Please try again.'
}
if (message.includes('Invalid JWT signature')) {View on GitHub (pinned to e474e8803c)
Solutions
- Initialize debug signing on the server (configure the signing secret per deployment docs)
- Ask the instance administrator to enable/configure debug signing
- Verify the server version supports the debug/sign endpoint
Defensive patterns
Strategy: try-catch
Try / catch
try { const { token, code } = await signDebugRequest(src, lang) } catch (e) { if (e.message.includes('not configured')) { showAdminConfigHelp() } else { throw e } } Prevention
- Check debug signing is configured before shipping debugger-dependent features
- Document the required server config for self-hosted admins
- Probe the endpoint once at startup to detect unconfigured instances early
When it happens
Trigger: POST /api/w/{workspace}/debug/sign returns an error status with a response body containing 'not initialized' — the instance has not configured debug signing (no signing secret/keys set up by the administrator).
Common situations: Self-hosted instance where the debug-signing env/secret was never set; fresh deployment migrated without initializing signing keys; EE feature attempted on a deployment lacking the license/config.
Related errors
- errorText || 'Failed to authorize debug session'
- Dependency generation failed: ${queueResponse.status} ${queu
- Not connected to DAP server
- No workspace selected
- Debug signing is not configured on the server. Please contac
AI-assisted analysis of windmill-labs/windmill@e474e8803c (2026-09-03).
Data as JSON: /api/errors/5af6fb7e7015911c.
Report an issue: GitHub.