usernamemikem

Is anyone going to bother to look at this error?

Hi, As stated above, environment: OS Ubuntu 24.04. AWS EC2 Cluster, 3 Vault servers, two on standby, 5 Consul storage servers. From Standby Server, current status 429 Before Upgrade: vault...

I fixed the bad certificate error, but same results. vault[1349]: 2025-03-27T18:14:32.984Z [INFO] core: entering standby mode 2025-03-27T18:14:32.998921+00:00 ip-10-61-2-11 consul[552]: 2025-03-27T18:14:32.998Z [INFO] agent: Synced check: check=vault:vault-dr.cloud.triciti.com:8200:vault-sealed-check 2025-03-27T18:14:53.249455+00:00 ip-10-61-2-11 vault[1349]: 2025-03-27T18:14:53.248Z [ERROR]...

Hi. No, but all previous version worked. The main URL is an internal load balancer with only port 8200 open. It has never in all the years we've used it,...

 server_1 is running V1.19.0 server_2 and 0 are running V1.18.0 You can see that standby v1.18.0 is fine running on the same system without error. Thanks. Mike

This is interesting, here is the successful log of V1.18.0, yet is shows the same error port 8201. The consul shows three sync'd checks, while the above only shows one....

Hi, When I enter the keys to unseal the standby node, it shows Error: This is a standby Vault node but can't communicate with the active node via request forwarding....

Hi, Issue is still exists with the new release v1.20.0. I believe I now know why. The status code will start as 429 then changes to 474 after the following...