So, to get routing back:

Not sure of the current benefit to use TC2.

This is still needed for acme.sh if we want to provision different *.nasqueron.org certificates on different servers.

Salt SELinux module issue

SELinux context was the default for anything created under /var, which we didn't allow and aren't interested to allow for nginx.

Yes, it's a fork from Vault 1.14 so we've all the features of token generation. back to the shorter s. tokens).

• about the UI it could be usefull managing secrets more easyly

Can't repro

Mumble isn't currently in scope.

Both are already set in DNS:

We use a wildcard certificate, so issuewild is needed, yes.

@Ash-Crow @fauve @rama @replicatorbe @Sandlayth @xcombelle Any feedback on this?

From router-001 network looks good:

Stopped currently not needed salt and node-exporter on router-001 to see if that helps.

Could be at hypervisor level. SSH failed until 13:22 where it worked immediately.