[SOLVED] can't access proxmox web GUI

[StamPoints]

I am pretty new to proxmox, the server have was working fine but now I can't access the Web GUI, with https://192.168.0.64:8006/, the VM still work as I can access them and do things on them, Linux VM, true nas etc....
I don't know what is relevant or not as I am still learning I will give all the information:
I have a intel 14900K , ddr5 192 gb ram, 3 4tb SSD's for the truenas, 2 4TB M.2 mirrored, on which there are all the VM's and proxmox, and a RTX 2000 ADA passed throw to the Linux VM for AI

on the shell when booting the server it spams things like this (I it out by so sorry if there are any mistakes):"
[32.511559] fwbr104i0: port 2(tap104i0) entering blocking state
[32.511605] fwbr104i0: port 2(tap104i0) entering forwarding state
[36.517386] tap111i0: enter promiscuous mode
[36.541032] vmbr0: port 7(fwpr111p0) entering blocking state
[36.541103] vmbr0: port 7(fwpr111p0) entering disabled state
[36.541164] fwpr111p0: entered allumulticast mode
[36.541237] fwpr111p0: entered promiscuous mode
[36.541351] vmbr0: port 7(fwpr111p0) entering blocking state
[36.541433] vmbr0: port 7(fwpr111p0) entering forwarding state"

and then after :

"[ 36.707163] x86/split lock detection: #AC: CPU 5/kvm/2901 took a split_locktrap at address: 0x7eefd050"

it does this for CPU 2, 3, 4, 5

I can make it ping itself in the shell

also i was getting

[111459.529637] systemd-journald[1015]: data hash table of /var/log/journal/c6c1b7d09b784dcaa39c3998c424fo1a/system.journal has a fill level at 75.0 174763 of 233016 items , 50331648 file size 287 bytes per hash table item, suggesting rotation

[111459.529627] systemd-journald[1015]: /var/log/journal/c6c1b7d09b784dcaa39c3998c424fo1a/system.journal limits reached or reader out-of-date, rotating

I tried rotating it and reducing it

with logrotate --force (not sure if I was doing it right )

and journalctl --vacuum-size=200m

also, I did a journalctl -f I think that is to see the errors I will have that in the picture below

 

[dj423]

I can make it ping itself in the shell

Can you ping the gateway from the pve host? DId anything change with your network interface setup by chance?

 

[StamPoints]

Can you ping the gateway from the pve host? DId anything change with your network interface setup by chance?

nothing changed in my network interface, and I can ping it from the proxmox shell and from my desktop

 

[dj423]

Maybe check if it's listening on port 8006?

sudo lsof -i -P -n | grep LISTEN

Should see something like:

pveproxy  2616079 www-data    6u  IPv6    16518      0t0  TCP *:8006 (LISTEN)
pveproxy  2990925 www-data    6u  IPv6    16518      0t0  TCP *:8006 (LISTEN)

If it's not listening, or if you haven't tried, you can bounce the web UI with

service pveproxy restart

 

[StamPoints]

one small question do you know how to switch the keyboard input language from the shell, I have a keyboard with a Chinese layout and proxmox is set to UK keyboard so I can't do "|" from sudo lsof -i -P -n | grep LISTEN

 

[dj423]

I don't, maybe try:

"localectl set-keymap <layout_code>"

 

[StamPoints]

I managed to switch keyboard with dpkg-reconfigure keyboard-configuration and a reboot, and here is now the result of lsof -i -P -n | grep LISTEN

 

[dj423]

Ok it's listening,
What does

pveproxy status

show?

 

[StamPoints]

Ok it's listening,
What does

pveproxy status

show?

Running

 

[dj423]

FYI If you shell into the pve host from your desktop, you can copy/paste from the terminal to avoid needing to photograph the screen.

 

[dj423]

Running

You might try "pveproxy restart" to see if that helps, are you running the firewall on the pve host by chance? Not sure why you can ping the host, but not connect via 8006, might comb the logs for clues too.

 

[StamPoints]

FYI If you shell into the pve host from your desktop, you can copy/paste from the terminal to avoid needing to photograph the screen.

That sounds great, just trying to figure out how to do that

 

[dj423]

From your desktop try: "ssh root@192.168.0.64" and enter in your creds for root.

 

[StamPoints]

You might try "pveproxy restart" to see if that helps, are you running the firewall on the pve host by chance? Not sure why you can ping the host, but not connect via 8006, might comb the logs for clues too.

I haven't set up a firewall yet, I just have tailscale on the vm's for now, I did the preproxy restart with no success.

 

[StamPoints]

 

[dj423]

From the pve host, try "curl -I http://192.168.0.64:8006"
should see output like:

HTTP/1.1 501 method 'HEAD' not available
Cache-Control: max-age=0
Connection: close
Date: Sun, 09 Feb 2025 00:01:27 GMT
Pragma: no-cache
Server: pve-api-daemon/3.0
Expires: Sun, 09 Feb 2025 00:01:27 GMT

 

[StamPoints]

it just hangs there without doing anything, also this showed up on the server

 

[gfngfn256]

Lets check space on /root, this filling up could cause availability problems.

So show output for:

df -hT

du -h -x -d1 /

 

[StamPoints]

here is the output for: df -hT du -h -x -d1 /

 

[gfngfn256]

You appear to have plenty space in /root ; not your issue.

However, I must tell you - to me I'm surprised that you have only 1.7G on / . On my system, that stores very little in root, I have 13G. I know other users have less than that, but 1.7G is almost unbelievable, to the point I'm concerned that you are missing things. Maybe I'm missing something with your setup/config.

I must point out, I don't use ZFS, so maybe some other user can chime-in here, as to their experience with this.