https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# neuvector-security
a
This message was deleted.
h
How did you install NV? Was it from Apps? Was it via Helm?
m
It was from apps
Apps > Charts > NeuVector (102.0.2+up2.4.5)
h
that should works right out of the box... since this is brand new install of NV, have you tried to uninstall and reinstall from Apps? to see if it works properly?
m
I have - It still results in authentication failed
I’ve also restarted/rebooted the nodes
Yeah, I just uninstalled/deleted the application and reinstalled it - no changes
I can access the app via 30954 and login using admin admin
but it does not work from the rancher UI
q
This message contains interactive elements.
m
yup
q
what version of Rancher?
m
2.7.5
q
hmmmm ok thanks. plz stand by
m
FYI
all passwords are the same between admin & this user-2147z
e.g. same password to login to Rancher + same to login to neuvector
b
@quaint-candle-18606 @most-market-25589, I'm getting the Authentication Failed error also on Rancher 2.7.4
m
I ended up going directly to the port of the application and logging in with admin admin, still no solution on my end other than bypassing rancher entirely
port 30954
q
does port 8443 also work?
b
@quaint-candle-18606 I am currently trying to reproduce this in my environment
🏆 1
@most-market-25589 Is this occurring on a downstream cluster or local Rancher cluster? Also, what kubernetes distro are you using? (RKE, RKE2 or K3s)
So quick update: I was able to install the latest Neuvector chart and did NOT encounter this issue: • Neuvector 102.0.2+up2.4.5 • Rancher version: v2.7.5 • Downstream RKE2 cluster running v1.26.5+rke2r1
b
uninstalling the Neuvector chart and reinstalling worked for me, on Rancher 2.7.4, NeuVector 102.0.2+up2.4.5, downstream cluster is 1.24.14+rke2r1
🤔 2
m
@boundless-holiday-25338 RKE2
i can check versions
👍 1
v1.25.11+rke2r1
v102.0.2+up2.4.5
v2.7.5
b
@most-market-25589 are you using the local admin to install this chart? Or using another user?
m
the local admin
👍 1
b
Did another test, this time with: • Rancher version: 2.7.5 • Kubernetes version: v1.25.11 +rke2r1 • Neuvector chart version: 102.0.2+up2.4.5 • OS: Ubuntu 22.10 Still wasn't able to reproduce this issue
@most-market-25589 what container runtime are you choosing when installing the Neuvector chart
Disregard that last comment --^ What browser are y'all using to login?
Try clearing your browsers cache, then try to login again @most-market-25589
m
Chrome - Version 114.0.5735.198 (Official Build) (arm64) - cache did not resolve anything
🤔 1
b
A few things: • Are you able to login using a private window? If so then it might cookie token related. ◦ If you can login, then navigate to the Settings page, select configuration, and then ctr+f or search for "Enable Control Path Logging" ◦ Then enable that (we would need this enabled temporary, after I suggest unchecking it) ◦ And if you can, grab a support bundle • If you are not able to login with a private browser, then can you grab the pod logs from the Neuvector controller?
Just writing some notes down; for another user running into this issue (They were using Terraform to spin up Neuvector)
For us. the issues were:
• global.cattle.url was not set (see link in first message of this thread)
• serviceAccount was set to the wring value. The default value (
neuvector
) should work fine
46 Views
Open in Slack
PreviousNext
Powered by