[SOLVED] My proxmox stopped responding in the browser (web interface).

[mar144]

Good afternoon,
My proxmox stopped responding in the browser (web interface).
I recently didn't make any changes or change my IP address. I have already tried the services but without success. Does anyone have any information that could help me solve this problem?

 

[Onslow]

Welcome, @mar144
What, exactly, did you do before it stopped?

 

[alexskysilk]

post the output of
systemctl -l --no-pager status pveproxy

 

[mar144]

Bem-vindo(a), @mar144
O que exatamente você fez antes de parar?

I didn't do anything, not even updating, creating new vms, nothing at all.

 

[mar144]

publicar a saída de
systemctl -l --no-pager status pveproxy

 

[mar144]

publicar a saída de
systemctl -l --no-pager status pveproxy

View attachment 97692

 

[alexskysilk]

best advice I can give anyone troubleshooting is learn to search the forum.

E

[SOLVED] Thread 'Cannot access WEB GUI'

Mar 31, 2022

Hi,

I did an update of my server and after the reboot, cannot access the web gui.
I tried to restart the pveproxy service and the log shows “permission denied” and i did a chmod 777 /var/log/pveproxy/access.log command…
Also i tried to do apt install proxmox-ve

Nothing works...

Some ideas? I'm desperate

Thanks

• Exio
• access cant connect gui gui problem permission timedout
• Replies: 20
• Forum: Proxmox VE: Installation and configuration

 

[mar144]

best advice I can give anyone troubleshooting is learn to search the forum.

E

[SOLVED] Thread 'Cannot access WEB GUI'

Mar 31, 2022

Hi,

I did an update of my server and after the reboot, cannot access the web gui.
I tried to restart the pveproxy service and the log shows “permission denied” and i did a chmod 777 /var/log/pveproxy/access.log command…
Also i tried to do apt install proxmox-ve

Nothing works...

Some ideas? I'm desperate

Thanks

• Exio
• access cant connect gui gui problem permission timedout
• Replies: 20
• Forum: Proxmox VE: Installation and configuration

Thanks for the recommendation to search the forum. From what I understand, what solved that colleague's problem in the matter you sent was this command "chmod 700 /var/log/pveproxy". I applied it here, but it didn't solve it. I still don't have access to the web interface, but this made me realize something important. I applied the command "systemctl status pvestatd.service" and saw an error message that is as follows: "BackupServer: error fetching datastores - 500 Can't connect to 192.168.254.23:8007 (No route to host)"

I had disabled this server for a long time, but I had not yet deleted the backup schedule at that location and I remembered that the problem with the interface started the day after I deleted the schedule. I don't know yet if this information will help us discover something that solves this problem.

 

[janus57]

Hi,

Look at your screen the file "access.log" have the wrong owner & chmod

Best regards,

 

[mar144]

I missed showing this command output as well:
root@proxmox01:/usr/share/pve-manager
# ls -ld /var/log/pveproxy/drwx------ 2 www-data www-data 10 May 13 15:22 /var/log/pveproxy/

 

[mar144]

Oi,

Observe na sua tela que o arquivo "access.log" possui o proprietário e as permissões (chmod) incorretas.

Atenciosamente,

Agora funcionou, meu amigo! Era isso mesmo. Mudei a propriedade do arquivo e o problema foi resolvido. Obrigado a todos.

 

[chenwb]

how about the network, press ip add,ping the gw

 

[gfngfn256]

What does this output:

df -h /