PHP 8.4 and MariaDB 11.8

Connected to tty 1
Type <Ctrl+a q> to exit the console, <Ctrl+a Ctrl+a> to enter Ctrl+a itself
press Enter within 5 s to answer first-boot questions
Keel Linux Configuration Console KC9383 appliance services                                                    < Quit >         Web:https://[2804:710:d0:5:be24:11ff:fea4:87e9]Check page:https://[2804:710:d0:5:be24:11ff:fea4:87e9]/keel-check/Webmin:     https://[2804:710:d0:5:be24:11ff:fea4:87e9]:12321SSH/SFTP:   root@2804:710:d0:5:be24:11ff:fea4:87e9 (port 22) Keel Linux Configuration Console KC9383 appliance services                                  < Quit >       Web:https://[2804:710:d0:5:be24:11ff:fea4:87e9]Check page:https://[2804:710:d0:5:be24:11ff:fea4:87e9]/keel-check/Webmin:     https://[2804:710:d0:5:be24:11ff:fea4:87e9]:12321SSH/SFTP:   root@2804:710:d0:5:be24:11ff:fea4:87e9 (port 22)
Debian GNU/Linux 13 kc9383 tty1
kc9383 login: root
Password:
Keel Linux lnmp 19.0-trixie-amd64
IPv6 Web:  https://[2804:710:d0:5:be24:11ff:fea4:87e9]
IPv6 SSH:  root@2804:710:d0:5:be24:11ff:fea4:87e9
Welcome to kc9383, Keel Linux 19.0 (Debian 13/Trixie)
System information for Tue Nov 10 01:03:49 2026 (UTC+0000)
System load:  11.67             Memory usage:  16.2%
Processes:    36                Swap usage:    0.0%
Usage of /:   16.2% of 7.78GB   Networking not configured
This system is not initialized yet: run keel-init to set it up.
For Advanced commandline config run:    confconsole
For more info see: https://github.com/Keel-Linux/confconsole
Linux kc9383 7.0.14-12-pve #1 SMP PREEMPT_DYNAMIC PMX 7.0.14-12 (2026-08-11T11:05Z) x86_64
=== Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

Connected to tty 1
Type <Ctrl+a q> to exit the console, <Ctrl+a Ctrl+a> to enter Ctrl+a itself
press Enter within 5 s to answer first-boot questions
Keel Linux Configuration Console  KC9384 appliance services                                                                            < Quit >           Web:https://[fd00:218:88:0:3b88:327c:2b47:672a]Check page:https://[fd00:218:88:0:3b88:327c:2b47:672a]/keel-check/Webmin:     https://[fd00:218:88:0:3b88:327c:2b47:672a]:12321SSH/SFTP:   root@fd00:218:88:0:3b88:327c:2b47:672a (port 22)Web:https://10.218.88.91Check page: https://10.218.88.91/keel-check/Webmin:     https://10.218.88.91:12321SSH/SFTP:   root@10.218.88.91 (port 22)
Debian GNU/Linux 13 kc9384 tty1
kc9384 login: root
Password:
Keel Linux lnmp 19.0-trixie-amd64
IPv6 Web:  https://[2804:7f0:9880:6c3:aa32:34a0:1756:8279]
IPv6 SSH:  root@2804:7f0:9880:6c3:aa32:34a0:1756:8279
IPv4 Web:  https://10.218.88.91
IPv4 SSH:  root@10.218.88.91
Welcome to kc9384, Keel Linux 19.0 (Debian 13/Trixie)
System information for Tue Nov 10 01:08:07 2026 (UTC+0000)
System load:  13.31            Memory usage:  12.7%
Processes:    39               Swap usage:    0.0%
Usage of /:   9.7% of 8.00GB   IP address for eth0: 10.218.88.91
This system is not initialized yet: run keel-init to set it up.
For Advanced commandline config run:    confconsole
For more info see: https://github.com/Keel-Linux/confconsole
Linux kc9384 7.0.14-19-pve #1 SMP PREEMPT_DYNAMIC PMX 7.0.14-19 (2026-09-18T07:31Z) x86_64
=== Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
Root Password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
Root Password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
kc9383.pop.coop
Domain name
xxx The name this machine is reached by, with its domain,    xx for example blog.example.org. It becomes the hostname,   xx the name /etc/hosts answers for this machine, and the    xx domain a TLS certificate is requested for in             xx confconsole.xxxx Leave the field empty to keep the name the machine has.  xxxx Fully qualified domain name:x
<Apply>x
>fqdn: /etc/keel/instance.yaml already declares the name, not written
=== Keel - First boot configuration
MariaDB password
Enter the password for the MariaDB administrative
account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel - First boot configuration
MariaDB password
Enter the password for the MariaDB administrative
account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
tq
qu   x<  OK  >x

********
Keel Linux - First boot configuration
kc9384.pop.coop
Domain name
xxx The name this machine is reached by, with its domain,    xx for example blog.example.org. It becomes the hostname,   xx the name /etc/hosts answers for this machine, and the    xx domain a TLS certificate is requested for in             xx confconsole.xxxx Leave the field empty to keep the name the machine has.  xxxx Fully qualified domain name:x
<Apply>x
>fqdn: /etc/keel/instance.yaml already declares the name, not written
=== Keel - First boot configuration
MariaDB password
Enter the password for the MariaDB administrative
account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel - First boot configuration
MariaDB password
Enter the password for the MariaDB administrative
account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
tq
qu   x<  OK  >x

********
Keel - First boot configuration
MariaDB password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel - First boot configuration
MariaDB password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********>WARNING: option --ssl-verify-server-cert is disabled, because of an insecure passwordless login.
MariaDB account 'admin' set from DB_PASS (24 characters), verified on [::1]:3306
[40lnmp-check] check database ready: keel_check.boot holds the row of this host, www-data reads it
=== Keel Linux - First boot configuration
Installation mode
How this appliance is installed (decision 0028). You choose it once.
Simple: one node. Everything is on this machine, with no mesh.
Cloud simple: two nodes, a primary and a replica on a WireGuard mesh. The data follows the primary. When the
primary stops, you promote the replica by hand.
Cloud advanced: two data nodes and a witness, three sites, etcd of three. When the primary stops, the replica
takes over by itself.
Choose the same mode on every node of the set.
Simple          one node, no mesh
Cloud simple    two nodes, failover by hand
Cloud advanced  two nodes and a witness, failover by itself
<Select>

********>WARNING: option --ssl-verify-server-cert is disabled, because of an insecure passwordless login.
MariaDB account 'admin' set from DB_PASS (24 characters), verified on [::1]:3306
[40lnmp-check] check database ready: keel_check.boot holds the row of this host, www-data reads it
=== Keel Linux - First boot configuration
Installation mode
How this appliance is installed (decision 0028). You choose it once.
Simple: one node. Everything is on this machine, with no mesh.
Cloud simple: two nodes, a primary and a replica on a WireGuard mesh. The data follows the primary. When the
primary stops, you promote the replica by hand.
Cloud advanced: two data nodes and a witness, three sites, etcd of three. When the primary stops, the replica
takes over by itself.
Choose the same mode on every node of the set.
Simple          one node, no mesh
Cloud simple    two nodes, failover by hand
Cloud advanced  two nodes and a witness, failover by itself
<Select>

Simpleone node, no meshCloud simple    two nodes, failover by hand>
== Keel Linux - First boot configuration
Installation mode
<  ok  >x
/etc/keel/instance.yaml: installation.mode: cloud_simple$ keel spec apply --system-only --non-interactive --skip-network --defer-certificate --spec/etc/keel/instance.yaml2026-11-10 01:04:08 INF Generating key and certificate (cn=syncthing log.pkg=syncthing)2026-11-10 01:04:08 INF Calculated device ID(device=3DO7UCG-WHLLEOJ-HBNIVXT-PZ3I6XZ-V6FVRWF-PSOPLXT-UTZA5DA-VTDULA3 log.pkg=github)apply --system-only: /etc/inithooks.conf not read or writteninstance.hostname: unchanged (kc9383)instance.fqdn: unchanged (/etc/hosts maps kc9383 to kc9383.pop.coop)derived.monit: crowdsec not watched: crowdsec.service starts only when /etc/crowdsec/local_api_credentials.yamlexists (ConditionPathExists)derived.monit: crowdsec-lapi not watched: its process crowdsec is not watched: crowdsec.service starts only when/etc/crowdsec/local_api_credentials.yaml exists (ConditionPathExists)derived.monit: write /etc/keel/monit/keel-manifest.conf: 9 unit(s) and 8 probe(s) of lnmp (mode 0600): doneoverlays.vip: unchanged (disabled: keel-vip.service)overlays.etcd: unchanged (disabled: etcd.service)overlays.crowdsec: create /etc/crowdsec/online_api_credentials.yaml empty, which CrowdSec's unit needs and whichsays not registered yet (mode 0600): doneoverlays.crowdsec: register this machine with CrowdSec's local API; cscli writes the password to/etc/crowdsec/local_api_credentials.yaml (cscli --error machines add --auto --force): doneoverlays.crowdsec: register with CrowdSec's central API (cscli --error capi register): doneoverlays.crowdsec: register CrowdSec's firewall bouncer (cscli bouncers add) and write its key to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.local (mode 0600, never printed) and its name to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.id, mode: nftables: doneoverlays.crowdsec: enable crowdsec.service: the overlay is enabled (systemctl enable crowdsec.service): doneoverlays.crowdsec: start crowdsec.service (systemctl start crowdsec.service): doneoverlays.crowdsec: enable crowdsec-firewall-bouncer.service: the overlay is enabled (systemctl enablecrowdsec-firewall-bouncer.service): doneoverlays.crowdsec: start crowdsec-firewall-bouncer.service (systemctl start crowdsec-firewall-bouncer.service):done57%
Keel Linux - First boot configuration
Role of this node
What this node is in its set of two (cloud simple).
Primary: the first node. It makes the mesh and invites the replica with a line you copy to it.
Replica: the second node. It joins with that line, and its data follows the primary.
Primary  the first node: makes the mesh, invites
Replica  joins the primary; its data follows it
<Select>

Simpleone node, no meshCloud simple    two nodes, failover by hand>
== Keel Linux - First boot configuration
Installation mode
<  ok  >x
/etc/keel/instance.yaml: installation.mode: cloud_simple$ keel spec apply --system-only --non-interactive --skip-network --defer-certificate --spec/etc/keel/instance.yaml2026-11-10 01:08:31 INF Generating key and certificate (cn=syncthing log.pkg=syncthing)2026-11-10 01:08:31 INF Calculated device ID(device=JAOLMP5-6MCZWDW-ZQ3A2QN-SNAWWBN-SCXXM34-SF7MIAA-LRWA2T3-H6TG6Q2 log.pkg=github)apply --system-only: /etc/inithooks.conf not read or writteninstance.hostname: unchanged (kc9384)instance.fqdn: unchanged (/etc/hosts maps kc9384 to kc9384.pop.coop)derived.monit: crowdsec not watched: crowdsec.service starts only when /etc/crowdsec/local_api_credentials.yamlexists (ConditionPathExists)derived.monit: crowdsec-lapi not watched: its process crowdsec is not watched: crowdsec.service starts only when/etc/crowdsec/local_api_credentials.yaml exists (ConditionPathExists)derived.monit: write /etc/keel/monit/keel-manifest.conf: 9 unit(s) and 8 probe(s) of lnmp (mode 0600): doneoverlays.vip: unchanged (disabled: keel-vip.service)overlays.etcd: unchanged (disabled: etcd.service)overlays.crowdsec: create /etc/crowdsec/online_api_credentials.yaml empty, which CrowdSec's unit needs and whichsays not registered yet (mode 0600): doneoverlays.crowdsec: register this machine with CrowdSec's local API; cscli writes the password to/etc/crowdsec/local_api_credentials.yaml (cscli --error machines add --auto --force): doneoverlays.crowdsec: register with CrowdSec's central API (cscli --error capi register): doneoverlays.crowdsec: register CrowdSec's firewall bouncer (cscli bouncers add) and write its key to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.local (mode 0600, never printed) and its name to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.id, mode: nftables: doneoverlays.crowdsec: enable crowdsec.service: the overlay is enabled (systemctl enable crowdsec.service): doneoverlays.crowdsec: start crowdsec.service (systemctl start crowdsec.service): doneoverlays.crowdsec: enable crowdsec-firewall-bouncer.service: the overlay is enabled (systemctl enablecrowdsec-firewall-bouncer.service): doneoverlays.crowdsec: start crowdsec-firewall-bouncer.service (systemctl start crowdsec-firewall-bouncer.service):done57%
Keel Linux - First boot configuration
Role of this node
What this node is in its set of two (cloud simple).
Primary: the first node. It makes the mesh and invites the replica with a line you copy to it.
Replica: the second node. It joins with that line, and its data follows the primary.
Primary  the first node: makes the mesh, invites
Replica  joins the primary; its data follows it
<Select>

Keel Linux - First boot configuration
keel mesh create: making
the mesh...
Keel Linux - First boot configuration
Make the mesh
<  ok  >x
$ keel mesh createcreated the mesh: this node is fdfe:e01b:ed3d::1/64 on wg0, WireGuard on UDP 51820keel mesh invite prints the line that joins the next nodeconfirming the new overlayconfirmed from keel mesh createthe overlay has no peer, so nothing can cross it: keel mesh create confirmed it once the routes to the gatewaysand to the operator's session were found to still leave through the uplinkwg-quick@wg0 enabled: the overlay comes back up at bootthe network change stays; the revert is cancelledmesh: this node holds the mesh's root CA, which signs the database certificates of a cloud simple pairkeel mesh: exit 0, done>Invite a node
This node invites the replica (node 2) into its mesh. Copy the line below to the replica (node 2): paste it into its Join a mesh screen, or run it there as root. It can be used once, until 2026-11-10T02:04:42Z. The line carries the service address of the pair, shown below: this node writes it as its appliance.vip, and the replica takes it from the join. Nobody types it.
Copy this line to the replica (node 2), on one line, as it is. It is a secret: it lets one node join this mesh.
keel mesh join - <<< <invite 1>
VIP: fdfe:e01b:ed3d::ffff:1
Expires: 2026-11-10T02:04:42Z
Press Enter to go on:

Primary  the first node: makes the mesh, invitesReplica  joins the primary; its data follows it
Keel Linux - First boot configuration
Join a mesh
Paste the line that Invite a node shows on the inviting node:
keel mesh join - <<< keel2:...
The token alone (keel2:...) is accepted too. It goes to keel
on its standard input, never on a command line.
<  OK  >         <Cancel>x

<Select>           < Back >x
4             3                         2                  1            0
Keel Linux - First boot configuration
Waiting for the nodes
Waiting for the replica (node 2) to join with the line, checked
every 5 s. Back gives a menu: Paste accept line, when the join
printed one (keel mesh accept keel1a:...), or the line again.
This node: fdfe:e01b:ed3d::1/64
VIP: fdfe:e01b:ed3d::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1            0
Keel Linux - First boot configuration
Take the VIP
Waiting for the replica to pair with this node (keel vip pair on the
replica). Then this node applies its description and takes the VIP.
If the replica says it paired and nothing moves here, choose Back
and Take it now.
This node: fdfe:e01b:ed3d::1/64
Member: fdfe:e01b:ed3d::d3ff, reached
VIP: fdfe:e01b:ed3d::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1
Keel Linux - First boot configuration
Take the VIP
<  ok  >x
$ keel vip promotefdfe:e01b:ed3d::d3ff: appliedthis node holds fdfe:e01b:ed3d::ffff:1 at epoch 1, on wg0, taken by the other member of the pair; the otherpeers are told in the backgroundkeel vip: exit 0, done
Keel Linux - First boot configuration
Status of this node
<  ok  >x
$ keel vip statusvip fdfe:e01b:ed3d::ffff:1: this node's appliance.viprole: primaryepoch 1, held by <public key> at fdfe:e01b:ed3d::1carried here: yesrouted to: no peer$ keel mesh statusthis node: fdfe:e01b:ed3d::1/64 on wg0, WireGuard on UDP 51820mesh identity: 2676f71f8a4431a596cc9d9daba55e05public key: <public key>peers: 1<public key>  fdfe:e01b:ed3d::d3ff/128[2804:7f0:9880:6c3:aa32:34a0:1756:8279]:51820  handshake 19 s agopending invites: 0etcd: not on this node (installation.mode cloud_simple; etcd runs on cloud advanced members only)vip fdfe:e01b:ed3d::ffff:1: this node's appliance.viprole: primaryepoch 1, held by <public key> at fdfe:e01b:ed3d::1carried here: yesrouted to: no peer$ keel database statuspair: VIP fdfe:e01b:ed3d::ffff:1; role here primary
other member: fdfe:e01b:ed3d::d3ff (<public key>)the primary's address: fdfe:e01b:ed3d::1dump: none yetserver: primary (mariadb --batch --skip-column-names --execute SELECT Host FROM mysql.user WHERE Repl_slave_priv= 'Y': replication is granted from fdfe:e01b:ed3d::d3ff)read_only: truesemi-synchronous: master ON, slave OFF, 0 replica(s) acknowledging, 0 commits acknowledged, 0 not78%>keelfirstboot cloud: Keel Cloud is not available yet: no key is asked, and this node runs standalone. It is offered once /etc/keel/cloud-endpoint names the service.
=== Keel Linux - First boot configuration
System Notifications and Critical Security Alerts
Enable local system notifications (root@localhost) to be
forwarded to your regular inbox. Notifications include
security updates and system messages.
Email:
<Enable>        < Skip >x

wg-quick@wg0 enabled: the overlay comes back up at boot
the network change stays; the revert is cancelled
joined the mesh: this node is fdfe:e01b:ed3d::d3ff/64 on wg0
peer: <public key> at fdfe:e01b:ed3d::1, through [2804:710:d0:5:be24:11ff:fea4:87e9]:51820
the mesh is up with 2 nodes; etcd starts when a third node joins, because 2 etcd members cannot lose one and keep a majority
vip: fdfe:e01b:ed3d::ffff:1, proposed by the inviter for the pair (appliance.vip on both nodes; keel mesh status --json gives it)
Press Enter to go on:
== Keel Linux - First boot configuration
< Yes >< No  >x
Becoming a replica REPLACES the data on this node with a copy of the primary at [fdfe:e01b:ed3d::1].If this server holds any database that is not its own, keel refuses and this console asks once more, namingthem; a Yes there drops them and cannot be undone. Move anything you need elsewhere first.This screen configures THIS node only. It does not create replicas, does not change any other machine, andcannot know what the others are doing. It changes the database server and leaves the network and the TLScertificate alone.Go on and make this node a replica?
Keel Linux - First boot configuration
Pair with the primary
<  ok  >x
$ keel vip pair fdfe:e01b:ed3d::1fdfe:e01b:ed3d::ffff:1 is the VIP of <public key> and<public key>, signed by bothkeel vip: exit 0, done
Keel Linux - First boot configuration
Pair with the primary
Paired. Waiting for the primary to take the VIP: its screen does it
once this node has paired.
This node: fdfe:e01b:ed3d::d3ff/64
Member: fdfe:e01b:ed3d::1, reached
VIP: fdfe:e01b:ed3d::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1            0>
== Keel Linux - First boot configuration
Pair with the primary
<  ok  >x
/etc/keel/instance.yaml: database.server.role: replica$ keel spec apply --system-only --non-interactive --skip-network --defer-certificate --spec/etc/keel/instance.yamlapply --system-only: /etc/inithooks.conf not read or writteninstance.hostname: unchanged (kc9384)instance.fqdn: unchanged (/etc/hosts maps kc9384 to kc9384.pop.coop)database.server: make or renew the database certificate for fdfe:e01b:ed3d::d3ff and fdfe:e01b:ed3d::ffff:1,signed by the mesh's root CA (here, or asked of its holder over the members' channel), under the engine's TLSdirectory (etc/mysql/keel-tls or etc/postgresql/keel-tls): donedatabase.server: write /etc/sysctl.d/90-keel-database.conf: both nodes bind the VIP (mode 0644): donedatabase.server: let the server bind the VIP before it carries it (sysctl -q -w net.ipv6.ip_nonlocal_bind=1):donedatabase.server: write /etc/mysql/mariadb.conf.d/99-keel-database.cnf: a paired node, server id 1501302975,binary log, GTID strict, semi-synchronous replication, TLS, the VIP fdfe:e01b:ed3d::ffff:1 bound (mode 0644):donedatabase.server: restart the server, which is the only way these take effect (systemctl restart mariadb): donedatabase.server.replication.allowed_from: authorize replication from fdfe:e01b:ed3d::1 with the certificate/CN=keel-fdfe-e01b-ed3d--1 mariadb of the mesh's root, outside the binary log (runuser -u mysql -- mariadb--batch, 5 statement(s) on standard input): donedatabase.server.role: the role is the VIP's: replica here (epoch known, held at fdfe:e01b:ed3d::1); the declaredreplica is the installation's (0020)database.server.role: make the server follow the pair's VIP (keel database follow): the holder writable, theother node read only and replicating from the holder over TLS, an old primary rejoined by GTID when it holdsnothing the holder lacks: donederived.monit: keel-vip not watched: keel-vip.service starts only when /var/lib/keel/etcd/cluster.json exists(ConditionPathExists)derived.monit: unchanged (/etc/keel/monit/keel-manifest.conf, 10 unit(s) and 9 probe(s) of lnmp, not included)overlays.etcd: unchanged (disabled: etcd.service)overlays.crowdsec: unchanged (enabled: crowdsec.service, crowdsec-firewall-bouncer.service)overlays.vip: enable keel-vip.service: the overlay is enabled (systemctl enable keel-vip.service): done54%
Keel Linux - First boot configuration
Status of this node
<  ok  >x
$ keel vip statusvip fdfe:e01b:ed3d::ffff:1: this node's appliance.viprole: replicaepoch 1, held by <public key> at fdfe:e01b:ed3d::1carried here: norouted to: <public key>$ keel mesh statusthis node: fdfe:e01b:ed3d::d3ff/64 on wg0, WireGuard on UDP 51820mesh identity: 2676f71f8a4431a596cc9d9daba55e05public key: <public key>peers: 1<public key>  fdfe:e01b:ed3d::1/128  [2804:710:d0:5:be24:11ff:fea4:87e9]:51820handshake 39 s agopending invites: 0etcd: not on this node (installation.mode cloud_simple; etcd runs on cloud advanced members only)vip fdfe:e01b:ed3d::ffff:1: this node's appliance.viprole: replicaepoch 1, held by <public key> at fdfe:e01b:ed3d::1carried here: norouted to: <public key>$ keel database statuspair: VIP fdfe:e01b:ed3d::ffff:1; role here replicaother member: fdfe:e01b:ed3d::1 (<public key>)the primary's address: fdfe:e01b:ed3d::1dump: none yetserver: replica (mariadb --batch --execute SHOW REPLICA STATUS\G)read_only: truesemi-synchronous: master ON, slave ON, 0 replica(s) acknowledging, 0 commits acknowledged, 0 notreplicating from: [fdfe:e01b:ed3d::1]:3306; IO Yes, SQL Yes; lag 0; TLS Yes; GTID IO position80%
>keelfirstboot cloud: Keel Cloud is not available yet: no key is asked, and this node runs standalone. It is offered once /etc/keel/cloud-endpoint names the service.
=== Keel Linux - First boot configuration
System Notifications and Critical Security Alerts
Enable local system notifications (root@localhost) to be
forwarded to your regular inbox. Notifications include
security updates and system messages.
Email:
<Enable>        < Skip >x

Connected to tty 1
Type <Ctrl+a q> to exit the console, <Ctrl+a Ctrl+a> to enter Ctrl+a itself
press Enter within 5 s to answer first-boot questions
Keel Linux Configuration Console KC9385 appliance services                                                    < Quit >         Web:https://[2804:710:d0:5:be24:11ff:fe42:c0f]Check page:https://[2804:710:d0:5:be24:11ff:fe42:c0f]/keel-check/Webmin:     https://[2804:710:d0:5:be24:11ff:fe42:c0f]:12321SSH/SFTP:   root@2804:710:d0:5:be24:11ff:fe42:c0f (port 22) Keel Linux Configuration Console KC9385 appliance services                                  < Quit >       Web:https://[2804:710:d0:5:be24:11ff:fe42:c0f]Check page:https://[2804:710:d0:5:be24:11ff:fe42:c0f]/keel-check/Webmin:     https://[2804:710:d0:5:be24:11ff:fe42:c0f]:12321SSH/SFTP:   root@2804:710:d0:5:be24:11ff:fe42:c0f (port 22)
Debian GNU/Linux 13 kc9385 tty1
kc9385 login: root
Password:
Keel Linux lnmp 19.0-trixie-amd64
IPv6 Web:  https://[2804:710:d0:5:be24:11ff:fe42:c0f]
IPv6 SSH:  root@2804:710:d0:5:be24:11ff:fe42:c0f
Welcome to kc9385, Keel Linux 19.0 (Debian 13/Trixie)
System information for Tue Nov 10 01:25:58 2026 (UTC+0000)
System load:  8.26              Memory usage:  16.2%
Processes:    36                Swap usage:    0.0%
Usage of /:   16.2% of 7.78GB   Networking not configured
This system is not initialized yet: run keel-init to set it up.
For Advanced commandline config run:    confconsole
For more info see: https://github.com/Keel-Linux/confconsole
Linux kc9385 7.0.14-12-pve #1 SMP PREEMPT_DYNAMIC PMX 7.0.14-12 (2026-08-11T11:05Z) x86_64
=== Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

Connected to tty 1
Type <Ctrl+a q> to exit the console, <Ctrl+a Ctrl+a> to enter Ctrl+a itself
press Enter within 5 s to answer first-boot questions
Keel KC9386 appliance services                                                           < Quit >      Web:https://[fd00:218:88:0:38f7:cb98:9c7b:c658]Check page:https://[fd00:218:88:0:38f7:cb98:9c7b:c658]/keel-check/Webmin:     https://[fd00:218:88:0:38f7:cb98:9c7b:c658]:12321SSH/SFTP:   root@fd00:218:88:0:38f7:cb98:9c7b:c658 (port 22)Web:https://10.218.88.95Check page: https://10.218.88.95/keel-check/Webmin:     https://10.218.88.95:12321SSH/SFTP:   root@10.218.88.95 (port 22) Keel Linux Configuration Console KC9386 appliance services                                            < Quit >    Web:https://[fd00:218:88:0:38f7:cb98:9c7b:c658]Check page:https://[fd00:218:88:0:38f7:cb98:9c7b:c658]/keel-check/Webmin:     https://[fd00:218:88:0:38f7:cb98:9c7b:c658]:12321SSH/SFTP:   root@fd00:218:88:0:38f7:cb98:9c7b:c658 (port 22)Web:https://10.218.88.95Check page: https://10.218.88.95/keel-check/Webmin:     https://10.218.88.95:12321SSH/SFTP:   root@10.218.88.95 (port 22)
Debian GNU/Linux 13 kc9386 tty1
kc9386 login: root
Password:
Keel Linux lnmp 19.0-trixie-amd64
IPv6 Web:  https://[2804:7f0:9880:6c3:dafd:796b:8898:aaf4]
IPv6 SSH:  root@2804:7f0:9880:6c3:dafd:796b:8898:aaf4
IPv4 Web:  https://10.218.88.95
IPv4 SSH:  root@10.218.88.95
Welcome to kc9386, Keel Linux 19.0 (Debian 13/Trixie)
System information for Tue Nov 10 01:29:17 2026 (UTC+0000)
System load:  7.41             Memory usage:  12.7%
Processes:    39               Swap usage:    0.0%
Usage of /:   9.7% of 8.00GB   IP address for eth0: 10.218.88.95
This system is not initialized yet: run keel-init to set it up.
For Advanced commandline config run:    confconsole
For more info see: https://github.com/Keel-Linux/confconsole
Linux kc9386 7.0.14-19-pve #1 SMP PREEMPT_DYNAMIC PMX 7.0.14-19 (2026-09-18T07:31Z) x86_64
=== Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

Connected to tty 1
Type <Ctrl+a q> to exit the console, <Ctrl+a Ctrl+a> to enter Ctrl+a itself
press Enter within 5 s to answer first-boot questions
Keel Linux Configuration Console KC9387 appliance services                                                    < Quit >           Webmin:     https://[2804:710:d0:5:be24:11ff:fe50:e481]:12321SSH/SFTP:   root@2804:710:d0:5:be24:11ff:fe50:e481 (port 22) Keel Linux Configuration Console KC9387 appliance services                                  < Quit >         Webmin:     https://[2804:710:d0:5:be24:11ff:fe50:e481]:12321SSH/SFTP:   root@2804:710:d0:5:be24:11ff:fe50:e481 (port 22)
Debian GNU/Linux 13 kc9387 tty1
kc9387 login: root
Password:
Keel Linux core 19.0-trixie-amd64
IPv6 SSH:  root@2804:710:d0:5:be24:11ff:fe50:e481
Welcome to kc9387, Keel Linux 19.0 (Debian 13/Trixie)
System information for Tue Nov 10 01:31:31 2026 (UTC+0000)
System load:  8.65             Memory usage:  9.0%
Processes:    29               Swap usage:    0.0%
Usage of /:   9.9% of 7.78GB   Networking not configured
This system is not initialized yet: run keel-init to set it up.
For Advanced commandline config run:    confconsole
For more info see: https://github.com/Keel-Linux/confconsole
Linux kc9387 7.0.14-12-pve #1 SMP PREEMPT_DYNAMIC PMX 7.0.14-12 (2026-08-11T11:05Z) x86_64
=== Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel Linux - First boot configuration
Root Password
Please enter new password for the root account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
Root Password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
Root Password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
Root Password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel Linux - First boot configuration
kc9385.pop.coop
Domain name
xxx The name this machine is reached by, with its domain,    xx for example blog.example.org. It becomes the hostname,   xx the name /etc/hosts answers for this machine, and the    xx domain a TLS certificate is requested for in             xx confconsole.xxxx Leave the field empty to keep the name the machine has.  xxxx Fully qualified domain name:x
<Apply>x
>fqdn: /etc/keel/instance.yaml already declares the name, not written
=== Keel - First boot configuration
MariaDB password
Enter the password for the MariaDB administrative
account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel - First boot configuration
MariaDB password
Enter the password for the MariaDB administrative
account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
tq
qu   x<  OK  >x

********
Keel Linux - First boot configuration
kc9386.pop.coop
Domain name
xxx The name this machine is reached by, with its domain,    xx for example blog.example.org. It becomes the hostname,   xx the name /etc/hosts answers for this machine, and the    xx domain a TLS certificate is requested for in             xx confconsole.xxxx Leave the field empty to keep the name the machine has.  xxxx Fully qualified domain name:x
<Apply>x
>fqdn: /etc/keel/instance.yaml already declares the name, not written
=== Keel - First boot configuration
MariaDB password
Enter the password for the MariaDB administrative
account.
Choose how to set this password:
Generate  A strong random password (recommended)
Manual    Type my own password
<  OK  >Generate  A strong random password (recommended)Manual    Type my own password
Keel - First boot configuration
MariaDB password
Enter the password for the MariaDB administrative
account.
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
tq
qu   x<  OK  >x

********
Keel Linux - First boot configuration
kc9387.pop.coop
Domain name
xxx The name this machine is reached by, with its domain,    xx for example blog.example.org. It becomes the hostname,   xx the name /etc/hosts answers for this machine, and the    xx domain a TLS certificate is requested for in             xx confconsole.xxxx Leave the field empty to keep the name the machine has.  xxxx Fully qualified domain name:x
<Apply>x
>fqdn: /etc/keel/instance.yaml already declares the name, not written
=== Keel Linux - First boot configuration
Installation mode
How this appliance is installed (decision 0028). You choose it once.
Simple: one node. Everything is on this machine, with no mesh.
Cloud simple: two nodes, a primary and a replica on a WireGuard mesh. The data follows the primary. When the
primary stops, you promote the replica by hand.
Cloud advanced: two data nodes and a witness, three sites, etcd of three. When the primary stops, the replica
takes over by itself.
Choose the same mode on every node of the set.
Simple          one node, no mesh
Cloud simple    two nodes, failover by hand
Cloud advanced  two nodes and a witness, failover by itself
<Select>

********
Keel - First boot configuration
MariaDB password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

********
Keel - First boot configuration
MariaDB password
Confirm password
Password Requirements
- must be at least 8 characters long
- must contain characters from at least 3 of the
following categories: uppercase, lowercase, numbers,
symbols
<  OK  >x

Simpleone node, no meshCloud simple    two nodes, failover by handCloud simple    two nodes, failover by handCloud advanced  two nodes and a witness, failover by itself>
== Keel Linux - First boot configuration
Installation mode
<  ok  >x
/etc/keel/instance.yaml: installation.mode: cloud_advanced$ keel spec apply --system-only --non-interactive --skip-network --defer-certificate --spec/etc/keel/instance.yamlapply --system-only: /etc/inithooks.conf not read or writteninstance.hostname: unchanged (kc9387)instance.fqdn: unchanged (/etc/hosts maps kc9387 to kc9387.pop.coop)derived.monit: crowdsec not watched: crowdsec.service starts only when /etc/crowdsec/local_api_credentials.yamlexists (ConditionPathExists)derived.monit: crowdsec-lapi not watched: its process crowdsec is not watched: crowdsec.service starts only when/etc/crowdsec/local_api_credentials.yaml exists (ConditionPathExists)derived.monit: write /etc/keel/monit/keel-manifest.conf: 5 unit(s) and 4 probe(s) of core (mode 0600): doneoverlays.vip: unchanged (disabled: keel-vip.service)overlays.etcd: etcd waits for its cluster: it forms at the third cloud advanced member's join, or with keel meshetcd form; nothing is started until thenoverlays.crowdsec: create /etc/crowdsec/online_api_credentials.yaml empty, which CrowdSec's unit needs and whichsays not registered yet (mode 0600): doneoverlays.crowdsec: register this machine with CrowdSec's local API; cscli writes the password to/etc/crowdsec/local_api_credentials.yaml (cscli --error machines add --auto --force): doneoverlays.crowdsec: register with CrowdSec's central API (cscli --error capi register): doneoverlays.crowdsec: register CrowdSec's firewall bouncer (cscli bouncers add) and write its key to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.local (mode 0600, never printed) and its name to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.id, mode: nftables: doneoverlays.crowdsec: enable crowdsec.service: the overlay is enabled (systemctl enable crowdsec.service): doneoverlays.crowdsec: start crowdsec.service (systemctl start crowdsec.service): doneoverlays.crowdsec: enable crowdsec-firewall-bouncer.service: the overlay is enabled (systemctl enablecrowdsec-firewall-bouncer.service): doneoverlays.crowdsec: start crowdsec-firewall-bouncer.service (systemctl start crowdsec-firewall-bouncer.service):doneapply --system-only: 9 change(s), 0 failed94%
Keel Linux - First boot configuration
Role of this node
What this node is in its set of three (cloud advanced).
Primary: the first node. It makes the mesh and invites the replica, then the witness, each with a line you copy
to it.
Replica: the second node. It joins with the first line, and its data follows the primary.
Witness: the third node, Keel Core on a third site. It joins with the second line and gives etcd its third vote.
It holds no data.
Primary  the first node: makes the mesh, invites
Replica  joins the primary; its data follows it
Witness  Keel Core on a third site: a vote, no data
<Select>

********>WARNING: option --ssl-verify-server-cert is disabled, because of an insecure passwordless login.
MariaDB account 'admin' set from DB_PASS (24 characters), verified on [::1]:3306
[40lnmp-check] check database ready: keel_check.boot holds the row of this host, www-data reads it
=== Keel Linux - First boot configuration
Installation mode
How this appliance is installed (decision 0028). You choose it once.
Simple: one node. Everything is on this machine, with no mesh.
Cloud simple: two nodes, a primary and a replica on a WireGuard mesh. The data follows the primary. When the
primary stops, you promote the replica by hand.
Cloud advanced: two data nodes and a witness, three sites, etcd of three. When the primary stops, the replica
takes over by itself.
Choose the same mode on every node of the set.
Simple          one node, no mesh
Cloud simple    two nodes, failover by hand
Cloud advanced  two nodes and a witness, failover by itself
<Select>

********>WARNING: option --ssl-verify-server-cert is disabled, because of an insecure passwordless login.
MariaDB account 'admin' set from DB_PASS (24 characters), verified on [::1]:3306
[40lnmp-check] check database ready: keel_check.boot holds the row of this host, www-data reads it
=== Keel Linux - First boot configuration
Installation mode
How this appliance is installed (decision 0028). You choose it once.
Simple: one node. Everything is on this machine, with no mesh.
Cloud simple: two nodes, a primary and a replica on a WireGuard mesh. The data follows the primary. When the
primary stops, you promote the replica by hand.
Cloud advanced: two data nodes and a witness, three sites, etcd of three. When the primary stops, the replica
takes over by itself.
Choose the same mode on every node of the set.
Simple          one node, no mesh
Cloud simple    two nodes, failover by hand
Cloud advanced  two nodes and a witness, failover by itself
<Select>

Primary  the first node: makes the mesh, invitesWitness  Keel Core on a third site: a vote, no data
Keel Linux - First boot configuration
Join a mesh
Paste the line that Invite a node shows on the inviting node:
keel mesh join - <<< keel2:...
The token alone (keel2:...) is accepted too. It goes to keel
on its standard input, never on a command line.
<  OK  >         <Cancel>x

Simpleone node, no meshCloud simple    two nodes, failover by handCloud simple    two nodes, failover by handCloud advanced  two nodes and a witness, failover by itself>
== Keel Linux - First boot configuration
Installation mode
<  ok  >x
/etc/keel/instance.yaml: installation.mode: cloud_advanced$ keel spec apply --system-only --non-interactive --skip-network --defer-certificate --spec/etc/keel/instance.yaml2026-11-10 01:26:17 INF Generating key and certificate (cn=syncthing log.pkg=syncthing)2026-11-10 01:26:17 INF Calculated device ID(device=FMRNKO5-Z2QHW6V-6WLHZKK-M5XWULX-XUKRH7F-EIGP5F5-H3NVRTP-LVYQCAT log.pkg=github)apply --system-only: /etc/inithooks.conf not read or writteninstance.hostname: unchanged (kc9385)instance.fqdn: unchanged (/etc/hosts maps kc9385 to kc9385.pop.coop)derived.monit: crowdsec not watched: crowdsec.service starts only when /etc/crowdsec/local_api_credentials.yamlexists (ConditionPathExists)derived.monit: crowdsec-lapi not watched: its process crowdsec is not watched: crowdsec.service starts only when/etc/crowdsec/local_api_credentials.yaml exists (ConditionPathExists)derived.monit: write /etc/keel/monit/keel-manifest.conf: 10 unit(s) and 9 probe(s) of lnmp (mode 0600): doneoverlays.vip: unchanged (disabled: keel-vip.service)overlays.etcd: etcd waits for its cluster: it forms at the third cloud advanced member's join, or with keel meshetcd form; nothing is started until thenoverlays.crowdsec: create /etc/crowdsec/online_api_credentials.yaml empty, which CrowdSec's unit needs and whichsays not registered yet (mode 0600): doneoverlays.crowdsec: register this machine with CrowdSec's local API; cscli writes the password to/etc/crowdsec/local_api_credentials.yaml (cscli --error machines add --auto --force): doneoverlays.crowdsec: register with CrowdSec's central API (cscli --error capi register): doneoverlays.crowdsec: register CrowdSec's firewall bouncer (cscli bouncers add) and write its key to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.local (mode 0600, never printed) and its name to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.id, mode: nftables: doneoverlays.crowdsec: enable crowdsec.service: the overlay is enabled (systemctl enable crowdsec.service): doneoverlays.crowdsec: start crowdsec.service (systemctl start crowdsec.service): doneoverlays.crowdsec: enable crowdsec-firewall-bouncer.service: the overlay is enabled (systemctl enablecrowdsec-firewall-bouncer.service): doneoverlays.crowdsec: start crowdsec-firewall-bouncer.service (systemctl start crowdsec-firewall-bouncer.service):56%
Keel Linux - First boot configuration
Role of this node
What this node is in its set of three (cloud advanced).
Primary: the first node. It makes the mesh and invites the replica, then the witness, each with a line you copy
to it.
Replica: the second node. It joins with the first line, and its data follows the primary.
Witness: the third node, Keel Core on a third site. It joins with the second line and gives etcd its third vote.
It holds no data.
Primary  the first node: makes the mesh, invites
Replica  joins the primary; its data follows it
<Select>

Simpleone node, no meshCloud simple    two nodes, failover by handCloud simple    two nodes, failover by handCloud advanced  two nodes and a witness, failover by itself>
== Keel Linux - First boot configuration
Installation mode
<  ok  >x
/etc/keel/instance.yaml: installation.mode: cloud_advanced$ keel spec apply --system-only --non-interactive --skip-network --defer-certificate --spec/etc/keel/instance.yaml2026-11-10 01:29:36 INF Generating key and certificate (cn=syncthing log.pkg=syncthing)2026-11-10 01:29:36 INF Calculated device ID(device=P5WV7Q3-VOG3FYY-3P64P36-H7EERHJ-CLRH6UC-PNJQKNS-IOXGTZI-UKZ2HQN log.pkg=github)apply --system-only: /etc/inithooks.conf not read or writteninstance.hostname: unchanged (kc9386)instance.fqdn: unchanged (/etc/hosts maps kc9386 to kc9386.pop.coop)derived.monit: crowdsec not watched: crowdsec.service starts only when /etc/crowdsec/local_api_credentials.yamlexists (ConditionPathExists)derived.monit: crowdsec-lapi not watched: its process crowdsec is not watched: crowdsec.service starts only when/etc/crowdsec/local_api_credentials.yaml exists (ConditionPathExists)derived.monit: write /etc/keel/monit/keel-manifest.conf: 10 unit(s) and 9 probe(s) of lnmp (mode 0600): doneoverlays.vip: unchanged (disabled: keel-vip.service)overlays.etcd: etcd waits for its cluster: it forms at the third cloud advanced member's join, or with keel meshetcd form; nothing is started until thenoverlays.crowdsec: create /etc/crowdsec/online_api_credentials.yaml empty, which CrowdSec's unit needs and whichsays not registered yet (mode 0600): doneoverlays.crowdsec: register this machine with CrowdSec's local API; cscli writes the password to/etc/crowdsec/local_api_credentials.yaml (cscli --error machines add --auto --force): doneoverlays.crowdsec: register with CrowdSec's central API (cscli --error capi register): doneoverlays.crowdsec: register CrowdSec's firewall bouncer (cscli bouncers add) and write its key to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.local (mode 0600, never printed) and its name to/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.id, mode: nftables: doneoverlays.crowdsec: enable crowdsec.service: the overlay is enabled (systemctl enable crowdsec.service): doneoverlays.crowdsec: start crowdsec.service (systemctl start crowdsec.service): doneoverlays.crowdsec: enable crowdsec-firewall-bouncer.service: the overlay is enabled (systemctl enablecrowdsec-firewall-bouncer.service): doneoverlays.crowdsec: start crowdsec-firewall-bouncer.service (systemctl start crowdsec-firewall-bouncer.service):56%
Keel Linux - First boot configuration
Role of this node
What this node is in its set of three (cloud advanced).
Primary: the first node. It makes the mesh and invites the replica, then the witness, each with a line you copy
to it.
Replica: the second node. It joins with the first line, and its data follows the primary.
Witness: the third node, Keel Core on a third site. It joins with the second line and gives etcd its third vote.
It holds no data.
Primary  the first node: makes the mesh, invites
Replica  joins the primary; its data follows it
<Select>

<invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1>z<invite 1>ze<invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2>F<invite 2>FA<invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1>m<invite 2><invite 1>m9<invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 2><invite 1><invite 2><invite 1>m9<invite 1><invite 1>m9<invite 1><invite 1>m9<invite 1><invite 1>m9<invite 1><invite 1>m9<invite 1><invite 1>m9<invite 1><invite 1>m9<invite 1><invite 1>m9<invite 1><invite 1>m9<invite 1>nQ<invite 1>m9<invite 1>Q<invite 1>m9<invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2>m9<invite 1><invite 2>m9<invite 1><invite 2>m9<invite 1><invite 2>m9<invite 1><invite 2>m9<invite 1><invite 2>m9<invite 1><invite 2>m9<invite 1><invite 2>m9<invite 1><invite 2>m9<invite 1><invite 2>m9<invite 1><invite 2>m9<invite 1><invite 2>9<invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 1><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 1><invite 2><invite 1><invite 2><invite 2><invite 2>D<invite 2>D_<invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2><invite 2>>Join a mesh
Join a mesh: keel joins this node to the mesh. When the inviting node cannot be reached, keel prints a line keel mesh accept keel1a:... and waits: run that line on the inviting node, or paste it into its Paste accept line screen.
endpoint 2804:710:d0:5:be24:11ff:fe50:e481, found on eth0 (--endpoint overrides it)
confirming over the overlay
confirmed from the inviter's answer over the overlay (invite ca7e396d0f3cde83)
the overlay was tested: the inviter's answer over the overlay (invite ca7e396d0f3cde83) arrived at fdfb:4991:29d::26f4 on wg0, from fdfb:4991:29d::1
wg-quick@wg0 enabled: the overlay comes back up at boot
the network change stays; the revert is cancelled
joined the mesh: this node is fdfb:4991:29d::26f4/64 on wg0
peer: <public key> at fdfb:4991:29d::1, through [2804:710:d0:5:be24:11ff:fe42:c0f]:51820
the mesh has 3 nodes: this node has them all as peers, and the inviter announces this node to the 1 other(s) over the overlay (one offline now learns of it at its next keel mesh sync)
etcd: this node forms with 2 other member(s)
vip: fdfb:4991:29d::ffff:1, proposed by the inviter for the pair (appliance.vip on both nodes; keel mesh status --json gives it)
Press Enter to go on:
== Keel Linux - First boot configuration
Status of this node
<  ok  >x
$ keel mesh statusthis node: fdfb:4991:29d::26f4/64 on wg0, WireGuard on UDP 51820mesh identity: 08ae4640eba45725377f58b1d9364bfdpublic key: <public key>peers: 2<public key>  fdfb:4991:29d::1/128  [2804:710:d0:5:be24:11ff:fe42:c0f]:51820handshake 12 s ago<public key>  fdfb:4991:29d::7cb4/128[2804:7f0:9880:6c3:dafd:796b:8898:aaf4]:51820  handshake 0 s agopending invites: 0etcd: 3 voter(s), 0 learner(s)keel-fdfb-4991-29d--7cb4  fdfb:4991:29d::7cb4  voter  healthykeel-fdfb-4991-29d--26f4  fdfb:4991:29d::26f4  voter  healthykeel-fdfb-4991-29d--1  fdfb:4991:29d::1  voter  healthyleader: keel-fdfb-4991-29d--1etcd: this member's certificate expires 2026-12-10 01:32 UTCvip: none (this node declares no appliance.vip and routes no other pair's)>keelfirstboot cloud: Keel Cloud is not available yet: no key is asked, and this node runs standalone. It is offered once /etc/keel/cloud-endpoint names the service.
=== Keel Linux - First boot configuration
System Notifications and Critical Security Alerts
Enable local system notifications (root@localhost) to be
forwarded to your regular inbox. Notifications include
security updates and system messages.
Email:
<Enable>        < Skip >x

Keel Linux - First boot configuration
keel mesh create: making
the mesh...
Keel Linux - First boot configuration
Make the mesh
<  ok  >x
$ keel mesh createcreated the mesh: this node is fdfb:4991:29d::1/64 on wg0, WireGuard on UDP 51820keel mesh invite prints the line that joins the next nodeconfirming the new overlayconfirmed from keel mesh createthe overlay has no peer, so nothing can cross it: keel mesh create confirmed it once the routes to the gatewaysand to the operator's session were found to still leave through the uplinkwg-quick@wg0 enabled: the overlay comes back up at bootthe network change stays; the revert is cancelledetcd: this node holds the mesh's root CA; etcd forms when the third cloud advanced member joinskeel mesh: exit 0, done>Invite a node
This node invites the replica (node 2) into its mesh. Copy the line below to the replica (node 2): paste it into its Join a mesh screen, or run it there as root. It can be used once, until 2026-11-10T02:26:56Z. The line carries the service address of the pair, shown below: this node writes it as its appliance.vip, and the replica takes it from the join. Nobody types it.
Copy this line to the replica (node 2), on one line, as it is. It is a secret: it lets one node join this mesh.
keel mesh join - <<< <invite 1>
VIP: fdfb:4991:29d::ffff:1
Expires: 2026-11-10T02:26:56Z
Press Enter to go on:

Primary  the first node: makes the mesh, invitesReplica  joins the primary; its data follows it
Keel Linux - First boot configuration
Join a mesh
Paste the line that Invite a node shows on the inviting node:
keel mesh join - <<< keel2:...
The token alone (keel2:...) is accepted too. It goes to keel
on its standard input, never on a command line.
<  OK  >         <Cancel>x

4             3                         2                  1            0
Keel Linux - First boot configuration
Waiting for the nodes
Waiting for the replica (node 2) to join with the line, checked
every 5 s. Back gives a menu: Paste accept line, when the join
printed one (keel mesh accept keel1a:...), or the line again.
This node: fdfb:4991:29d::1/64
etcd: not_formed, voters 0
VIP: fdfb:4991:29d::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1            0
Keel Linux - First boot configuration
Waiting for the nodes
Waiting for the replica (node 2) to join with the line, checked
every 5 s. Back gives a menu: Paste accept line, when the join
printed one (keel mesh accept keel1a:...), or the line again.
This node: fdfb:4991:29d::1/64
etcd: not_formed, voters 0
VIP: fdfb:4991:29d::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1            0
Keel Linux - First boot configuration
Waiting for the nodes
Waiting for the replica (node 2) to join with the line, checked
every 5 s. Back gives a menu: Paste accept line, when the join
printed one (keel mesh accept keel1a:...), or the line again.
This node: fdfb:4991:29d::1/64
etcd: not_formed, voters 0
VIP: fdfb:4991:29d::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1            0>Invite a node
This node invites the witness (node 3, Keel Core) into its mesh. Copy the line below to the witness (node 3, Keel Core): paste it into its Join a mesh screen, or run it there as root. It can be used once, until 2026-11-10T02:30:06Z. The line carries the service address of the pair, shown below: this node writes it as its appliance.vip, and the replica takes it from the join. Nobody types it.
Copy this line to the witness (node 3, Keel Core), on one line, as it is. It is a secret: it lets one node join this mesh.
keel mesh join - <<< <invite 1><invite 2><invite 1><invite 1><invite 2><invite 1>
VIP: fdfb:4991:29d::ffff:1
Expires: 2026-11-10T02:30:06Z
Press Enter to go on:

etcd: not_formed, voters 0
VIP: fdfb:4991:29d::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1            0
Keel Linux - First boot configuration
< Yes >< No  >x
Becoming a replica REPLACES the data on this node with a copy of the primary at [fdfb:4991:29d::1].If this server holds any database that is not its own, keel refuses and this console asks once more, namingthem; a Yes there drops them and cannot be undone. Move anything you need elsewhere first.This screen configures THIS node only. It does not create replicas, does not change any other machine, andcannot know what the others are doing. It changes the database server and leaves the network and the TLScertificate alone.Go on and make this node a replica?
Keel Linux - First boot configuration
Pair with the primary
<  ok  >x
$ keel vip pair fdfb:4991:29d::1fdfb:4991:29d::ffff:1 is the VIP of <public key> and<public key>, signed by bothetcd: fdfb:4991:29d::ffff:1: its pair's role is grantedkeel vip: exit 0, done
Keel Linux - First boot configuration
Pair with the primary
Paired. Waiting for the primary to take the VIP: its screen does it
once this node has paired.
This node: fdfb:4991:29d::7cb4/64
Member: fdfb:4991:29d::1, reached
Member: fdfb:4991:29d::26f4, reached
etcd: formed, voters 3
VIP: fdfb:4991:29d::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1>
== Keel Linux - First boot configuration
Pair with the primary
<  ok  >x
/etc/keel/instance.yaml: database.server.role: replica$ keel spec apply --system-only --non-interactive --skip-network --defer-certificate --spec/etc/keel/instance.yamlapply --system-only: /etc/inithooks.conf not read or writteninstance.hostname: unchanged (kc9386)instance.fqdn: unchanged (/etc/hosts maps kc9386 to kc9386.pop.coop)database.server: make or renew the database certificate for fdfb:4991:29d::7cb4 and fdfb:4991:29d::ffff:1,signed by the mesh's root CA (here, or asked of its holder over the members' channel), under the engine's TLSdirectory (etc/mysql/keel-tls or etc/postgresql/keel-tls): donedatabase.server: write /etc/sysctl.d/90-keel-database.conf: both nodes bind the VIP (mode 0644): donedatabase.server: let the server bind the VIP before it carries it (sysctl -q -w net.ipv6.ip_nonlocal_bind=1):donedatabase.server: write /etc/mysql/mariadb.conf.d/99-keel-database.cnf: a paired node, server id 392227899,binary log, GTID strict, semi-synchronous replication, TLS, the VIP fdfb:4991:29d::ffff:1 bound (mode 0644):donedatabase.server: restart the server, which is the only way these take effect (systemctl restart mariadb): donedatabase.server.replication.allowed_from: authorize replication from fdfb:4991:29d::1 with the certificate/CN=keel-fdfb-4991-29d--1 mariadb of the mesh's root, outside the binary log (runuser -u mysql -- mariadb--batch, 5 statement(s) on standard input): donedatabase.server.role: the role is the VIP's: replica here (epoch known, held at fdfb:4991:29d::1); the declaredreplica is the installation's (0020)database.server.role: make the server follow the pair's VIP (keel database follow): the holder writable, theother node read only and replicating from the holder over TLS, an old primary rejoined by GTID when it holdsnothing the holder lacks: donederived.monit: write /etc/keel/monit/keel-manifest.conf: 12 unit(s) and 10 probe(s) of lnmp (mode 0600): doneoverlays.etcd: unchanged (enabled: etcd.service)overlays.crowdsec: unchanged (enabled: crowdsec.service, crowdsec-firewall-bouncer.service)overlays.vip: enable keel-vip.service: the overlay is enabled (systemctl enable keel-vip.service): doneoverlays.vip: start keel-vip.service: queue it: its job runs after etcd.service, which is ready only when amajority of its cluster runs, and this run does not wait for that majority (systemctl start --no-block57%
Keel Linux - First boot configuration
Status of this node
<  ok  >x
$ keel vip statusvip fdfb:4991:29d::ffff:1: this node's appliance.viprole: replicaepoch 1, held by <public key> at fdfb:4991:29d::1carried here: norouted to: <public key>$ keel mesh statusthis node: fdfb:4991:29d::7cb4/64 on wg0, WireGuard on UDP 51820mesh identity: 08ae4640eba45725377f58b1d9364bfdpublic key: <public key>peers: 2<public key>  fdfb:4991:29d::1/128  [2804:710:d0:5:be24:11ff:fe42:c0f]:51820handshake 43 s ago<public key>  fdfb:4991:29d::26f4/128[2804:710:d0:5:be24:11ff:fe50:e481]:51820  handshake 32 s agopending invites: 0etcd: 3 voter(s), 0 learner(s)keel-fdfb-4991-29d--7cb4  fdfb:4991:29d::7cb4  voter  healthykeel-fdfb-4991-29d--26f4  fdfb:4991:29d::26f4  voter  healthykeel-fdfb-4991-29d--1  fdfb:4991:29d::1  voter  healthyleader: keel-fdfb-4991-29d--1etcd: this member's certificate expires 2026-12-10 01:30 UTCvip fdfb:4991:29d::ffff:1: this node's appliance.viprole: replicaepoch 1, held by <public key> at fdfb:4991:29d::1carried here: norouted to: <public key>$ keel database statuspair: VIP fdfb:4991:29d::ffff:1; role here replica68%
>keelfirstboot cloud: Keel Cloud is not available yet: no key is asked, and this node runs standalone. It is offered once /etc/keel/cloud-endpoint names the service.
=== Keel Linux - First boot configuration
System Notifications and Critical Security Alerts
Enable local system notifications (root@localhost) to be
forwarded to your regular inbox. Notifications include
security updates and system messages.
Email:
<Enable>        < Skip >x

Keel Linux - First boot configuration
Waiting for the nodes
Waiting for the witness (node 3, Keel Core) to join with the line,
checked every 5 s. Back gives a menu: Paste accept line, when the
join printed one (keel mesh accept keel1a:...), or the line again.
This node: fdfb:4991:29d::1/64
Member: fdfb:4991:29d::7cb4, reached
etcd: not_formed, voters 0
VIP: fdfb:4991:29d::ffff:1, holder none yet
5
<Select>           < Back >x
4             3                         2                  1            0>
== Keel Linux - First boot configuration
Take the VIP
Waiting for the replica to pair with this node (keel vip pair on the
replica). Then this node applies its description and takes the VIP.
If the replica says it paired and nothing moves here, choose Back
and Take it now.
This node: fdfb:4991:29d::1/64
Member: fdfb:4991:29d::7cb4, reached
Member: fdfb:4991:29d::26f4, reached
e
Vx                                5
<Select>           < Back >x
4             3                  >
== Keel Linux - First boot configuration
Take the VIP
<  ok  >x
$ keel vip promotethis node holds fdfb:4991:29d::ffff:1 at epoch 1, by etcd's lease 134441423142732358the peers are told in the backgroundvip fdfb:4991:29d::ffff:1: fdfb:4991:29d::26f4: appliedvip fdfb:4991:29d::ffff:1: fdfb:4991:29d::7cb4: appliedkeel vip: exit 0, done
Keel Linux - First boot configuration
Status of this node
<  ok  >x
$ keel vip statusvip fdfb:4991:29d::ffff:1: this node's appliance.viprole: primaryepoch 1, held by <public key> at fdfb:4991:29d::1etcd lease 134441423142732358carried here: yesrouted to: no peer$ keel mesh statusthis node: fdfb:4991:29d::1/64 on wg0, WireGuard on UDP 51820mesh identity: 08ae4640eba45725377f58b1d9364bfdpublic key: <public key>peers: 2<public key>  fdfb:4991:29d::7cb4/128[2804:7f0:9880:6c3:dafd:796b:8898:aaf4]:51820  handshake 28 s ago<public key>  fdfb:4991:29d::26f4/128[2804:710:d0:5:be24:11ff:fe50:e481]:51820  handshake 29 s agopending invites: 0etcd: 3 voter(s), 0 learner(s)keel-fdfb-4991-29d--7cb4  fdfb:4991:29d::7cb4  voter  healthykeel-fdfb-4991-29d--26f4  fdfb:4991:29d::26f4  voter  healthykeel-fdfb-4991-29d--1  fdfb:4991:29d::1  voter  healthyleader: keel-fdfb-4991-29d--1etcd: this member's certificate expires 2026-12-10 01:26 UTCvip fdfb:4991:29d::ffff:1: this node's appliance.viprole: primaryepoch 1, held by <public key> at fdfb:4991:29d::1etcd lease 134441423142732358carried here: yesrouted to: no peer62%>keelfirstboot cloud: Keel Cloud is not available yet: no key is asked, and this node runs standalone. It is offered once /etc/keel/cloud-endpoint names the service.
=== Keel Linux - First boot configuration
System Notifications and Critical Security Alerts
Enable local system notifications (root@localhost) to be
forwarded to your regular inbox. Notifications include
security updates and system messages.
Email:
<Enable>        < Skip >x