Problem cant acces Proxmox via web

K

kraxxis

New Member
Oct 24, 2019
7
0
1
Hi!

I have Proxmox working fine, and after sometine from my last loggin via web now when I try to acces the browser (Chrome) give me this error "ERR_EMPTY_RESPONSE"

I always use https, so thats not my case, I tried and read so many posts but I couldn't find an solution.

Also I tried to renovate certificates as I read in another post

spirit said:
packages seem to be ok.

Can you try to regenerate certificates ?
#pvecm updatecerts --force

then

# /etc/init.d/pvedaemon restart
# /etc/init.d/pveproxy restart
Click to expand...

I can ping to the server and access via Putty, and the server can ping me, but is simpossible to acces via web and I tried Chrome, Explorer and Edge.

Any suggestion?

Thanks
 
t.lamprecht said:
Can you please also post the output of:
Code: 
systemctl status pveproxy pvedaemon
Click to expand...


root@srvprox01:~# systemctl status pveproxy pvedaemon
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset:
Active: active (running) since Thu 2019-10-24 21:58:08 CEST; 1 day 17h ago
Process: 13915 ExecStop=/usr/bin/pveproxy stop (code=exited, status=0/SUCCESS)
Process: 13330 ExecReload=/usr/bin/pveproxy restart (code=exited, status=0/SUC
Process: 13929 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCES
Main PID: 13967 (pveproxy)
Tasks: 4 (limit: 4915)
Memory: 105.1M
CPU: 36.420s
CGroup: /system.slice/pveproxy.service
├─13400 pveproxy worker
├─13401 pveproxy worker
├─13402 pveproxy worker
└─13967 pveproxy

Oct 25 06:25:11 srvprox01 pveproxy[13967]: starting 3 worker(s)
Oct 25 06:25:11 srvprox01 pveproxy[13967]: worker 13400 started
Oct 25 06:25:11 srvprox01 pveproxy[13967]: worker 13401 started
Oct 25 06:25:11 srvprox01 pveproxy[13967]: worker 13402 started
Oct 25 06:25:16 srvprox01 pveproxy[13972]: worker exit
Oct 25 06:25:16 srvprox01 pveproxy[13971]: worker exit
Oct 25 06:25:16 srvprox01 pveproxy[13970]: worker exit
lines 1-23...skipping...
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-10-24 21:58:08 CEST; 1 day 17h ago
Process: 13915 ExecStop=/usr/bin/pveproxy stop (code=exited, status=0/SUCCESS)
Process: 13330 ExecReload=/usr/bin/pveproxy restart (code=exited, status=0/SUCCESS)
Process: 13929 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 13967 (pveproxy)
Tasks: 4 (limit: 4915)
Memory: 105.1M
CPU: 36.420s
CGroup: /system.slice/pveproxy.service
├─13400 pveproxy worker
├─13401 pveproxy worker
├─13402 pveproxy worker
└─13967 pveproxy

Oct 25 06:25:11 srvprox01 pveproxy[13967]: starting 3 worker(s)
Oct 25 06:25:11 srvprox01 pveproxy[13967]: worker 13400 started
Oct 25 06:25:11 srvprox01 pveproxy[13967]: worker 13401 started
Oct 25 06:25:11 srvprox01 pveproxy[13967]: worker 13402 started
Oct 25 06:25:16 srvprox01 pveproxy[13972]: worker exit
Oct 25 06:25:16 srvprox01 pveproxy[13971]: worker exit
Oct 25 06:25:16 srvprox01 pveproxy[13970]: worker exit
Oct 25 06:25:16 srvprox01 pveproxy[13967]: worker 13972 finished
Oct 25 06:25:16 srvprox01 pveproxy[13967]: worker 13970 finished
Oct 25 06:25:16 srvprox01 pveproxy[13967]: worker 13971 finished

● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-10-24 21:57:47 CEST; 1 day 17h ago
Process: 13845 ExecStop=/usr/bin/pvedaemon stop (code=exited, status=0/SUCCESS)
Process: 13850 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
Main PID: 13869 (pvedaemon)
Tasks: 4 (limit: 4915)
Memory: 101.1M
CPU: 27.013s
CGroup: /system.slice/pvedaemon.service
├─13869 pvedaemon
├─13872 pvedaemon worker
├─13873 pvedaemon worker
└─13874 pvedaemon worker

Oct 24 21:57:42 srvprox01 systemd[1]: Starting PVE API Daemon...
Oct 24 21:57:47 srvprox01 pvedaemon[13869]: starting server
Oct 24 21:57:47 srvprox01 pvedaemon[13869]: starting 3 worker(s)
Oct 24 21:57:47 srvprox01 pvedaemon[13869]: worker 13872 started
lines 1-46...skipping...
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-10-24 21:58:08 CEST; 1 day 17h ago
Process: 13915 ExecStop=/usr/bin/pveproxy stop (code=exited, status=0/SUCCESS)
Process: 13330 ExecReload=/usr/bin/pveproxy restart (code=exited, status=0/SUCCESS)
Process: 13929 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 13967 (pveproxy)
Tasks: 4 (limit: 4915)
Memory: 105.1M
CPU: 36.420s
CGroup: /system.slice/pveproxy.service
├─13400 pveproxy worker
├─13401 pveproxy worker
├─13402 pveproxy worker
└─13967 pveproxy

Oct 25 06:25:11 srvprox01 pveproxy[13967]: starting 3 worker(s)
Oct 25 06:25:11 srvprox01 pveproxy[13967]: worker 13400 started
Oct 25 06:25:11 srvprox01 pveproxy[13967]: worker 13401 started
Oct 25 06:25:11 srvprox01 pveproxy[13967]: worker 13402 started
Oct 25 06:25:16 srvprox01 pveproxy[13972]: worker exit
Oct 25 06:25:16 srvprox01 pveproxy[13971]: worker exit
Oct 25 06:25:16 srvprox01 pveproxy[13970]: worker exit
Oct 25 06:25:16 srvprox01 pveproxy[13967]: worker 13972 finished
Oct 25 06:25:16 srvprox01 pveproxy[13967]: worker 13970 finished
Oct 25 06:25:16 srvprox01 pveproxy[13967]: worker 13971 finished

● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-10-24 21:57:47 CEST; 1 day 17h ago
Process: 13845 ExecStop=/usr/bin/pvedaemon stop (code=exited, status=0/SUCCESS)
Process: 13850 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
Main PID: 13869 (pvedaemon)
Tasks: 4 (limit: 4915)
Memory: 101.1M
CPU: 27.013s
CGroup: /system.slice/pvedaemon.service
├─13869 pvedaemon
├─13872 pvedaemon worker
├─13873 pvedaemon worker
└─13874 pvedaemon worker

Oct 24 21:57:42 srvprox01 systemd[1]: Starting PVE API Daemon...
Oct 24 21:57:47 srvprox01 pvedaemon[13869]: starting server
Oct 24 21:57:47 srvprox01 pvedaemon[13869]: starting 3 worker(s)
Oct 24 21:57:47 srvprox01 pvedaemon[13869]: worker 13872 started
Oct 24 21:57:47 srvprox01 pvedaemon[13869]: worker 13873 started
Oct 24 21:57:47 srvprox01 pvedaemon[13869]: worker 13874 started
Oct 24 21:57:47 srvprox01 systemd[1]: Started PVE API Daemon.
 
If it helps, I tried to do an "update and upgrade" and then I got this answer:

Code: 
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 pve-firmware : Conflicts: firmware-linux-free but 3.4 is to be installed
E: Broken packages


The server is on from last 9 months and never had this problems before. I don't know how to deal with this exactly :| I'm practicly new with Linux o_O
 
kraxxis said:
If it helps, I tried to do an "update and upgrade" and then I got this answer:
Click to expand...
Did you 'upgrade' or 'dist-upgrade', or maybe 'full upgrade'?

Code: 
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
pve-firmware : Conflicts: firmware-linux-free but 3.4 is to be installed
E: Broken packages


The server is on from last 9 months and never had this problems before. I don't know how to deal with this exactly :| I'm practicly new with Linux o_O
Click to expand...
How new is 'practically new' :)

Do you know where to find apt sources, and how to have a look at them? (/etc/apt/sources.list)

I am new to Proxmox, but I know that with the release of Proxmox6, the underlying Debian system went from Stretch to Buster. I guess you are running 'Stretch', but I don't know what the default kernel with Proxmox5 was. In my (just installed) Proxmox6, I got a 5.x kernel version, so your version is not upgraded but might want to do so.
 
wbk said:
Did you 'upgrade' or 'dist-upgrade', or maybe 'full upgrade'?
Click to expand...

I did "apt update && apt upgrade"

How new is 'practically new' :)

Do you know where to find apt sources, and how to have a look at them? (/etc/apt/sources.list)

I am new to Proxmox, but I know that with the release of Proxmox6, the underlying Debian system went from Stretch to Buster. I guess you are running 'Stretch', but I don't know what the default kernel with Proxmox5 was. In my (just installed) Proxmox6, I got a 5.x kernel version, so your version is not upgraded but might want to do so.
Click to expand...

My Debian version is Stretch yes, and the version is "Linux srvprox01 4.13.13-5-pve #1 SMP PVE 4.13.13-38" but I don't know exactly why is that important for the problem that I have :/


@t.lamprecht Did you check the log that you ask for? Any help please.
 
The error from apt upgrade may not be related to your problem with the web front end, but it should not happen either. I would solve that issue anyway.

I did not know which version of linux-firmware-free was supposed to be on your system, and thought: "Maybe the system is being upgraded to a new major version (apt-get dist-upgrade), and is the kernel updated with a wish for a newer firmware package."

Thinking about it, the firmwares have not so much to do with the kernel, so my post was not so helpful. With your answer it is clear that the upgrade is not to a new version of Debian either :)

Sorry for my lack of knowledge of Proxmox, good luck!
 
wbk said:
The error from apt upgrade may not be related to your problem with the web front end, but it should not happen either. I would solve that issue anyway.

I did not know which version of linux-firmware-free was supposed to be on your system, and thought: "Maybe the system is being upgraded to a new major version (apt-get dist-upgrade), and is the kernel updated with a wish for a newer firmware package."

Thinking about it, the firmwares have not so much to do with the kernel, so my post was not so helpful. With your answer it is clear that the upgrade is not to a new version of Debian either :)

Sorry for my lack of knowledge of Proxmox, good luck!
Click to expand...


Thanks anyway for your help dude. At least you tried to help.

Anyway, I finally just resolved both errors just trying to resolve the "apt-get upgrade" problem. Basicly the source list had a duplicate source, once I deleted the duplicated I could upgrade. But for any reason linux was trying to update the "linux-firmware" instead of the "pve-firmware" and once I resolved that, the acces to the web start to work again :D
 
kraxxis said:
Thanks anyway for your help dude. At least you tried to help.

Anyway, I finally just resolved both errors just trying to resolve the "apt-get upgrade" problem. Basicly the source list had a duplicate source, once I deleted the duplicated I could upgrade. But for any reason linux was trying to update the "linux-firmware" instead of the "pve-firmware" and once I resolved that, the acces to the web start to work again :D
Click to expand...

Ah OK, so the interrupted upgrade caused those issues. Still strange that an exact duplicate source3 entry could cause this...
FYI, always use apt full-upgrade to upgrade a Proxmox VE instance, sometimes we need to remove replace packages, so "upgrade" alone won't always do it. We prohibit to remove proxmox-ve per default anyway, so even a missconfiguration should not let apt remove PVE immediately.

Anyway, great you solved it.
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back