This message was deleted.
# generala
adamant-kite-43734
04/26/2023, 2:27 PMThis message was deleted.
h
hundreds-evening-84071
04/26/2023, 2:34 PMHave you looked at this document (option E): https://ranchermanager.docs.rancher.com/pages-for-subheaders/rancher-on-a-single-node-with-docker#2-choose-an-ssl-option-and-install-rancher
a
agreeable-pharmacist-24247
04/26/2023, 2:41 PMDon’t want to choose any and plain http is what am interested as while adding an existing cluster to rancher is causing cert issue
agreeable-pharmacist-24247
04/26/2023, 2:42 PMAs it’s not able to find cert or I don’t see an option to pass cert
f
full-painter-23916
04/26/2023, 4:39 PMIt is technically possible to configure the server to listen for plain http by (ab)using config meant for putting it behind a TLS-terminating device.
But the UI will not work without TLS, full-stop. It is 2023, not 1999. The auth cookie is marked
securea
agreeable-pharmacist-24247
04/26/2023, 4:41 PMYes we were able to generate and successfully installed and able to access ui with out issue s
agreeable-pharmacist-24247
04/26/2023, 4:42 PMBut when tried to add an existing cluster via the command we generate via the arancher UI
That was not able to authenticate against management due to cert
agreeable-pharmacist-24247
04/26/2023, 4:42 PMNow I do not see even the cert to be passed as an arg to the generated command
agreeable-pharmacist-24247
04/26/2023, 4:43 PMI meant the option to provide cert used by management to be passed to the seed cluster while joining
f
full-painter-23916
04/26/2023, 4:45 PMNormally the cert is just from a valid ca recognized by the agent. If you're generating your own then that needs to be configured in the server (this is "option b") and there is a mechanism where the agent downloads the cert and ensures its signature matches what was expected so you don't have to explicitly give it.
15 Views