Channels
extensions
rancher-extensions
supermicro-sixsq
ozt
os
one-point-x
rio
onlinemeetup
v16-v21-migration
events
onlinetraining
training-1220
training-0110
training-0124
k3s-contributor
submariner
storage
k3os
windows
ci-cd
theranchcast
rfed_ara
nederlands
ukranian
danish
training-0131
masterclass
training-0207
training-0214
terraform-controller
epinio
phillydotnet
swarm
rancher-wrangler
deutsch
russian
chinese
mesos
français
japanese
arm
longhorn-dev
terraform-provider-rke
service-mesh
azure
gcp
academy
random
elemental
espanol
lima
harvester-dev
portugues
kubernetes
kim
hypper
kubewarden
opni
logging
neuvector-security
rancher-setup
developer
office-hours
mexico
cabpr
rke
vsphere
longhorn-storage
k3s
k3d
terraform-provider-rancher2
fleet
amazon
harvester
rke2
s3gw
hobbyfarm
rancher-desktop
general
Title
f
flaky-winter-94949
11/11/2022, 8:14 PMCreate a new certificate secret, then edit the rancher ingress to use that new secret, be sure the secret is in the same namespace as the original
✅ 1
c
careful-article-61190
11/11/2022, 9:30 PMI did updated with new secrete, ingress but seems like its still shows insecure and old cert in browser do we need to redeploy ?
f
flaky-winter-94949
11/11/2022, 9:31 PMDid you add the entire cert chain or just the cert?
c
careful-article-61190
11/11/2022, 9:33 PMI added only cert
should i try cert chain, also do we need to redeploy or anything
f
flaky-winter-94949
11/11/2022, 9:36 PMFull chain, you shouldnt need a redeploy but you may have to use incogneto mode/clear cache
c
careful-article-61190
11/11/2022, 9:36 PMyes just installed full chain.
it's not working, still see old, Ingress is pointing to the secrete in same namespace as earlier secrete. I use pvt key and chain. I wonder there was some option to SSL reclycle or something.