Okay, this one I had to sleep on.
I had freshly installed Proxmox 9 on three separate boxes, set to updating and clustering. However, once clustered and while logged into 192.168.22.10 I could flit between two of the three, but not the third. And if I was logged into the third (..22.30) I was able to adjust it, but not the other two. It would time out, make me log back in again (which was getting infuriating) giving the "permission denied - invalid pve ticket (401)" error. A few google searches later and I was able to discern that it's timeclock was wrong. The system time was using BIOS as UTC and then adjusting for my -7 off my selection of America/LA. I then followed Alice down that rabbit hole, but nothing was adjusting the clock.
A few choice words later and my wife urging me to spend time with her relaxing instead of in the office suffering, and one nights sleep: I remembered that I hadn't changed the DNS settings during install. They default to 127.0.0.1 which I had left alone and planned to alter later since this box was going to run piHole1 for my setup. That was the ticket!
But nothing pointed that out. How could it? All of the wonderful searches I did had great ideas, but the system would only output data if there were any to output. Which there wasn't. Mind you (and this is where I realized my problem) that I could ping 1.1.1.1 but not google.com, obvious DNS issue right there if you know what to look for.
So I altered my /etc/resolv.conf file with my router's IP for DNS (for now) and then ran:
I hope this helps someone in the future.
(wave.gif)
I had freshly installed Proxmox 9 on three separate boxes, set to updating and clustering. However, once clustered and while logged into 192.168.22.10 I could flit between two of the three, but not the third. And if I was logged into the third (..22.30) I was able to adjust it, but not the other two. It would time out, make me log back in again (which was getting infuriating) giving the "permission denied - invalid pve ticket (401)" error. A few google searches later and I was able to discern that it's timeclock was wrong. The system time was using BIOS as UTC and then adjusting for my -7 off my selection of America/LA. I then followed Alice down that rabbit hole, but nothing was adjusting the clock.
A few choice words later and my wife urging me to spend time with her relaxing instead of in the office suffering, and one nights sleep: I remembered that I hadn't changed the DNS settings during install. They default to 127.0.0.1 which I had left alone and planned to alter later since this box was going to run piHole1 for my setup. That was the ticket!
But nothing pointed that out. How could it? All of the wonderful searches I did had great ideas, but the system would only output data if there were any to output. Which there wasn't. Mind you (and this is where I realized my problem) that I could ping 1.1.1.1 but not google.com, obvious DNS issue right there if you know what to look for.
So I altered my /etc/resolv.conf file with my router's IP for DNS (for now) and then ran:
Code:
systemctl restart chronyd
system networking restartI hope this helps someone in the future.
(wave.gif)