Web Interface Not Working Properly(login fail and else).

SkyWhale

Active Member
May 22, 2018
5
0
41
40
I installed Proxmox today(8.3-1). I've been using Proxmox for 7 years, but this is the first time I've encountered such an issue(The last version i used is 5.xx).

After installation and logging in, I registered ZFS and a few other configurations. However, the web interface is not functioning properly (the loading spinner keeps spinning, but no data is retrieved).

When I attempted to log in again after logging out, I couldn't log in due to repeated timeouts (SSH login with a password works without any issues).

From within the server, I tested packets and found the following results:

Code:
174 curl -k https://localhost:8006 <- This works fine.
175 curl -k -d 'username=root@pam' --data-urlencode 'password=*****' https://localhost:8006/api2/json/access/ticket <- No response.
Below is the access.log file with web trying:

Code:
<First Page Access>

::ffff:192.168.1.12 - - [25/01/2025:03:35:11 +0900] "GET / HTTP/1.1" 200 887
::ffff:192.168.1.12 - - [25/01/2025:03:35:11 +0900] "GET /pve2/ext6/theme-crisp/resources/theme-crisp-all.css?ver=7.0.0 HTTP/1.1" 200 66
::ffff:192.168.1.12 - - [25/01/2025:03:35:11 +0900] "GET /pve2/ext6/crisp/resources/charts-all.css?ver=7.0.0 HTTP/1.1" 200 780
...
::ffff:192.168.1.12 - - [25/01/2025:03:35:15 +0900] "GET /pve2/ext6/theme-crisp/resources/images/form/exclamation.png HTTP/1.1" 200 1351

<Login Attempt>

::ffff:192.168.1.12 - - [25/01/2025:03:35:21 +0900] "GET /pve2/ext6/theme-crisp/resources/images/loadmask/loading.gif HTTP/1.1" 200 1849
::ffff:192.168.1.12 - - [25/01/2025:03:35:51 +0900] "POST /api2/extjs/access/ticket HTTP/1.1" 596 -
::ffff:192.168.1.12 - - [25/01/2025:03:35:51 +0900] "GET /pve2/ext6/theme-crisp/resources/images/tools/tool-sprites.png HTTP/1.1" 200 24404
::ffff:192.168.1.12 - - [25/01/2025:03:35:51 +0900] "GET /pve2/ext6/theme-crisp/resources/images/shared/icon-error.png HTTP/1.1" 200 18494

Here, I receive no response and only get an error icon.

So I rebooted and try again. Then, suddenly login is succeed! but after few second, not working again.

seems, web engine is OK but some packet between web and inner machine is fail.

What steps can I take next to resolve this issue? Thank you in advance for your guidance.

Let me know if you need adjustments or additional details!
 
If this is an IP conflict issue, requests from localhost should work normally.
Code:
174 curl -k https://localhost:8006 <- This works fine.
175 curl -k -d 'username=root@pam' --data-urlencode 'password=*****' https://localhost:8006/api2/json/access/ticket <- No response.
An IP conflict is definitely worth considering, but it is hard to explain why even localhost is not processing responses properly in this case.

Based on the packets, it seems that the localhost can successfully respond to requests for the "web interface" itself:

Code:
174 curl -k https://localhost:8006 <- This works fine.

However, when making a request to the API for a ticket, it consistently results in a timeout:
Code:
175 curl -k -d 'username=root@pam' --data-urlencode 'password=*****' https://localhost:8006/api2/json/access/ticket <- No response.

This behavior suggests that the issue might not be related to IP conflicts. Instead, it could be some type of API daemon issue, where the daemon responsible for handling API requests is either not running properly or encountering errors when processing requests.

It might be worth investigating the API-related services or logs to identify potential issues with the API daemon.