This message was deleted.
# general
a
This message was deleted.
b
if you are running k3s on the same host, it will spin up its own ingress controller that listens on ports 80/443, which likely conflict with your existing nginx installation. you may want to run it on its own host. Alternatively you an set alternate ports for the bundled ingress controller and then either proxy through nginx or just use the alt port to access rancher UI
l
Thank you for your answer, can you please let me know how to modify ingress controller config?
b
it's actually the service-lb that is using the port
l
Thank you 👍