shadow1ng/fscan · error

unknown_status_code: %d

Error message

unknown_status_code: %d

What it means

Guard in doNeo4jAuth: the Neo4j HTTP API returned a status code that is neither 200 (auth OK) nor 401/403 (auth failed), e.g. 5xx or a redirect. The outcome is classified as unknown because the code does not map to a credential verdict.

Source

Thrown at plugins/services/neo4j.go:119

			Success:   true,
			Conn:      &neo4jConnWrapper{},
			ErrorType: ErrorTypeUnknown,
			Error:     nil,
		}
	}

	if resp.StatusCode == 401 || resp.StatusCode == 403 {
		return &AuthResult{
			Success:   false,
			ErrorType: ErrorTypeAuth,
			Error:     fmt.Errorf(i18n.GetText("service_auth_failed")+": %d", resp.StatusCode),
		}
	}

	return &AuthResult{
		Success:   false,
		ErrorType: ErrorTypeUnknown,
		Error:     fmt.Errorf(i18n.GetText("unknown_status_code")+": %d", resp.StatusCode),
	}
}

// neo4jConnWrapper Neo4j连接包装器
type neo4jConnWrapper struct{}

func (w *neo4jConnWrapper) Close() error {
	return nil
}

// classifyNeo4jErrorType Neo4j错误分类
func classifyNeo4jErrorType(err error) ErrorType {
	if err == nil {
		return ErrorTypeUnknown
	}

	neo4jAuthErrors := []string{
		"authentication failed",

View on GitHub (pinned to 95cc12e753)

Solutions

1. Check whether the Neo4j HTTP endpoint is up and not behind a gateway returning errors
2. Verify the target URL points to the Neo4j REST API rather than another service
3. Retry transient 5xx responses with backoff

When it happens

Trigger: Thrown at plugins/services/neo4j.go:119 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of shadow1ng/fscan@95cc12e753 (2026-09-06). Data as JSON: /api/errors/6dd557d51116633d. Report an issue: GitHub.