Can't connect to the Webinterface

chriss199815 · Dec 5, 2019

Hello there:

I installed proxmox for the first time yesterday and it worked fine. But after I trayed using an Old Switch today I could connect the server Anymore to be clear the Server didn't have any Interneconection as well.
As I didn't have anything on the Sever I choose the Reinstall proxmox But I still have the same problem. The Server is reachable by SSH and it has a connection to the Internet.
Has anybody an Idea?

Chris

Chris · Dec 5, 2019

Hi,
make sure you are using https and port 8006 to connect to the server. Since you have a working ssh connection, please check if the services are up and running systemctl status pveproxy pvedaemon and if the service is listening at the port 8006 ss -tl | grep 8006

chriss199815 · Dec 6, 2019

Yea,

it was the https thing. I feel so dumb now.
Thanks a lot.
Chriss

Edit: you can close.

Chris · Dec 6, 2019

chriss199815 said:
Yea,

it was the https thing. I feel so dumb now.
Thanks a lot.
Chriss

Edit: you can close.

No worries

glad it works!

smcracraft · Dec 6, 2019

Hmmm, I am not so lucky. While the above commands report aok (see below), the run of the proxmox_kvm.py code gives this when trying to create a PV:

creation of qemu VM centos-static with vmid 137 failed with exception=500 Internal Server Error: {\"data\":null}

So my question is how to drill down into the API to understand why it is giving the API error from the proxmox server.

API up:

Code:

root@ceph-hv-01:~# ss -tl | grep 8006
LISTEN   0         128                 0.0.0.0:8006              0.0.0.0:*     
root@ceph-hv-01:~# systemctl status pveproxy pvedaemon
● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset:
   Active: active (running) since Wed 2019-11-20 20:11:34 UTC; 2 weeks 1 days ag
  Process: 3082313 ExecReload=/usr/bin/pveproxy restart (code=exited, status=0/S
 Main PID: 1541509 (pveproxy)
    Tasks: 4 (limit: 6144)
   Memory: 169.6M
      CPU: 5h 4min 13.752s
   CGroup: /system.slice/pveproxy.service
           ├─1541509 pveproxy
           ├─3341423 pveproxy worker
           ├─3358483 pveproxy worker
           └─3361252 pveproxy worker

Dec 06 17:56:34 ceph-hv-01 pveproxy[1541509]: starting 1 worker(s)
Dec 06 17:56:34 ceph-hv-01 pveproxy[1541509]: worker 3341423 started
Dec 06 18:10:23 ceph-hv-01 pveproxy[3327359]: worker exit
Dec 06 18:10:23 ceph-hv-01 pveproxy[1541509]: worker 3327359 finished
Dec 06 18:10:23 ceph-hv-01 pveproxy[1541509]: starting 1 worker(s)
Dec 06 18:10:23 ceph-hv-01 pveproxy[1541509]: worker 3358483 started
Dec 06 18:12:49 ceph-hv-01 pveproxy[3329893]: worker exit
Dec 06 18:12:49 ceph-hv-01 pveproxy[1541509]: worker 3329893 finished
Dec 06 18:12:49 ceph-hv-01 pveproxy[1541509]: starting 1 worker(s)
Dec 06 18:12:49 ceph-hv-01 pveproxy[1541509]: worker 3361252 started

● pvedaemon.service - PVE API Daemon
   Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset
   Active: active (running) since Mon 2018-12-17 19:52:20 UTC; 11 months 19 days
 Main PID: 8987 (pvedaemon)
    Tasks: 4 (limit: 6144)
   Memory: 259.3M
      CPU: 3h 26min 12.103s
   CGroup: /system.slice/pvedaemon.service
           ├─   8987 pvedaemon
           ├─3316629 pvedaemon worker
           ├─3325563 pvedaemon worker
           └─3327272 pvedaemon worker

Dec 06 17:48:13 ceph-hv-01 pvedaemon[3327272]: <ansible@pam> end task UPID:ceph-
Dec 06 17:48:51 ceph-hv-01 pvedaemon[3327272]: <ansible@pam> update VM 86092: -d
Dec 06 17:48:51 ceph-hv-01 pvedaemon[3327272]: cannot delete 'balloon' - not set
Dec 06 17:48:51 ceph-hv-01 pvedaemon[3327272]: cannot delete 'shares' - not set
Dec 06 17:48:56 ceph-hv-01 pvedaemon[3332373]: start VM 86092: UPID:ceph-hv-01:0
Dec 06 17:48:56 ceph-hv-01 pvedaemon[3325563]: <ansible@pam> starting task UPID:
Dec 06 17:48:58 ceph-hv-01 pvedaemon[3325563]: <ansible@pam> end task UPID:ceph-
Dec 06 18:00:22 ceph-hv-01 pvedaemon[3316629]: <root@pam> successful auth for us
Dec 06 18:04:29 ceph-hv-01 pvedaemon[3325563]: <root@pam> successful auth for us
Dec 06 18:08:36 ceph-hv-01 pvedaemon[3327272]: <root@pam> successful auth for us
root@ceph-hv-01:~# exit

Chris · Dec 9, 2019

smcracraft said:

Hmmm, I am not so lucky. While the above commands report aok (see below), the run of the proxmox_kvm.py code gives this when trying to create a PV:

creation of qemu VM centos-static with vmid 137 failed with exception=500 Internal Server Error: {\"data\":null}

So my question is how to drill down into the API to understand why it is giving the API error from the proxmox server.

API up:

Code:

root@ceph-hv-01:~# ss -tl | grep 8006
LISTEN   0         128                 0.0.0.0:8006              0.0.0.0:*    
root@ceph-hv-01:~# systemctl status pveproxy pvedaemon
● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset:
   Active: active (running) since Wed 2019-11-20 20:11:34 UTC; 2 weeks 1 days ag
  Process: 3082313 ExecReload=/usr/bin/pveproxy restart (code=exited, status=0/S
Main PID: 1541509 (pveproxy)
    Tasks: 4 (limit: 6144)
   Memory: 169.6M
      CPU: 5h 4min 13.752s
   CGroup: /system.slice/pveproxy.service
           ├─1541509 pveproxy
           ├─3341423 pveproxy worker
           ├─3358483 pveproxy worker
           └─3361252 pveproxy worker

Dec 06 17:56:34 ceph-hv-01 pveproxy[1541509]: starting 1 worker(s)
Dec 06 17:56:34 ceph-hv-01 pveproxy[1541509]: worker 3341423 started
Dec 06 18:10:23 ceph-hv-01 pveproxy[3327359]: worker exit
Dec 06 18:10:23 ceph-hv-01 pveproxy[1541509]: worker 3327359 finished
Dec 06 18:10:23 ceph-hv-01 pveproxy[1541509]: starting 1 worker(s)
Dec 06 18:10:23 ceph-hv-01 pveproxy[1541509]: worker 3358483 started
Dec 06 18:12:49 ceph-hv-01 pveproxy[3329893]: worker exit
Dec 06 18:12:49 ceph-hv-01 pveproxy[1541509]: worker 3329893 finished
Dec 06 18:12:49 ceph-hv-01 pveproxy[1541509]: starting 1 worker(s)
Dec 06 18:12:49 ceph-hv-01 pveproxy[1541509]: worker 3361252 started

● pvedaemon.service - PVE API Daemon
   Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset
   Active: active (running) since Mon 2018-12-17 19:52:20 UTC; 11 months 19 days
Main PID: 8987 (pvedaemon)
    Tasks: 4 (limit: 6144)
   Memory: 259.3M
      CPU: 3h 26min 12.103s
   CGroup: /system.slice/pvedaemon.service
           ├─   8987 pvedaemon
           ├─3316629 pvedaemon worker
           ├─3325563 pvedaemon worker
           └─3327272 pvedaemon worker

Dec 06 17:48:13 ceph-hv-01 pvedaemon[3327272]: <ansible@pam> end task UPID:ceph-
Dec 06 17:48:51 ceph-hv-01 pvedaemon[3327272]: <ansible@pam> update VM 86092: -d
Dec 06 17:48:51 ceph-hv-01 pvedaemon[3327272]: cannot delete 'balloon' - not set
Dec 06 17:48:51 ceph-hv-01 pvedaemon[3327272]: cannot delete 'shares' - not set
Dec 06 17:48:56 ceph-hv-01 pvedaemon[3332373]: start VM 86092: UPID:ceph-hv-01:0
Dec 06 17:48:56 ceph-hv-01 pvedaemon[3325563]: <ansible@pam> starting task UPID:
Dec 06 17:48:58 ceph-hv-01 pvedaemon[3325563]: <ansible@pam> end task UPID:ceph-
Dec 06 18:00:22 ceph-hv-01 pvedaemon[3316629]: <root@pam> successful auth for us
Dec 06 18:04:29 ceph-hv-01 pvedaemon[3325563]: <root@pam> successful auth for us
Dec 06 18:08:36 ceph-hv-01 pvedaemon[3327272]: <root@pam> successful auth for us
root@ceph-hv-01:~# exit

Hi,
this seems totally unrelated to the original issue. Or do you experience issues while accessing the WebUI? Also where is the proxmox_kvm.py coming from? This seems to stem from outside of PVEs software stack.
The API documentation can be found here https://pve.proxmox.com/pve-docs/api-viewer/index.html
To check where the error is coming from you probably want to have a look at the source as well, see https://git.proxmox.com/
and https://git.proxmox.com/?p=qemu-server.git;a=summary in particular.

Search

Search

Can't connect to the Webinterface

chriss199815

Active Member

Chris

Proxmox Staff Member

chriss199815

Active Member

Chris

Proxmox Staff Member

smcracraft

Member

Chris

Proxmox Staff Member

We value your privacy