# Initial Setup

Starting from version `5.0.0-red-deer` the flecs core requires you to authenticate yourself in order to do most things. This works by creating a local user account with password. Currently it is only possible to create exactly one local super admin account.

## Initial Setup via WebApp

Open a web browser and go to `https://<device-ip>` or `https://<device-hostname>`. If this is the first time you open the WebApp you should see a browser warning about the self signed certificate of the WebApp. To continue you have to trust this certificate and add an exception.

The initial setup should begin immediately. The first step creates an auth provider which should complete on its own. For the second and currently last step you will be prompted to create a super admin user with password. You will have to remember or store your password somewhere save as you wont be able access flecs without logging in and file system access is required to reset the super admin ([#resetting-the-super-admin](#resetting-the-super-admin "mention")).

Now you can close the setup, log in with your new super admin user and continue with  [license-activation](https://docs.flecs.tech/product-docs/flecs-core/license-activation "mention").

## Resetting the Super Admin

{% hint style="info" %}
Resetting the super admin is currently only possible if you have file system access to the host system. (e.g. via ssh)
{% endhint %}

1. Stop flecs-core
   1. flecs installed via filip: `sudo systemctl stop flecs`&#x20;
   2. flecs via docker compose: use `compose down`
2. Delete the data of the auth provider which should be by default in `/var/lib/docker/volumes/flecs-000fe4ce-fence/_data/`
3. Restart flecs-core
   1. flecs installed via filip: `sudo systemctl start flecs-webapp`&#x20;
   2. flecs via docker compose: use `compose up`
4. Open the flecs WebApp which should prompt you to create a new super admin  &#x20;
