[SOLVED] Webgui refused to connect pveproxy running without erros

W

whattheserver

Member
Aug 23, 2015
5
3
23
whattheserver.me
installed a comodo SSL properly with chain via webgui it reloaded partially then wouldn't work after that

reverted the certificates via below

according to everything i can see it should be working tried alternate browsers and clearing cache using different IP still refused


any ideas?

have not tried rebooting node yet as i do not want to interrupt all the currently running VPS unnecessarily if possible


Code: 
pvecm updatecerts
pvecm updatecerts -f
systemctl restart pveproxy
root@coby:~# systemctl status pve-cluster pveproxy pvedaemon
● pve-cluster.service - The Proxmox VE cluster filesystem
   Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2018-07-06 15:12:59 CEST; 22min ago
  Process: 29353 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
  Process: 29331 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
 Main PID: 29337 (pmxcfs)
    Tasks: 6 (limit: 4915)
   Memory: 13.6M
      CPU: 1.880s
   CGroup: /system.slice/pve-cluster.service
           └─29337 /usr/bin/pmxcfs

Jul 06 15:12:57 coby systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jul 06 15:12:57 coby systemd[1]: Starting The Proxmox VE cluster filesystem...
Jul 06 15:12:59 coby systemd[1]: Started The Proxmox VE cluster filesystem.

● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2018-07-06 15:27:04 CEST; 8min ago
  Process: 24242 ExecStop=/usr/bin/pveproxy stop (code=exited, status=0/SUCCESS)
  Process: 29874 ExecReload=/usr/bin/pveproxy restart (code=exited, status=0/SUCCESS)
  Process: 24370 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
 Main PID: 24491 (pveproxy)
    Tasks: 4 (limit: 4915)
   Memory: 115.4M
      CPU: 1.358s
   CGroup: /system.slice/pveproxy.service
           ├─24491 pveproxy
           ├─24492 pveproxy worker
           ├─24493 pveproxy worker
           └─24494 pveproxy worker

Jul 06 15:27:03 coby systemd[1]: Starting PVE API Proxy Server...
Jul 06 15:27:04 coby pveproxy[24370]: Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface.
Jul 06 15:27:04 coby pveproxy[24491]: starting server
Jul 06 15:27:04 coby pveproxy[24491]: starting 3 worker(s)
Jul 06 15:27:04 coby pveproxy[24491]: worker 24492 started
Jul 06 15:27:04 coby pveproxy[24491]: worker 24493 started
Jul 06 15:27:04 coby pveproxy[24491]: worker 24494 started
Jul 06 15:27:04 coby systemd[1]: Started PVE API Proxy Server.

● pvedaemon.service - PVE API Daemon
   Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2018-07-06 14:32:28 CEST; 1h 2min ago
  Process: 9832 ExecStop=/usr/bin/pvedaemon stop (code=exited, status=0/SUCCESS)
  Process: 9846 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
 Main PID: 9909 (pvedaemon)
    Tasks: 4 (limit: 4915)
   Memory: 110.7M
      CPU: 1.375s
   CGroup: /system.slice/pvedaemon.service
           ├─9909 pvedaemon
           ├─9912 pvedaemon worker
           ├─9913 pvedaemon worker
           └─9914 pvedaemon worker

Jul 06 14:32:27 coby systemd[1]: Starting PVE API Daemon...
Jul 06 14:32:28 coby pvedaemon[9909]: starting server
Jul 06 14:32:28 coby pvedaemon[9909]: starting 3 worker(s)
Jul 06 14:32:28 coby pvedaemon[9909]: worker 9912 started
Jul 06 14:32:28 coby pvedaemon[9909]: worker 9913 started
Jul 06 14:32:28 coby systemd[1]: Started PVE API Daemon.
Jul 06 14:32:28 coby pvedaemon[9909]: worker 9914 started

root@coby:~#


root@coby:~# tail -f /var/log/pveproxy/access.log
redactedip - - [06/07/2018:14:29:52 +0200] "GET /pve2/ext6/crisp/resources/charts-all.css HTTP/1.1" 200 995
redactedip - - [06/07/2018:14:29:52 +0200] "GET /pve2/css/ext6-pve.css?ver=5.2-2 HTTP/1.1" 200 2814
redactedip - - [06/07/2018:14:29:52 +0200] "GET /pve2/ext6/charts.js HTTP/1.1" 304 -
redactedip - - [06/07/2018:14:29:52 +0200] "GET /pve2/ext6/locale/locale-en.js HTTP/1.1" 304 -
redactedip - - [06/07/2018:14:29:52 +0200] "GET /pve2/ext6/theme-crisp/resources/theme-crisp-all_1.css HTTP/1.1" 200 33744
redactedip - - [06/07/2018:14:29:54 +0200] "GET /pve2/fa/css/font-awesome.css HTTP/1.1" 200 7289
redactedip - - [06/07/2018:14:29:54 +0200] "GET /pve2/ext6/ext-all.js HTTP/1.1" 304 -
redactedip - - [06/07/2018:14:29:57 +0200] "GET /proxmoxlib.js?ver=1.0-19 HTTP/1.1" 304 -
redactedip - - [06/07/2018:14:29:57 +0200] "GET /pve2/js/pvemanagerlib.js?ver=5.2-2 HTTP/1.1" 304 -
163.172.135.224 - - [06/07/2018:15:29:52 +0200] "GET http0://....bing.com HTTP/1.1" 501 -



root@coby:~# tail /var/log/daemon.log
Jul  6 15:39:14 coby pvestatd[7251]: got timeout
Jul  6 15:39:44 coby pvestatd[7251]: got timeout
Jul  6 15:39:54 coby pvestatd[7251]: got timeout
Jul  6 15:39:59 coby pvestatd[7251]: status update time (7.020 seconds)
Jul  6 15:40:00 coby systemd[1]: Starting Proxmox VE replication runner...
Jul  6 15:40:00 coby systemd[1]: Started Proxmox VE replication runner.
Jul  6 15:40:14 coby pvestatd[7251]: got timeout
Jul  6 15:40:58 coby pvestatd[7251]: status update time (6.866 seconds)
Jul  6 15:41:00 coby systemd[1]: Starting Proxmox VE replication runner...
Jul  6 15:41:00 coby systemd[1]: Started Proxmox VE replication runner.
root@coby:~#

root@coby:~# netstat -ltn | grep 8006
tcp        0      0 0.0.0.0:8006            0.0.0.0:*               LISTEN     
root@coby:~#
root@coby:~# curl -s -k https:....//127.0.0.1:8006 | grep title
root@coby:~# curl -s -k https....://localhost:8006 | grep title
root@coby:~#


root@coby:~# pveversion
pve-manager/5.2-2/b1d1c7f4 (running kernel: 4.15.17-3-pve)
root@coby:~# uname -r
4.15.17-3-pve
root@coby:~#
root@coby:~# pve-firewall status
Status: disabled/stopped
root@coby:~#
 
  • Like
Reactions: helj15798 and Joeman79
You must log in or register to reply here.
Top Bottom