Vault server not initialized anymore after service restart

After changing the server config.hcl config since I wanted to update my certificate, restart the vault service ending up in Vault not capable of retrieving anything and pretending to not be initialized anymore. I’m using Raft as a storage backend and my config looks like this:

listener "tcp" {
  address = ""
  tls_disable = true

listener "tcp" {
  address = "SERVER_IP:8200"
  tls_cert_file = "/opt/vault/tls/mycert.cert.pem"
  tls_key_file  = "/opt/vault/tls/mykey.key.pem"

storage "raft" {
  path    = "/opt/vault/data"
  node_id = "node1"

ui = true
api_addr = "http://SERVER_IP:8200"
cluster_addr = "https://SERVER_IP:8201"

Vault version used is 1.8.1. Since it’s not storing in temporary folder I don’t see what could be wrong in terms of persistence, any clue?

Any logs that you can provide may prove helpful (system/service logs) in determining the cause in your specific case.
I learned recently that Vault going into an uninitialized state is kind of the default failure mode for unhandled exceptions so any additional logs you can provide would be quite helpful in determining the cause.

EDIT: Might have found something useful in /var/log/messages

Aug 26 16:31:39 vault vault[6099]: 2021-08-26T14:31:39.023Z [ERROR] core: unlocking HA lock failed: error="cannot find peer"
Aug 26 16:31:39 vault vault[6099]: 2021-08-26T14:31:39.024Z [ERROR] storage.raft.raft-net: failed to accept connection: error="Raft RPC layer closed"

I have audit logs enabled but it doesn’t seem to provide meaningful data, vault service status only shows

core: security barrier not initialized
core: seal configuration missing, not initialized

after opening the ui once. Just after doing a restart, it shows basic information about server launch and nothing special except one warn:

[WARN]  no `api_addr` value specified in config or in VAULT_AP` value specified in config or in VAULT_API_ADDR; falling back to detection if possible, but this value should be manually set