Set Nango's encryption key

Create a 32-byte key in base64:

openssl rand -base64 32

Set the same value as NANGO_ENCRYPTION_KEY on the Nango server and in the DorkOS server environment. DorkOS checks that it decodes to exactly 32 bytes. It refuses to start this route when the value is missing or malformed. DorkOS reads it when it starts, so restart DorkOS after you set or change it.

Set the server address

Set NANGO_BASE_URL to the Nango origin, such as http://localhost:3003. DorkOS rejects an invalid URL during startup.

Save the secret key

Open Settings › Connections. Under How DorkOS reaches your apps, open Add another way (if nothing is set up yet, the choices are already open) and paste the Nango secret key into the Your Nango server entry. Once it's saved, Your Nango server is listed with its state. DorkOS keeps it in the local encrypted credential store. Saving or removing the key updates the route without a restart.

Connect an account

Choose a service and complete the sign-in through your Nango server. The account appears in Connections after Nango reports it as active. It remains unavailable to agents until this route can provide immutable action versions and safe classifications.

A popular app you set up in Nango, like Gmail or Notion, shows up in Connections as that app, whatever key you gave it in Nango. If you set up the same app twice, the one you set up first keeps the app's row. The other gets its own row, named with its Nango key so you can tell them apart. Setting up another one later never moves the app's row or the accounts on it.