Proxmox Web-GUI doesn't connect

T

Tornavida

New Member
Jun 9, 2020
21
1
3
33
Hi

I've just installed the proxmox VE on my system some 2 days ago. got everything up and running.
But today suddenly my web-interface to the server just broke and was not reachable after rebooting it over SSH.
I've looked thru some threads here in the forum "but everything seems fine". So I also emptied my browser cache and tried over http and https. now am stuck with the ssh terminal. I could need some diagnostic help to understand what the problem might be.

cheers, Torna
 
yes ... actually I didn't make any changes or something. It was all running fine. because of AFK, i had to relogin (Web GUI). 'Put in my acc&pw and after the loading symbol appeared and didn't disappear for some 1-2 min. So I did # reboot now thru SSH and after that ... that

I put together a PC and wanted to play around VMs Nextcloud and stuff - so I've got nothing important on the Server. So I got not a lot of experience with Unix/Linus systems. more like Copy&Paste playarounds - , am a Pro in that. xD
 
I've now started my virtual machines via qm start XXX command. both, nextcloud and Win10Pro, are running and nextcloud is reachable thru Web GUI and also the Apps.
Maybe this info is of any value ?....
 
Tornavida said:
But today suddenly my web-interface to the server just broke and was not reachable after rebooting it over SSH
Click to expand...

Tornavida said:
I've now started my virtual machines via qm start XXX command. both, nextcloud and Win10Pro, are running and nextcloud is reachable thru Web GUI and also the Apps.
Maybe this info is of any value ?....
Click to expand...

Yeah, that means that the server is in general OK but there's something specific going on with the webserver.

Can you post the status: systemctl status pveproxy pvedaemon

You could also try to simply restart the services: systemctl restart pveproxy pvedaemon
 
t.lamprecht said:
Can you post the status: systemctl status pveproxy pvedaemon

You could also try to simply restart the services: systemctl restart pveproxy pvedaemon
Click to expand...

out:
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2020-06-10 00:05:43 CEST; 9h ago
Process: 1805 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 1812 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 1820 (pveproxy)
Tasks: 4 (limit: 4915)
Memory: 133.3M
CGroup: /system.slice/pveproxy.service
├─1820 pveproxy
├─1821 pveproxy worker
├─1822 pveproxy worker
└─1823 pveproxy worker

Jun 10 00:05:43 server systemd[1]: Starting PVE API Proxy Server...
Jun 10 00:05:43 server pveproxy[1820]: starting server
Jun 10 00:05:43 server pveproxy[1820]: starting 3 worker(s)
Jun 10 00:05:43 server pveproxy[1820]: worker 1821 started
Jun 10 00:05:43 server pveproxy[1820]: worker 1822 started
Jun 10 00:05:43 server pveproxy[1820]: worker 1823 started
Jun 10 00:05:43 server 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 Wed 2020-06-10 00:05:43 CEST; 9h ago
Process: 1706 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
Main PID: 1800 (pvedaemon)
Tasks: 4 (limit: 4915)
Memory: 133.8M
CGroup: /system.slice/pvedaemon.service
├─1800 pvedaemon
├─1801 pvedaemon worker
├─1802 pvedaemon worker
└─1803 pvedaemon worker

Jun 10 00:05:42 server systemd[1]: Starting PVE API Daemon...
Jun 10 00:05:43 server pvedaemon[1800]: starting server
Jun 10 00:05:43 server pvedaemon[1800]: starting 3 worker(s)
Jun 10 00:05:43 server pvedaemon[1800]: worker 1801 started
Jun 10 00:05:43 server pvedaemon[1800]: worker 1802 started
Jun 10 00:05:43 server pvedaemon[1800]: worker 1803 started
Jun 10 00:05:43 server systemd[1]: Started PVE API Daemon.


that's the output
 
Seems all OK. So this could be a network problem.
Please check you're using the correct address and it's configured on the host:
ip -br -c a

Also, you can check the access log of the public facing pveproxy: /var/log/pveproxy/access.log
 
You can check from the server SSH console if it'd be accessible from there: wget --no-check-certificate https://localhost:8006 to see if the server replies to request in general.
 
t.lamprecht said:
Seems all OK. So this could be a network problem.
Please check you're using the correct address and it's configured on the host:
ip -br -c a

Also, you can check the access log of the public facing pveproxy: /var/log/pveproxy/access.log
Click to expand...


Out:
root@server:~# ip -br -c a lo UNKNOWN 127.0.0.1/8 ::1/128 enp9s0 UP wlp8s0 DOWN vmbr0 UP 192.168.1.3/24 2a02:120b:2c6b:a1d0:7285:c2ff:feb4:f512/64 fe80::7285:c2ff:feb4:f512/64


log:
root@server:~# cd /var/log/pveproxy/ root@server:/var/log/pveproxy# ls access.log access.log.2.gz access.log.4.gz access.log.6.gz access.log.1 access.log.3.gz access.log.5.gz access.log.7.gz root@server:/var/log/pveproxy#

root@server:/var/log/pveproxy# nano access.log was empty

access.log.1:
has too many pages to post - but here I got a full list of accesses ... couldn't reach the last page tho.
ex:
192.168.1.127 - root@pam [09/06/2020:01:16:03 +0200] "GET /api2/json/nodes/server/qemu/101/status/current HTTP/1.1" 200 689 192.168.1.127 - root@pam [09/06/2020:01:16:03 +0200] "GET /api2/extjs/nodes/server/qemu/100/pending HTTP/1.1" 200 887 192.168.1.127 - root@pam [09/06/2020:01:16:04 +0200] "GET /api2/json/nodes/server/qemu/101/status/current HTTP/1.1" 200 688 192.168.1.127 - - [09/06/2020:01:34:09 +0200] "GET / HTTP/1.1" 200 800 192.168.1.127 - - [09/06/2020:01:34:09 +0200] "GET /pve2/ext6/theme-crisp/resources/theme-crisp-all.css HTTP/1.1" 200 68 192.168.1.127 - - [09/06/2020:01:34:09 +0200] "GET /pve2/ext6/crisp/resources/charts-all.css HTTP/1.1" 200 995 192.168.1.127 - - [09/06/2020:01:34:09 +0200] "GET /pve2/fa/css/font-awesome.css HTTP/1.1" 200 7289 192.168.1.127 - - [09/06/2020:01:34:09 +0200] "GET /pve2/js/u2f-api.js HTTP/1.1" 200 4901 192.168.1.127 - - [09/06/2020:01:34:09 +0200] "GET /pve2/ext6/locale/locale-en.js HTTP/1.1" 200 2569 192.168.1.127 - - [09/06/2020:01:34:09 +0200] "GET /pve2/css/ext6-pve.css?ver=6.2-4 HTTP/1.1" 200 3044 192.168.1.127 - - [09/06/2020:01:34:09 +0200] "GET /pwt/css/ext6-pmx.css?ver=2.2-1 HTTP/1.1" 200 179 192.168.1.127 - - [09/06/2020:01:34:09 +0200] "GET /pve2/js/qrcode.min.js HTTP/1.1" 200 6998 192.168.1.127 - - [09/06/2020:01:34:09 +0200] "GET /proxmoxlib.js?ver=2.2-1 HTTP/1.1" 200 48461 192.168.1.127 - - [09/06/2020:01:34:09 +0200] "GET /pve2/ext6/theme-crisp/resources/theme-crisp-all_1.css HTTP/1.1" 200 33744 192.168.1.127 - - [09/06/2020:01:34:09 +0200] "GET /pve2/ext6/theme-crisp/resources/theme-crisp-all_2.css HTTP/1.1" 200 5208 192.168.1.127 - - [09/06/2020:01:34:09 +0200] "GET /pve2/js/pvemanagerlib.js?ver=6.2-4 HTTP/1.1" 200 210060 192.168.1.127 - - [09/06/2020:01:34:09 +0200] "GET /pve2/ext6/ext-all.js HTTP/1.1" 200 609692 192.168.1.127 - - [09/06/2020:01:34:09 +0200] "GET /pve2/ext6/charts.js HTTP/1.1" 200 100383 192.168.1.127 - - [09/06/2020:01:34:11 +0200] "GET /pve2/ext6/theme-crisp/resources/images/form/trigger.png HTTP/1.1" 200 17627 192.168.1.127 - - [09/06/2020:01:34:11 +0200] "GET /pve2/ext6/theme-crisp/resources/images/form/checkbox.png HTTP/1.1" 200 17917 192.168.1.127 - - [09/06/2020:01:34:11 +0200] "GET /pve2/ext6/theme-crisp/resources/images/button/default-small-arrow.png HTTP/1.1" 200 17328 192.168.1.127 - - [09/06/2020:01:34:11 +0200] "GET /pve2/ext6/theme-crisp/resources/images/util/splitter/mini-bottom.png HTTP/1.1" 200 15274 192.168.1.127 - - [09/06/2020:01:34:11 +0200] "GET /pve2/ext6/theme-crisp/resources/images/tab-bar/default-scroll-left.png HTTP/1.1" 200 18514 192.168.1.127 - - [09/06/2020:01:34:11 +0200] "GET /pve2/ext6/theme-crisp/resources/images/tab-bar/default-scroll-right.png HTTP/1.1" 200 18517 192.168.1.127 - - [09/06/2020:01:34:11 +0200] "GET /pve2/ext6/theme-crisp/resources/images/tree/arrows.png HTTP/1.1" 200 3078 192.168.1.127 - - [09/06/2020:01:34:11 +0200] "GET /pve2/ext6/theme-crisp/resources/images/grid/sort_desc.png HTTP/1.1" 200 18260 192.168.1.127 - - [09/06/2020:01:34:11 +0200] "GET /pve2/images/proxmox_logo.png HTTP/1.1" 200 2809 192.168.1.127 - - [09/06/2020:01:34:11 +0200] "GET /pve2/fa/fonts/fontawesome-webfont.woff2?v=4.7.0 HTTP/1.1" 200 77160 192.168.1.127 - - [09/06/2020:01:34:11 +0200] "GET /api2/json/access/domains HTTP/1.1" 200 159 192.168.1.127 - - [09/06/2020:01:34:18 +0200] "GET /pve2/ext6/theme-crisp/resources/images/loadmask/loading.gif HTTP/1.1" 200 1849 192.168.1.127 - - [09/06/2020:01:34:19 +0200] "POST /api2/extjs/access/ticket HTTP/1.1" 200 682 192.168.1.127 - root@pam [09/06/2020:01:34:19 +0200] "GET /api2/extjs/version?_dc=1591659258315 HTTP/1.1" 200 95 192.168.1.127 - root@pam [09/06/2020:01:34:19 +0200] "GET /api2/extjs/cluster/sdn?_dc=1591659258316 HTTP/1.1" 200 92 192.168.1.127 - root@pam [09/06/2020:01:34:19 +0200] "GET /api2/extjs/nodes/localhost/subscription?_dc=1591659258317 HTTP/1.1" 200 180 192.168.1.127 - root@pam [09/06/2020:01:34:19 +0200] "GET /api2/json/cluster/resources HTTP/1.1" 200 542 192.168.1.127 - root@pam [09/06/2020:01:34:19 +0200] "GET /api2/json/cluster/tasks HTTP/1.1" 200 1030 192.168.1.127 - - [09/06/2020:01:34:19 +0200] "GET /pve2/ext6/theme-crisp/resources/images/tools/tool-sprites.png HTTP/1.1" 200 24404 192.168.1.127 - - [09/06/2020:01:34:19 +0200] "GET /pve2/ext6/theme-crisp/resources/images/shared/icon-warning.png HTTP/1.1" 200 17717 192.168.1.127 - root@pam [09/06/2020:01:34:19 +0200] "GET /api2/extjs/nodes/server/qemu/101/config?_dc=1591659258496 HTTP/1.1" 200 593 192.168.1.127 - - [09/06/2020:01:34:19 +0200] "GET /pve2/ext6/theme-crisp/resources/images/toolbar/default-scroll-left.png HTTP/1.1" 200 17863 192.168.1.127 - - [09/06/2020:01:34:19 +0200] "GET /pve2/ext6/theme-crisp/resources/images/button/default-toolbar-small-s-arrow.png HTTP/1.1" 200 17377 192.168.1.127 - - [09/06/2020:01:34:19 +0200] "GET /pve2/ext6/theme-crisp/resources/images/button/default-toolbar-small-arrow.png HTTP/1.1" 200 17341 192.168.1.127 - - [09/06/2020:01:34:19 +0200] "GET /pve2/ext6/theme-crisp/resources/images/toolbar/default-scroll-right.png HTTP/1.1" 200 18300 192.168.1.127 - - [09/06/2020:01:34:19 +0200] "GET /pve2/ext6/theme-crisp/resources/images/toolbar/default-scroll-top.png HTTP/1.1" 200 18260 192.168.1.127 - - [09/06/2020:01:34:19 +0200] "GET /pve2/ext6/theme-crisp/resources/images/toolbar/default-scroll-bottom.png HTTP/1.1" 200 18266 192.168.1.127 - - [09/06/2020:01:34:19 +0200] "GET /pve2/images/icon-ram.png HTTP/1.1" 200 193 192.168.1.127 - - [09/06/2020:01:34:19 +0200] "GET /pve2/images/icon-cpu.png HTTP/1.1" 200 205 192.168.1.127 - root@pam [09/06/2020:01:34:19 +0200] "GET /api2/json/nodes/server/qemu/101/rrddata?timeframe=hour&cf=AVERAGE HTTP/1.1" 200 3360 192.168.1.127 - root@pam [09/06/2020:01:34:19 +0200] "GET /api2/json/nodes/server/qemu/101/status/current HTTP/1.1" 200 664 192.168.1.127 - root@pam [09/06/2020:01:34:22 +0200] "GET /api2/json/nodes/server/qemu/101/status/current HTTP/1.1" 200 681

VM: 100 nextcloud, 101 Win10
 
t.lamprecht said:
You can check from the server SSH console if it'd be accessible from there: wget --no-check-certificate https://localhost:8006 to see if the server replies to request in general.
Click to expand...

out:
root@server:/var/log/pveproxy# wget --no-check-certificate https://localhost:8006 --2020-06-10 09:32:23-- https://localhost:8006/ Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost (localhost)|127.0.0.1|:8006... connected. WARNING: The certificate of ‘localhost’ is not trusted. WARNING: The certificate of ‘localhost’ doesn't have a known issuer. HTTP request sent, awaiting response... 200 OK Length: 2160 (2.1K) [text/html] Saving to: ‘index.html’ index.html 100%[===================================================================================================================================================================>] 2.11K --.-KB/s in 0s 2020-06-10 09:32:24 (171 MB/s) - ‘index.html’ saved [2160/2160]
 
.... I could open proxmox IP out for connection. if that would b of any use ??
as said, don't have any important files on the server pc...
 
... :p
Guys it's now running again. I restarted my client machine and tried it on MS Edge and now it works like nothin was.
Opera can't reach it still tho, but I guess it will be okay after clearing the cache or smh letting it connect to "insecure pages"
But thanks a lot for your efforts !!!!
:)
regards Torna
 
Tornavida said:
out:
root@server:/var/log/pveproxy# wget --no-check-certificate https://localhost:8006 --2020-06-10 09:32:23-- https://localhost:8006/ Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost (localhost)|127.0.0.1|:8006... connected. WARNING: The certificate of ‘localhost’ is not trusted. WARNING: The certificate of ‘localhost’ doesn't have a known issuer. HTTP request sent, awaiting response... 200 OK Length: 2160 (2.1K) [text/html] Saving to: ‘index.html’ index.html 100%[===================================================================================================================================================================>] 2.11K --.-KB/s in 0s 2020-06-10 09:32:24 (171 MB/s) - ‘index.html’ saved [2160/2160]
Click to expand...

yeah that definitively makes it a client or network issue.

Glad you figured it out, note also that we do not really test with opera but only with the following listed browsers:
https://pve.proxmox.com/pve-docs/ch..._web_browsers_for_accessing_the_web_interface
 
  • Like
Reactions: Tornavida
t.lamprecht said:
yeah that definitively makes it a client or network issue.

Glad you figured it out, note also that we do not really test with opera but only with the following listed browsers:
https://pve.proxmox.com/pve-docs/ch..._web_browsers_for_accessing_the_web_interface
Click to expand...


Danke trotzdem für die Hilfe und schnelle Reaktion. Hätte ich vorher checken müssen. Obwohl mit Opera hat es bis gestern gefunzt ... und nun kommt die Seite mit der Warnung die unsichere Seite trotzdem zu verbinden nicht mehr.
Werd mich nun ans letsencrypt für das SSl cert machen. Wird zwar nur für das nextcloud funktionieren denke ich.
 
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