Icinga director wizard Unable to detect your deployment endpoint

Hi,
I’ve done a fresh Icinga2 installation. Two master servers, one database server, and an Icinga Web server with Director. I’m getting stuck at the Director wizard.
The message says: “Unable to detect your deployment endpoint.”

The logs show:

information/HttpServerConnection: Request GET /v1/ (from [xx.xx.xx.xx]:53892), user: xx.xx.xx.xx, agent: , status: OK) took total 0ms.
[2025-04-23 12:16:34 +0200] information/HttpServerConnection: Request GET /v1/objects/zones (from [xx.xx.xx.xx]:53892), user: xx.xx.xx.xx, agent: , status: OK) took total 0ms.
[2025-04-23 12:16:34 +0200] information/HttpServerConnection: Request GET /v1/objects/endpoints (from [xx.xx.xx.xx]:53892), user: xx.xx.xx.xx, agent: , status: OK) took total 0ms.
[2025-04-23 12:16:34 +0200] information/HttpServerConnection: HTTP client disconnected (from [xx.xx.xx.xx]:53892)
[2025-04-23 12:16:34 +0200] information/ApiListener: New client connection from [xx.xx.xx.xx]:53894 (no client certificate)
[2025-04-23 12:16:34 +0200] information/HttpServerConnection: Request GET /v1/ (from [xx.xx.xx.xx]:53894), user: xx.xx.xx.xx, agent: , status: OK) took total 0ms.
[2025-04-23 12:16:34 +0200] information/HttpServerConnection: Request GET /v1/status (from [xx.xx.xx.xx]:53894), user: xx.xx.xx.xx, agent: , status: OK) took total 0ms.

hat looks good so far.

However, the Director doesn’t proceed in the wizard and says:
“Unable to detect your deployment endpoint. I was looking for the first endpoint configured with an assigned API user in the ‘siguvmaster’ zone.”

What can I do? Do you have any ideas?

Debian 12.10
Director version: 1.11.4
Icingaweb: 2.12.4
Icinga2: r2.14.5-1

zone config:

/*

  • Endpoint and Zone configuration for a cluster setup
  • This local example requires NodeName defined in
  • constants.conf.
    */

object Endpoint “hostdomain1” {
}

object Endpoint “hostdomain2” {
host = “host.domain.org
port = “5665”
}

object Zone “xxxmaster” {
endpoints = [ “hostdomain1”,“hostdomain2” ]
}
/*

  • Defines a global zone for distributed setups with masters,
  • satellites and clients.
  • This is required to sync configuration commands,
  • templates, apply rules, etc. to satellite and clients.
  • All nodes require the same configuration and must
  • have accept_config enabled in the api feature.
    */

object Zone “global-templates” {
global = true
}

/*

  • Defines a global zone for the Icinga Director.
  • This is required to sync configuration commands,
  • templates, apply rules, etc. to satellite and clients.
  • All nodes require the same configuration and must
  • have accept_config enabled in the api feature.
    */

object Zone “director-global” {
global = true
}

/*

  • Read the documentation on how to configure
  • a cluster setup with multiple zones.
    */

/*
object Endpoint “masterxxx” {
host = “masterxxx”
}

object Endpoint “satellitexx” {
host = “satellitexxx”
}

object Zone “master” {
endpoints = [ “masterxxx” ]
}

object Zone “satellite” {
parent = “master”
endpoints = [ “satellitexx” ]
}
*/

API Config:

/**

  • The ApiUser objects are used for authentication against the API.
    */
    object ApiUser “root” {
    password = “xxx”
    // client_cn = “”

permissions = [ “*” ]
}

object ApiUser “icingaweb2” {
password = “xxx”
permissions = [ “status/query”, “actions/", "objects/modify/”, “objects/query/*” ]
}

object ApiUser “director” {
password = “xxx”
permissions = [ “*” ]
}