I have a new cluster I am building in a datacenter. I have an existing cluster and desire to move guests to new hardware.
The original build was given an ip address on the internet through a vlan on a linux bond. Then a second vlan was added to connect the new servers to the old server switches through a Q-in-Q trunk. This way I can migrate across the lan. Networking wise all appears happy.
However, when I root login to the web gui via the original setup internet facing address, no problem. If I try from the internal address I can get to the GUI but it rejects the login.
For testing I added a PVE login and that appears to be fine on the lan address and fails on the internet interface.
Appears to me there is something set at the time of users creation that set a filter for access. Just don't know where to look.
Thanks.
The original build was given an ip address on the internet through a vlan on a linux bond. Then a second vlan was added to connect the new servers to the old server switches through a Q-in-Q trunk. This way I can migrate across the lan. Networking wise all appears happy.
However, when I root login to the web gui via the original setup internet facing address, no problem. If I try from the internal address I can get to the GUI but it rejects the login.
For testing I added a PVE login and that appears to be fine on the lan address and fails on the internet interface.
Appears to me there is something set at the time of users creation that set a filter for access. Just don't know where to look.
Thanks.