Local Komodo connection to local Periphery fails

[FoUStep]

In v1, the connection was easily established with a passkey. In the new v2 setup, it's not really obvious what the correct configuration (and additional missing documentation) is.

I've tried several things to keep Komodo connected to Periphery and not the other way around. Could it be that it's not generating keys?

Is there any clear instruction what to do after upgrading from v1 to v2? For other hosts, the problem was easily solved adjusting the config toml file with the public key and by removing the legacy passkey. I don't have a customized configuration and not mapped the toml folder as not all instructions require to do this.

Is there anything required to set the public key into the compose.env file?

I tried it with:

• PERIPHERY_CORE_PUBLIC_KEY (string)
• PERIPHERY_CORE_ADDRESS (set to the IP and default to core)
• Old legacy Passkeys

[FoUStep]

So I've finally gotten it to work using the following:
PERIPHERY_ONBOARDING_KEY

The upgrade guide tells you this:

The address of Komodo Core. Must be reachable from this host.
If provided, Periphery will operate in outbound mode.
Env: PERIPHERY_CORE_ADDRESS
Default: None
core_address = "<YOUR_KOMODO_CORE_ADDRESS>" # Example: demo.komo.do, ws://localhost:9120

The Server this Periphery agent should "connect as".
Systemd periphery can use the system hostname by setting connect_as = "$(hostname)".
Env: PERIPHERY_CONNECT_AS
Default: None
connect_as = "<SERVER_NAME>"

Make Onboarding Keys in Server settings.
Not needed if connecting as Server that already exists.
Env: PERIPHERY_ONBOARDING_KEY
onboarding_key = "<YOUR_ONBOARDING_KEY>"

But the proper configuration file for compose is this:
PERIHERY_SERVER_ENABLED=true

Point Periphery to Core for connection
PERIPHERY_CORE_ADDRESS=ws://:
Use the same name as KOMODO_FIRST_SERVER_NAME to connect
PERIPHERY_CONNECT_AS=${KOMODO_FIRST_SERVER_NAME}
Use the public key generated by Core.
PERIPHERY_CORE_PUBLIC_KEYS=""
PERIPHERY_ONBOARDING_KEY=''