Protected server onboarding

This checklist outlines the normal path for an authorised server host to register a DFBHD server, connect Devil-Guard Server and confirm live protection reporting.

Before installation

Authorised access

Use an approved Server Host or Administrator account. Do not share server API credentials with players or unauthorised operators.

Working HawkSync instance

Confirm the DFBHD server and HawkSync player snapshot are working before adding Devil-Guard enforcement.

Current release

Download the current Devil-Guard Server release published on the main page and keep the version matched to the supported web release.

Backups

Back up the server configuration, HawkSync data and existing Devil-Guard settings before replacing or upgrading files.

Installation path
01

Register the server

Create or confirm the server record in the Control Center and record the assigned server identity and protected API credentials.

02

Install the enforcer

Place Devil-Guard Server on the protected Windows host, configure the website endpoint, server identity, API token and HawkSync source required by the release.

03

Restrict access

Store configuration secrets with restrictive permissions. Allow only the network ports required by the game, HawkSync and the outbound website connection.

04

Start and verify

Start the service and confirm the public server card reports the expected name, instance, version, health and online state.

Operational checks

Player snapshot

Confirm Devil-Guard can read the current HawkSync player session and correctly associate live names with registered accounts and approved aliases.

PC requirement

Confirm players without a valid signed Devil-Guard PC identity are handled according to the protected-server policy.

Enforcement reporting

Test that HawkSync kick results, managed blacklist status and Devil-Guard-owned firewall actions are reported separately and accurately.

Logs and health

Review service logs and the Control Center after startup, upgrades and configuration changes. Resolve degraded health before relying on enforcement.

Important

Use the release-specific deployment notes

This public page is a checklist, not a replacement for the exact README, deployment notes and environment examples included with the downloaded Server package.