I am unable to log in to NSX-T UI using VIP IP address/FQDN in browser. When I try to login, it logs in, but when clicked on different tabs within it, it logs out automatically. In Google Chrome browser, after it logs out, I tried to check what's happening in the backend server access by pressing F12 key, I see error as "Failed to load resource: the server responded with a status of 403 ()".
Strange thing is we have two client windows VMs. I am able to log in to UI using VIP IP address/FQDN in browser, no issues. But in other client machine, it doesn't work.
NSX-T Manager version - 188.8.131.52.
I tried to look into the NSX-T Manager http.log file, I see below error log messages
I also, tried to look into the NSX-T Manager policy.log file, I see below error log messages,
Did anyone faced this issue earlier? any suggestions would be great help.
Message was edited by: Chethan B H Thought snippets pasted in the message content works, as it didn't, I have attached the snippets again.
Let me see if I got it right, you have two clients machine where you try to login into NSX-T by using the VIP or the FQDN to that VIP and it works always perfect from one but not from the other?
If this is case could you please answer this questions:
Thank you for looking into this issue. You got it right. We have two client machines, it was not working from 1st windows client machine for long time, we used to login with 2nd client machine. We had a lab Power up/Power down activity recently. After that. from 1st machine its working, from 2nd machine its not working now. Its very strange issue!
Please find my answers as below:
To be honest with you this does not seem to be an issue with NSX-T as it is working perfectly from one of your VMs, if you migrate the Windows VM to the same host where the working one is, does it work?
Also if you connect to the browser and run a netstat -an do you see all the connections being established?
I kept both the VMs on the same host and did run netstat -an on both the VMs. After hitting NSX-T Manager in browser, netstat result says connection is established with port 443 on both the VMs.