Webinterface not reachable

Tim1

Member
May 5, 2022
55
0
6
Hello Guys,

I shutdown my Proxmox Server 1 month.
Today I started the Server and I cannot reach the webinterface.

Via Putty I can access the shell but not the webinterface.
My Servers are running in the background.

Any ideas?
 
Last edited:
With regard to your post in the other thread: the file needs to be explicitly created, and is then read automatically by the pveproxy service. Try writing it and then restarting the service (or rebooting) and see if that helps.
 
  • Like
Reactions: Tim1
With regard to your post in the other thread: the file needs to be explicitly created, and is then read automatically by the pveproxy service. Try writing it and then restarting the service (or rebooting) and see if that helps.
Done, but the Problem is still there
 
Could you attach the output of ss -tlnp and journalctl -u pveproxy?
 
root@pve:/etc/default# ss -tlnp
State Recv-Q Send-Q Local Address:port Peer Address:port Process
LISTEN 0 4096 127.0.0.1:85 0.0.0.0:* users:(("pvedaemon worke",pid=1158,fd=6),("pvedaemon worke",pid=1157,fd=6),("pvedaemon worke",pid=1156,fd=6),("pvedaemon",pid=1155,fd=6))
LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=836,fd=3))
LISTEN 0 4096 0.0.0.0:3128 0.0.0.0:* users:(("spiceproxy work",pid=1178,fd=6),("spiceproxy",pid=1177,fd=6))
LISTEN 0 100 127.0.0.1:25 0.0.0.0:* users:(("master",pid=1017,fd=13))
LISTEN 0 512 192.168.178.48:3300 0.0.0.0:* users:(("ceph-mon",pid=1026,fd=29))
LISTEN 0 512 192.168.178.48:6789 0.0.0.0:* users:(("ceph-mon",pid=1026,fd=30))
LISTEN 0 4096 0.0.0.0:8006 0.0.0.0:* users:(("pveproxy worker",pid=1172,fd=6),("pveproxy worker",pid=1171,fd=6),("pveproxy worker",pid=1170,fd=6),("pveproxy",pid=1169,fd=6))
LISTEN 0 4096 0.0.0.0:111 0.0.0.0:* users:(("rpcbind",pid=701,fd=4),("systemd",pid=1,fd=36))
LISTEN 0 512 192.168.178.48:6800 0.0.0.0:* users:(("ceph-mgr",pid=1475,fd=27))
LISTEN 0 512 192.168.178.48:6801 0.0.0.0:* users:(("ceph-mgr",pid=1475,fd=28))
LISTEN 0 128 [::]:22 [::]:* users:(("sshd",pid=836,fd=4))
LISTEN 0 100 [::1]:25 [::]:* users:(("master",pid=1017,fd=14))
LISTEN 0 4096 [::]:111 [::]:* users:(("rpcbind",pid=701,fd=6),("systemd",pid=1,fd=38))





Oct 19 09:59:44 pve systemd[1]: Starting PVE API Proxy Server...
Oct 19 09:59:45 pve pveproxy[3366]: starting server
Oct 19 09:59:45 pve pveproxy[3366]: starting 3 worker(s)
Oct 19 09:59:45 pve pveproxy[3366]: worker 3367 started
Oct 19 09:59:45 pve pveproxy[3366]: worker 3368 started
Oct 19 09:59:45 pve pveproxy[3366]: worker 3369 started
Oct 19 09:59:45 pve systemd[1]: Started PVE API Proxy Server.
Oct 19 10:03:31 pve systemd[1]: Stopping PVE API Proxy Server...
Oct 19 10:03:31 pve pveproxy[3366]: received signal TERM
Oct 19 10:03:31 pve pveproxy[3366]: server closing
Oct 19 10:03:31 pve pveproxy[3368]: worker exit
Oct 19 10:03:31 pve pveproxy[3369]: worker exit
Oct 19 10:03:31 pve pveproxy[3367]: worker exit
Oct 19 10:03:31 pve pveproxy[3366]: worker 3368 finished
Oct 19 10:03:31 pve pveproxy[3366]: worker 3369 finished
Oct 19 10:03:31 pve pveproxy[3366]: worker 3367 finished
Oct 19 10:03:31 pve pveproxy[3366]: server stopped
Oct 19 10:03:32 pve systemd[1]: pveproxy.service: Succeeded.
Oct 19 10:03:32 pve systemd[1]: Stopped PVE API Proxy Server.
Oct 19 10:03:32 pve systemd[1]: pveproxy.service: Consumed 1.222s CPU time.
Oct 19 10:03:32 pve systemd[1]: Starting PVE API Proxy Server...
Oct 19 10:03:33 pve pveproxy[4212]: starting server
Oct 19 10:03:33 pve pveproxy[4212]: starting 3 worker(s)
Oct 19 10:03:33 pve pveproxy[4212]: worker 4213 started
Oct 19 10:03:33 pve pveproxy[4212]: worker 4214 started
Oct 19 10:03:33 pve pveproxy[4212]: worker 4215 started
Oct 19 10:03:33 pve systemd[1]: Started PVE API Proxy Server.
Oct 19 10:05:20 pve systemd[1]: Stopping PVE API Proxy Server...
Oct 19 10:05:20 pve pveproxy[4212]: received signal TERM
Oct 19 10:05:20 pve pveproxy[4212]: server closing
Oct 19 10:05:20 pve pveproxy[4214]: worker exit
Oct 19 10:05:20 pve pveproxy[4213]: worker exit
Oct 19 10:05:20 pve pveproxy[4215]: worker exit
Oct 19 10:05:20 pve pveproxy[4212]: worker 4213 finished
Oct 19 10:05:20 pve pveproxy[4212]: worker 4215 finished
Oct 19 10:05:20 pve pveproxy[4212]: worker 4214 finished
Oct 19 10:05:20 pve pveproxy[4212]: server stopped
Oct 19 10:05:21 pve systemd[1]: pveproxy.service: Succeeded.
Oct 19 10:05:21 pve systemd[1]: Stopped PVE API Proxy Server.
Oct 19 10:05:21 pve systemd[1]: pveproxy.service: Consumed 1.235s CPU time.
Oct 19 10:05:21 pve systemd[1]: Starting PVE API Proxy Server...
Oct 19 10:05:22 pve pveproxy[4608]: starting server
Oct 19 10:05:22 pve pveproxy[4608]: starting 3 worker(s)
Oct 19 10:05:22 pve pveproxy[4608]: worker 4609 started
Oct 19 10:05:22 pve pveproxy[4608]: worker 4610 started
Oct 19 10:05:22 pve pveproxy[4608]: worker 4611 started
Oct 19 10:05:22 pve systemd[1]: Started PVE API Proxy Server.
Oct 19 10:05:34 pve systemd[1]: Stopping PVE API Proxy Server...
Oct 19 10:05:35 pve pveproxy[4608]: received signal TERM
Oct 19 10:05:35 pve pveproxy[4608]: server closing
Oct 19 10:05:35 pve pveproxy[4609]: worker exit
Oct 19 10:05:35 pve pveproxy[4610]: worker exit
Oct 19 10:05:35 pve pveproxy[4611]: worker exit
Oct 19 10:05:35 pve pveproxy[4608]: worker 4610 finished
Oct 19 10:05:35 pve pveproxy[4608]: worker 4611 finished
Oct 19 10:05:35 pve pveproxy[4608]: worker 4609 finished
Oct 19 10:05:35 pve pveproxy[4608]: server stopped
Oct 19 10:05:36 pve systemd[1]: pveproxy.service: Succeeded.
Oct 19 10:05:36 pve systemd[1]: Stopped PVE API Proxy Server.
Oct 19 10:05:36 pve systemd[1]: pveproxy.service: Consumed 1.224s CPU time.
Oct 19 10:05:36 pve systemd[1]: Starting PVE API Proxy Server...
Oct 19 10:05:36 pve pveproxy[4664]: starting server
Oct 19 10:05:36 pve pveproxy[4664]: starting 3 worker(s)
Oct 19 10:05:36 pve pveproxy[4664]: worker 4665 started
Oct 19 10:05:36 pve pveproxy[4664]: worker 4666 started
Oct 19 10:05:36 pve pveproxy[4664]: worker 4667 started
Oct 19 10:05:36 pve systemd[1]: Started PVE API Proxy Server.
Oct 19 10:12:05 pve systemd[1]: Stopping PVE API Proxy Server...
Oct 19 10:12:05 pve pveproxy[4664]: received signal TERM
Oct 19 10:12:05 pve pveproxy[4664]: server closing
Oct 19 10:12:05 pve pveproxy[4667]: worker exit
Oct 19 10:12:05 pve pveproxy[4666]: worker exit
Oct 19 10:12:05 pve pveproxy[4665]: worker exit
Oct 19 10:12:05 pve pveproxy[4664]: worker 4666 finished
Oct 19 10:12:05 pve pveproxy[4664]: worker 4667 finished
Oct 19 10:12:05 pve pveproxy[4664]: worker 4665 finished
Oct 19 10:12:05 pve pveproxy[4664]: server stopped
Oct 19 10:12:06 pve systemd[1]: pveproxy.service: Succeeded.
Oct 19 10:12:06 pve systemd[1]: Stopped PVE API Proxy Server.
Oct 19 10:12:06 pve systemd[1]: pveproxy.service: Consumed 1.253s CPU time.
-- Boot 155eba0f41d4415d9381c80c70135eb1 --
Oct 19 10:12:34 pve systemd[1]: Starting PVE API Proxy Server...
Oct 19 10:12:35 pve pveproxy[1168]: starting server
Oct 19 10:12:35 pve pveproxy[1168]: starting 3 worker(s)
Oct 19 10:12:35 pve pveproxy[1168]: worker 1169 started
Oct 19 10:12:35 pve pveproxy[1168]: worker 1170 started
Oct 19 10:12:35 pve pveproxy[1168]: worker 1171 started
Oct 19 10:12:35 pve systemd[1]: Started PVE API Proxy Server.
Oct 19 10:17:33 pve systemd[1]: Reloading PVE API Proxy Server.
Oct 19 10:17:33 pve pveproxy[14148]: send HUP to 1168
Oct 19 10:17:33 pve pveproxy[1168]: received signal HUP
Oct 19 10:17:33 pve pveproxy[1168]: server closing
Oct 19 10:17:33 pve pveproxy[1168]: server shutdown (restart)
Oct 19 10:17:33 pve systemd[1]: Reloaded PVE API Proxy Server.
Oct 19 10:17:34 pve pveproxy[1168]: restarting server
Oct 19 10:17:34 pve pveproxy[1168]: starting 3 worker(s)
Oct 19 10:17:34 pve pveproxy[1168]: worker 14159 started
Oct 19 10:17:34 pve pveproxy[1168]: worker 14160 started
Oct 19 10:17:34 pve pveproxy[1168]: worker 14161 started
Oct 19 10:17:39 pve pveproxy[1170]: worker exit
Oct 19 10:17:39 pve pveproxy[1169]: worker exit
Oct 19 10:17:39 pve pveproxy[1171]: worker exit
Oct 19 10:17:39 pve pveproxy[1168]: worker 1170 finished
Oct 19 10:17:39 pve pveproxy[1168]: worker 1169 finished
Oct 19 10:17:39 pve pveproxy[1168]: worker 1171 finished
Oct 19 10:18:14 pve systemd[1]: Stopping PVE API Proxy Server...
Oct 19 10:18:15 pve pveproxy[1168]: received signal TERM
Oct 19 10:18:15 pve pveproxy[1168]: server closing
Oct 19 10:18:15 pve pveproxy[14159]: worker exit
Oct 19 10:18:15 pve pveproxy[14161]: worker exit
Oct 19 10:18:15 pve pveproxy[14160]: worker exit
Oct 19 10:18:15 pve pveproxy[1168]: worker 14161 finished
Oct 19 10:18:15 pve pveproxy[1168]: worker 14159 finished
Oct 19 10:18:15 pve pveproxy[1168]: worker 14160 finished
Oct 19 10:18:15 pve pveproxy[1168]: server stopped
Oct 19 10:18:16 pve systemd[1]: pveproxy.service: Succeeded.
Oct 19 10:18:16 pve systemd[1]: Stopped PVE API Proxy Server.
Oct 19 10:18:16 pve systemd[1]: pveproxy.service: Consumed 2.281s CPU time.
-- Boot 753216c32a824fc1a6fbbbaa227a2f40 --
Oct 19 10:18:42 pve systemd[1]: Starting PVE API Proxy Server...
Oct 19 10:18:43 pve pveproxy[1174]: starting server
Oct 19 10:18:43 pve pveproxy[1174]: starting 3 worker(s)
Oct 19 10:18:43 pve pveproxy[1174]: worker 1175 started
Oct 19 10:18:43 pve pveproxy[1174]: worker 1176 started
Oct 19 10:18:43 pve pveproxy[1174]: worker 1177 started
Oct 19 10:18:43 pve systemd[1]: Started PVE API Proxy Server.
Oct 19 10:30:26 pve systemd[1]: Stopping PVE API Proxy Server...
Oct 19 10:30:27 pve pveproxy[1174]: received signal TERM
Oct 19 10:30:27 pve pveproxy[1174]: server closing
Oct 19 10:30:27 pve pveproxy[1177]: worker exit
Oct 19 10:30:27 pve pveproxy[1175]: worker exit
Oct 19 10:30:27 pve pveproxy[1176]: worker exit
Oct 19 10:30:27 pve pveproxy[1174]: worker 1175 finished
Oct 19 10:30:27 pve pveproxy[1174]: worker 1176 finished
Oct 19 10:30:27 pve pveproxy[1174]: worker 1177 finished
Oct 19 10:30:27 pve pveproxy[1174]: server stopped
Oct 19 10:30:28 pve systemd[1]: pveproxy.service: Succeeded.
Oct 19 10:30:28 pve systemd[1]: Stopped PVE API Proxy Server.
Oct 19 10:30:28 pve systemd[1]: pveproxy.service: Consumed 1.280s CPU time.
-- Boot 412b895f0d0b49a18d18a87113e4fdea --
Oct 19 11:00:41 pve systemd[1]: Starting PVE API Proxy Server...
Oct 19 11:00:42 pve pveproxy[1175]: starting server
Oct 19 11:00:42 pve pveproxy[1175]: starting 3 worker(s)
Oct 19 11:00:42 pve pveproxy[1175]: worker 1176 started
Oct 19 11:00:42 pve pveproxy[1175]: worker 1177 started
Oct 19 11:00:42 pve pveproxy[1175]: worker 1178 started
Oct 19 11:00:42 pve systemd[1]: Started PVE API Proxy Server.
Oct 19 11:06:58 pve systemd[1]: Stopping PVE API Proxy Server...
Oct 19 11:06:59 pve pveproxy[1175]: received signal TERM
Oct 19 11:06:59 pve pveproxy[1175]: server closing
Oct 19 11:06:59 pve pveproxy[1176]: worker exit
Oct 19 11:06:59 pve pveproxy[1178]: worker exit
Oct 19 11:06:59 pve pveproxy[1177]: worker exit
Oct 19 11:06:59 pve pveproxy[1175]: worker 1177 finished
Oct 19 11:06:59 pve pveproxy[1175]: worker 1176 finished
Oct 19 11:06:59 pve pveproxy[1175]: worker 1178 finished
Oct 19 11:06:59 pve pveproxy[1175]: server stopped
Oct 19 11:07:00 pve systemd[1]: pveproxy.service: Succeeded.
Oct 19 11:07:00 pve systemd[1]: Stopped PVE API Proxy Server.
Oct 19 11:07:00 pve systemd[1]: pveproxy.service: Consumed 1.231s CPU time.
Oct 19 11:07:00 pve systemd[1]: Starting PVE API Proxy Server...
Oct 19 11:07:01 pve pveproxy[2808]: starting server
Oct 19 11:07:01 pve pveproxy[2808]: starting 3 worker(s)
Oct 19 11:07:01 pve pveproxy[2808]: worker 2809 started
Oct 19 11:07:01 pve pveproxy[2808]: worker 2810 started
Oct 19 11:07:01 pve pveproxy[2808]: worker 2811 started
Oct 19 11:07:01 pve systemd[1]: Started PVE API Proxy Server.
Oct 19 11:08:08 pve systemd[1]: Stopping PVE API Proxy Server...
Oct 19 11:08:09 pve pveproxy[2808]: received signal TERM
Oct 19 11:08:09 pve pveproxy[2808]: server closing
Oct 19 11:08:09 pve pveproxy[2810]: worker exit
Oct 19 11:08:09 pve pveproxy[2811]: worker exit
Oct 19 11:08:09 pve pveproxy[2809]: worker exit
Oct 19 11:08:09 pve pveproxy[2808]: worker 2810 finished
Oct 19 11:08:09 pve pveproxy[2808]: worker 2809 finished
Oct 19 11:08:09 pve pveproxy[2808]: worker 2811 finished
Oct 19 11:08:09 pve pveproxy[2808]: server stopped
Oct 19 11:08:10 pve systemd[1]: pveproxy.service: Succeeded.
Oct 19 11:08:10 pve systemd[1]: Stopped PVE API Proxy Server.
Oct 19 11:08:10 pve systemd[1]: pveproxy.service: Consumed 1.214s CPU time.
-- Boot ecf86c49fa3642feaf9094cb3375bab0 --
Oct 19 11:08:36 pve systemd[1]: Starting PVE API Proxy Server...
Oct 19 11:08:36 pve pveproxy[1166]: starting server
Oct 19 11:08:36 pve pveproxy[1166]: starting 3 worker(s)
Oct 19 11:08:36 pve pveproxy[1166]: worker 1167 started
Oct 19 11:08:36 pve pveproxy[1166]: worker 1168 started
Oct 19 11:08:36 pve pveproxy[1166]: worker 1169 started
Oct 19 11:08:36 pve systemd[1]: Started PVE API Proxy Server.
Oct 19 11:10:23 pve systemd[1]: Stopping PVE API Proxy Server...
Oct 19 11:10:23 pve pveproxy[1166]: received signal TERM
Oct 19 11:10:23 pve pveproxy[1166]: server closing
Oct 19 11:10:23 pve pveproxy[1167]: worker exit
Oct 19 11:10:23 pve pveproxy[1169]: worker exit
Oct 19 11:10:23 pve pveproxy[1168]: worker exit
Oct 19 11:10:23 pve pveproxy[1166]: worker 1168 finished
Oct 19 11:10:23 pve pveproxy[1166]: worker 1167 finished
Oct 19 11:10:23 pve pveproxy[1166]: worker 1169 finished
Oct 19 11:10:23 pve pveproxy[1166]: server stopped
Oct 19 11:10:24 pve systemd[1]: pveproxy.service: Succeeded.
Oct 19 11:10:24 pve systemd[1]: Stopped PVE API Proxy Server.
Oct 19 11:10:24 pve systemd[1]: pveproxy.service: Consumed 1.232s CPU time.
Oct 19 11:10:24 pve systemd[1]: Starting PVE API Proxy Server...
Oct 19 11:10:25 pve pveproxy[1875]: starting server
Oct 19 11:10:25 pve pveproxy[1875]: starting 3 worker(s)
Oct 19 11:10:25 pve pveproxy[1875]: worker 1876 started
Oct 19 11:10:25 pve pveproxy[1875]: worker 1877 started
Oct 19 11:10:25 pve pveproxy[1875]: worker 1878 started
Oct 19 11:10:25 pve systemd[1]: Started PVE API Proxy Server.
Oct 19 11:12:27 pve systemd[1]: Stopping PVE API Proxy Server...
Oct 19 11:12:28 pve pveproxy[1875]: received signal TERM
Oct 19 11:12:28 pve pveproxy[1875]: server closing
Oct 19 11:12:28 pve pveproxy[1878]: worker exit
Oct 19 11:12:28 pve pveproxy[1876]: worker exit
Oct 19 11:12:28 pve pveproxy[1877]: worker exit
Oct 19 11:12:28 pve pveproxy[1875]: worker 1877 finished
Oct 19 11:12:28 pve pveproxy[1875]: worker 1878 finished
Oct 19 11:12:28 pve pveproxy[1875]: worker 1876 finished
Oct 19 11:12:28 pve pveproxy[1875]: server stopped
Oct 19 11:12:29 pve systemd[1]: pveproxy.service: Succeeded.
Oct 19 11:12:29 pve systemd[1]: Stopped PVE API Proxy Server.
Oct 19 11:12:29 pve systemd[1]: pveproxy.service: Consumed 1.226s CPU time.
-- Boot 2b274a5440074ba9aa17db91ab10e2eb --
Oct 19 11:49:09 pve systemd[1]: Starting PVE API Proxy Server...
Oct 19 11:49:10 pve pveproxy[1169]: starting server
Oct 19 11:49:10 pve pveproxy[1169]: starting 3 worker(s)
Oct 19 11:49:10 pve pveproxy[1169]: worker 1170 started
Oct 19 11:49:10 pve pveproxy[1169]: worker 1171 started
Oct 19 11:49:10 pve pveproxy[1169]: worker 1172 started
Oct 19 11:49:10 pve systemd[1]: Started PVE API Proxy Server.
 
I don't see any errors there… could you clarify what you mean by "not reachable"? Are you accessing the page over https? Can you access the page from the server itself through, say, curl -k https://localhost:8006?
 
I don't see any errors there… could you clarify what you mean by "not reachable"? Are you accessing the page over https? Can you access the page from the server itself through, say, curl -k https://localhost:8006?
I tested it as http / https, but site is noch available.

Output:

root@pve:~# curl -k https://localhost:8006
curl: (7) Failed to connect to localhost port 8006: Connection refused
 
Do you have any firewall rules configured? Is there anything interesting popping up in /var/log/pveproxy/access.log when you try to access the page?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!