That address works on the computer running the container. From any other computer or phone, open https://<host>:3443 instead, with the host's name or IP address, so your password never crosses the network unencrypted. The browser warns about the node's self-signed certificate until you trust it; see HTTPS and the Node Certificate.

A new node has no default account or password. The first time you open it, ControlBird shows the setup wizard instead of the login screen.

Claim Your Node

Choose how you sign in: a local Password, OpenID Connect (Google, Microsoft, GitHub, or a custom provider), or LDAP.
Configure and verify it. With a password, you sign in as owner. With OpenID Connect, you sign in once through your provider to confirm it works. With LDAP, you connect to your directory over LDAPS or StartTLS and enter your own directory username and password; the Owner then signs in with that directory account.
Pick the time zone used for timestamps.
Optionally connect a Git repository to keep a history of your configuration off the node. You can skip this and set it up later in Config Manager.

Completing the wizard makes you the node's owner. From then on, the login screen appears as usual.

Claim it before anyone else can reach it

Whoever completes the setup wizard first becomes the owner. Finish it right after starting the container, before the node is reachable from other networks.

The ControlBird Desktop

After setup, the ControlBird desktop appears. This is your workspace for managing devices, building automations, and monitoring your system. The interface includes:

Taskbar: Quick access to all apps at the bottom of the screen
Desktop: Drag-and-drop workspace for app windows
System Tray: Status indicators and notifications

You're now ready to explore the platform. The next step covers the architecture behind ControlBird so you understand how everything fits together.