[SOLVED] Cant access proxmox webgui

I am not the most experienced person here - look at my badge ;)
I saw you already checked listener on on 8006 exists but did you also tried curl -k https://localhost:8006
If the html content is returned then the pveproxy service is working correctly, the only other option would be FW or weird routing in my opinion.
The curl command would create some entries in the log as well.

Good luck
 
hepo said:
I am not the most experienced person here - look at my badge ;)
I saw you already checked listener on on 8006 exists but did you also tried curl -k https://localhost:8006
If the html content is returned then the pveproxy service is working correctly, the only other option would be FW or weird routing in my opinion.
The curl command would create some entries in the log as well.

Good luck
Click to expand...

I think you guys really should loose like 45seconds and read the entire thread with attention before telling me to do the same thing again and again ahah
I did exactly everything that users sugested me ;)

Anyway, upgrading proxmox v6.3 to v6.4 brokes the FW or create weirth routing? Cause it was working perfectly before the upgrade.
 
Last edited:
root@DatacenterFR:~# wget --no-check-certificate https://localhost:8006
--2021-05-30 20:48:55-- https://localhost:8006/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8006... failed: Connection refused.

-------------------------------------------------------------------------------------------

root@DatacenterFR:~# nmap -p 8006 145.201.xxx.xxx
Starting Nmap 7.70 ( https://nmap.org ) at 2021-05-30 20:49 UTC
Nmap scan report for 145.201.xxx.xxx
Host is up (0.000052s latency).

PORT STATE SERVICE
8006/tcp closed wpl-analytics


Two simple tests, it says closed but this port is open, i really dont understand what happended after the upgrade...
 
lps90 said:
Two simple tests, it says closed but this port is open, i really dont understand what happended after the upgrade...
Click to expand...
can you please post the output of:

Code: 
cat /etc/hosts
cat /etc/network/interfaces
ip a

?
 
Solved in my case, is a problem of SSL:

upnpc -a [IP-PVE] 80 80 TCP 60
Code: 
upnpc : miniupnpc library test client, version 2.1.
 (c) 2005-2018 Thomas Bernard.
Go to http://miniupnp.free.fr/ or https://miniupnp.tuxfamily.org/
for more information.
List of UPNP devices found on the network :
 desc: http://192.***.0.***:5000/rootDesc.xml
 st: urn:schemas-upnp-org:device:InternetGatewayDevice:1

Found valid IGD : http://192.***.0.***:5000/ctl/IPConn
Local LAN ip address : 192.***.0.***
ExternalIPAddress = 190.***.245.***
InternalIP:Port = 192.***.0.***:80
external 190.***.245.***:80 TCP is redirected to internal 192.***.0.***:80 (duration=60)

pvenode acme cert order -f
Code: 
Loading ACME account details
Placing ACME order
Order URL: https://acme-v02.api.letsencrypt.org/acme/order/***/***

Getting authorization details from 'https://acme-v02.api.letsencrypt.org/acme/authz-v3/***'
The validation for servags-vm.***.** is pending!
Setting up webserver
Triggering validation
Sleeping for 5 seconds
Status is still 'pending', trying again in 10 seconds
Status is 'valid', domain 'servags-vm.***.**' OK!

All domains validated!

Creating CSR
Checking order status
Order is ready, finalizing order
valid!

Downloading certificate
Setting pveproxy certificate and key
Restarting pveproxy
Task OK

And works again... :)
 
Last edited:
dcsapak said:
can you please post the output of:

Code: 
cat /etc/hosts
cat /etc/network/interfaces
ip a

?
Click to expand...

Here is...

cat /etc/hosts:
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
149.2xx.xx.xx ns3xxxxx.ip-149-2xx-xx.eu DatacenterFR
# The following lines are desirable for IPv6 capable hosts
#(added automatically by netbase upgrade)


cat /etc/network/interfaces:
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback
iface lo inet6 loopback

auto eno1
iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
address 149.2xx.xx.xx/24
gateway 149.2xx.xx.254
bridge-ports eno1
bridge-stp off
bridge-fd 0

#Failover Ips

up ip addr add 51.xxx.xxx.xxx/32 dev vmbr0
down ip addr del 51.xxx.xxx.xxx/32 dev vmbr0
up ip addr add 51.2xx.xx.xx/32 dev vmbr0
down ip addr del 51.2xx.xx.xx/32 dev vmbr0
up ip addr add 146.5x.xx.xx/32 dev vmbr0
down ip addr del 146.5x.xx.xx/32 dev vmbr0
up ip addr add 87.9x.xxx.x/32 dev vmbr0
down ip addr del 87.9x.xxx.x/32 dev vmbr0
up ip addr add 192.168.1.1/24 dev vmbr0
down ip addr del 192.168.1.1/24 dev vmbr0
up ip addr add 192.168.2.1/24 dev vmbr0
down ip addr del 192.168.2.1/24 dev vmbr0

post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -t nat -A POSTROUTING -s '192.168.1.0/24' -o eno1 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -s '192.168.1.0/24' -o eno1 -j MASQUERADE

ip a:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether 08:62:66:37:17:43 brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 08:62:66:37:17:43 brd ff:ff:ff:ff:ff:ff
inet 149.2xx.xx.xx/24 brd 149.2xx.xx.255 scope global vmbr0
valid_lft forever preferred_lft forever
inet 51.xxx.xxx.xxx/32 scope global vmbr0
valid_lft forever preferred_lft forever
inet 51.2xx.xx.xx/32 scope global vmbr0
valid_lft forever preferred_lft forever
inet 146.5x.xx.xx/32 scope global vmbr0
valid_lft forever preferred_lft forever
inet 87.9x.xxx.x/32 scope global vmbr0
valid_lft forever preferred_lft forever
inet 192.168.1.1/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet 192.168.2.1/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::axx:xxff:fexx:xx43/64 scope link
valid_lft forever preferred_lft forever
12: veth104i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb master fwbr104i0 state UP group default qlen 1000
link/ether fe:13:0f:93:a6:77 brd ff:ff:ff:ff:ff:ff link-netnsid 2
13: fwbr104i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether ae:60:35:75:a3:92 brd ff:ff:ff:ff:ff:ff
14: fwpr104p0@fwln104i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether 8e:6c:e0:cb:6f:ed brd ff:ff:ff:ff:ff:ff
15: fwln104i0@fwpr104p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr104i0 state UP group default qlen 1000
link/ether ae:60:35:75:a3:92 brd ff:ff:ff:ff:ff:ff
16: veth402i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb master fwbr402i0 state UP group default qlen 1000
link/ether fe:c6:e8:47:da:59 brd ff:ff:ff:ff:ff:ff link-netnsid 3
17: fwbr402i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 16:02:81:71:d4:fb brd ff:ff:ff:ff:ff:ff
18: fwpr402p0@fwln402i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether 9a:fd:75:dd:d8:ff brd ff:ff:ff:ff:ff:ff
19: fwln402i0@fwpr402p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr402i0 state UP group default qlen 1000
link/ether 16:02:81:71:d4:fb brd ff:ff:ff:ff:ff:ff
20: veth404i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb master fwbr404i0 state UP group default qlen 1000
link/ether fe:8f:10:e6:80:1e brd ff:ff:ff:ff:ff:ff link-netnsid 4
21: fwbr404i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether ea:f8:e9:a8:f3:ec brd ff:ff:ff:ff:ff:ff
22: fwpr404p0@fwln404i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether a6:3b:5c:79:4f:9e brd ff:ff:ff:ff:ff:ff
23: fwln404i0@fwpr404p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr404i0 state UP group default qlen 1000
link/ether ea:f8:e9:a8:f3:ec brd ff:ff:ff:ff:ff:ff
24: veth320i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb master fwbr320i0 state UP group default qlen 1000
link/ether fe:fe:3e:61:90:3e brd ff:ff:ff:ff:ff:ff link-netnsid 5
25: fwbr320i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 82:b6:71:1b:e4:00 brd ff:ff:ff:ff:ff:ff
26: fwpr320p0@fwln320i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether ee:eb:f0:04:cd:18 brd ff:ff:ff:ff:ff:ff
27: fwln320i0@fwpr320p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr320i0 state UP group default qlen 1000
link/ether 82:b6:71:1b:e4:00 brd ff:ff:ff:ff:ff:ff
28: veth324i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb master fwbr324i0 state UP group default qlen 1000
link/ether fe:31:9f:b7:1c:ba brd ff:ff:ff:ff:ff:ff link-netnsid 6
29: fwbr324i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether fe:68:7c:f2:8e:05 brd ff:ff:ff:ff:ff:ff
30: fwpr324p0@fwln324i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether 5e:59:fb:1d:8c:af brd ff:ff:ff:ff:ff:ff
31: fwln324i0@fwpr324p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr324i0 state UP group default qlen 1000
link/ether fe:68:7c:f2:8e:05 brd ff:ff:ff:ff:ff:ff
32: veth450i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb master fwbr450i0 state UP group default qlen 1000
link/ether fe:c3:68:01:a2:75 brd ff:ff:ff:ff:ff:ff link-netnsid 7
33: fwbr450i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 32:bf:11:b1:0b:e1 brd ff:ff:ff:ff:ff:ff
34: fwpr450p0@fwln450i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether 86:55:dc:e2:67:ed brd ff:ff:ff:ff:ff:ff
35: fwln450i0@fwpr450p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr450i0 state UP group default qlen 1000
link/ether 32:bf:11:b1:0b:e1 brd ff:ff:ff:ff:ff:ff
36: veth106i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb master fwbr106i0 state UP group default qlen 1000
link/ether fe:b2:4e:bc:64:cf brd ff:ff:ff:ff:ff:ff link-netnsid 8
37: fwbr106i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 56:da:19:e4:d4:ab brd ff:ff:ff:ff:ff:ff
38: fwpr106p0@fwln106i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether f6:ba:6a:9f:48:d3 brd ff:ff:ff:ff:ff:ff
39: fwln106i0@fwpr106p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr106i0 state UP group default qlen 1000
link/ether 56:da:19:e4:d4:ab brd ff:ff:ff:ff:ff:ff
40: veth102i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb master fwbr102i0 state UP group default qlen 1000
link/ether fe:c5:79:a8:8c:fe brd ff:ff:ff:ff:ff:ff link-netnsid 1
41: fwbr102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether fe:c4:1a:ff:cb:46 brd ff:ff:ff:ff:ff:ff
42: fwpr102p0@fwln102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether 0a:82:42:50:7c:d7 brd ff:ff:ff:ff:ff:ff
43: fwln102i0@fwpr102p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr102i0 state UP group default qlen 1000
link/ether fe:c4:1a:ff:cb:46 brd ff:ff:ff:ff:ff:ff
48: veth100i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb master fwbr100i0 state UP group default qlen 1000
link/ether fe:f3:85:30:99:bb brd ff:ff:ff:ff:ff:ff link-netnsid 0
49: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether ea:24:8d:87:59:b7 brd ff:ff:ff:ff:ff:ff
50: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether 06:d1:90:25:04:34 brd ff:ff:ff:ff:ff:ff
51: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
link/ether ea:24:8d:87:59:b7 brd ff:ff:ff:ff:ff:ff
 
pcready.cl said:
Solved in my case, is a problem of SSL:

upnpc -a [IP-PVE] 80 80 TCP 60
Code: 
upnpc : miniupnpc library test client, version 2.1.
 (c) 2005-2018 Thomas Bernard.
Go to http://miniupnp.free.fr/ or https://miniupnp.tuxfamily.org/
for more information.
List of UPNP devices found on the network :
 desc: http://192.***.0.***:5000/rootDesc.xml
 st: urn:schemas-upnp-org:device:InternetGatewayDevice:1

Found valid IGD : http://192.***.0.***:5000/ctl/IPConn
Local LAN ip address : 192.***.0.***
ExternalIPAddress = 190.***.245.***
InternalIP:Port = 192.***.0.***:80
external 190.***.245.***:80 TCP is redirected to internal 192.***.0.***:80 (duration=60)

pvenode acme cert order -f
Code: 
Loading ACME account details
Placing ACME order
Order URL: https://acme-v02.api.letsencrypt.org/acme/order/***/***

Getting authorization details from 'https://acme-v02.api.letsencrypt.org/acme/authz-v3/***'
The validation for servags-vm.***.** is pending!
Setting up webserver
Triggering validation
Sleeping for 5 seconds
Status is still 'pending', trying again in 10 seconds
Status is 'valid', domain 'servags-vm.***.**' OK!

All domains validated!

Creating CSR
Checking order status
Order is ready, finalizing order
valid!

Downloading certificate
Setting pveproxy certificate and key
Restarting pveproxy
Task OK

And works again... :)
Click to expand...

upnpc -a 149.2xx.xx.xxx 80 80 TCP 60:
upnpc : miniupnpc library test client, version 2.1.
(c) 2005-2018 Thomas Bernard.
Go to http://miniupnp.free.fr/ or https://miniupnp.tuxfamily.org/
for more information.
No IGD UPnP Device found on the network !


pvenode acme cert order -f:
Can't use an undefined value as a HASH reference at /usr/share/perl5/PVE/API2/ACME.pm line 196.

Not a solution for me...
 
lps90 said:
upnpc -a 149.2xx.xx.xxx 80 80 TCP 60:
upnpc : miniupnpc library test client, version 2.1.
(c) 2005-2018 Thomas Bernard.
Go to http://miniupnp.free.fr/ or https://miniupnp.tuxfamily.org/
for more information.
No IGD UPnP Device found on the network !


pvenode acme cert order -f:
Can't use an undefined value as a HASH reference at /usr/share/perl5/PVE/API2/ACME.pm line 196.

Not a solution for me...
Click to expand...
Is the SSL certificate you use valid? in self-signed?
What is the result of:

systemctl status pveproxy.service

journalctl -u pveproxy.service
 
systemctl status pveproxy.service:
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-05-26 02:16:09 UTC; 5 days ago
Process: 5434 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 5439 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 5441 (pveproxy)
Tasks: 4 (limit: 4915)
Memory: 28.4M
CGroup: /system.slice/pveproxy.service
├─5441 pveproxy
├─5442 pveproxy worker
├─5443 pveproxy worker
└─5444 pveproxy worker

May 26 02:16:08 DatacenterFR systemd[1]: Starting PVE API Proxy Server...
May 26 02:16:09 DatacenterFR pveproxy[5441]: starting server
May 26 02:16:09 DatacenterFR pveproxy[5441]: starting 3 worker(s)
May 26 02:16:09 DatacenterFR pveproxy[5441]: worker 5442 started
May 26 02:16:09 DatacenterFR pveproxy[5441]: worker 5443 started
May 26 02:16:09 DatacenterFR pveproxy[5441]: worker 5444 started
May 26 02:16:09 DatacenterFR systemd[1]: Started PVE API Proxy Server.

journalctl -u pveproxy.service:
-- Logs begin at Tue 2021-05-18 00:59:54 UTC, end at Mon 2021-05-31 21:45:41 UTC. --
May 18 00:59:56 DatacenterFR systemd[1]: Starting PVE API Proxy Server...
May 18 00:59:57 DatacenterFR pveproxy[1195]: starting server
May 18 00:59:57 DatacenterFR pveproxy[1195]: starting 3 worker(s)
May 18 00:59:57 DatacenterFR pveproxy[1195]: worker 1196 started
May 18 00:59:57 DatacenterFR pveproxy[1195]: worker 1197 started
May 18 00:59:57 DatacenterFR pveproxy[1195]: worker 1198 started
May 18 00:59:57 DatacenterFR systemd[1]: Started PVE API Proxy Server.
May 19 00:00:00 DatacenterFR systemd[1]: Reloading PVE API Proxy Server.
May 19 00:00:00 DatacenterFR pveproxy[14959]: send HUP to 1195
May 19 00:00:00 DatacenterFR systemd[1]: Reloaded PVE API Proxy Server.
May 19 00:00:00 DatacenterFR pveproxy[1195]: received signal HUP
May 19 00:00:00 DatacenterFR pveproxy[1195]: server closing
May 19 00:00:00 DatacenterFR pveproxy[1195]: server shutdown (restart)
May 19 00:00:01 DatacenterFR pveproxy[1195]: restarting server
May 19 00:00:01 DatacenterFR pveproxy[1195]: starting 3 worker(s)
May 19 00:00:01 DatacenterFR pveproxy[1195]: worker 15901 started
May 19 00:00:01 DatacenterFR pveproxy[1195]: worker 15904 started
May 19 00:00:01 DatacenterFR pveproxy[1195]: worker 15906 started
May 19 00:00:06 DatacenterFR pveproxy[1197]: worker exit
May 19 00:00:06 DatacenterFR pveproxy[1198]: worker exit
May 19 00:00:06 DatacenterFR pveproxy[1196]: worker exit
May 19 00:00:07 DatacenterFR pveproxy[1195]: worker 1196 finished
May 19 00:00:07 DatacenterFR pveproxy[1195]: worker 1197 finished
May 19 00:00:07 DatacenterFR pveproxy[1195]: worker 1198 finished
May 25 15:11:16 DatacenterFR systemd[1]: Stopping PVE API Proxy Server...
May 25 15:11:16 DatacenterFR pveproxy[1195]: received signal TERM
May 25 15:11:16 DatacenterFR pveproxy[1195]: server closing
May 25 15:11:16 DatacenterFR pveproxy[15904]: worker exit
May 25 15:11:16 DatacenterFR pveproxy[15906]: worker exit
May 25 15:11:16 DatacenterFR pveproxy[15901]: worker exit
May 25 15:11:17 DatacenterFR pveproxy[1195]: worker 15901 finished
May 25 15:11:17 DatacenterFR pveproxy[1195]: worker 15906 finished
May 25 15:11:17 DatacenterFR pveproxy[1195]: worker 15904 finished
May 25 15:11:17 DatacenterFR pveproxy[1195]: server stopped
May 25 15:11:18 DatacenterFR systemd[1]: pveproxy.service: Succeeded.
May 25 15:11:18 DatacenterFR systemd[1]: Stopped PVE API Proxy Server.
May 25 15:11:18 DatacenterFR systemd[1]: Starting PVE API Proxy Server...
May 25 15:11:19 DatacenterFR pveproxy[12681]: starting server
May 25 15:11:19 DatacenterFR pveproxy[12681]: starting 3 worker(s)
May 25 15:11:19 DatacenterFR pveproxy[12681]: worker 12682 started
May 25 15:11:19 DatacenterFR pveproxy[12681]: worker 12683 started
May 25 15:11:19 DatacenterFR pveproxy[12681]: worker 12684 started
May 25 15:11:19 DatacenterFR systemd[1]: Started PVE API Proxy Server.
May 26 01:46:04 DatacenterFR systemd[1]: Stopping PVE API Proxy Server...
May 26 01:46:05 DatacenterFR pveproxy[12681]: received signal TERM
May 26 01:46:05 DatacenterFR pveproxy[12681]: server closing
May 26 01:46:05 DatacenterFR pveproxy[12683]: worker exit
May 26 01:46:05 DatacenterFR pveproxy[12684]: worker exit
May 26 01:46:05 DatacenterFR pveproxy[12682]: worker exit
May 26 01:46:05 DatacenterFR pveproxy[12681]: worker 12682 finished
May 26 01:46:05 DatacenterFR pveproxy[12681]: worker 12684 finished
May 26 01:46:05 DatacenterFR pveproxy[12681]: worker 12683 finished
 
I know the location is "/etc/pve/", but how i can check the expiration date?
 
Last edited:
openssl x509 -enddate -noout -in /etc/pve/pve-root-ca.pem:
notAfter=Dec 20 17:52:14 2030 GMT

idk if is the correct way to check it...
 
New to the fourms, but I have been spending some time trying to figure out the problem. Going as far as trying to reinstall it, which didn't work.
I've checked the SSL route - as long as the SSL certificate is "valid", Proxmox should start correctly.

I think I might have found a solution though. After poking around in the perl source code, Proxmox VE - and possibly other Proxmox software - has been programed to look for a config file in "/etc/default/$proxy_name". "$proxy_name" being the name of the web interface (pveproxy) or any other proxy for the Proxmox software.
After doing some debugging, I've got a basic file that tells pveproxy - the web interface program - to listen on "0.0.0.0", though I'm sure a reverse of this can be done for those needing IPv6 and are stuck on the IPv4 listening port.

Drop this file into /etc/default/pveproxy:
Bash: 
LISTEN_IP=0.0.0.0
This should tell pveproxy to listen on that address. This should fix OP's problem.

Edit: Forgot to add this. For the curious folke wanting to examine the Proxmox VE source code, it's located at "/usr/share/perl5/PVE/". Not like people already knew, but just in case for those who didn't find the page in the documentation. https://pve.proxmox.com/wiki/Developer_Documentation
 
Last edited:
  • Like
Reactions: blckdevice and lps90
hsf3232 said:
New to the fourms, but I have been spending some time trying to figure out the problem. Going as far as trying to reinstall it, which didn't work.
I've checked the SSL route - as long as the SSL certificate is "valid", Proxmox should start correctly.

I think I might have found a solution though. After poking around in the perl source code, Proxmox VE - and possibly other Proxmox software - has been programed to look for a config file in "/etc/default/$proxy_name". "$proxy_name" being the name of the web interface (pveproxy) or any other proxy for the Proxmox software.
After doing some debugging, I've got a basic file that tells pveproxy - the web interface program - to listen on "0.0.0.0", though I'm sure a reverse of this can be done for those needing IPv6 and are stuck on the IPv4 listening port.

Drop this file into /etc/default/pveproxy:
Bash: 
LISTEN_IP=0.0.0.0
This should tell pveproxy to listen on that address. This should fix OP's problem.

Edit: Forgot to add this. For the curious folke wanting to examine the Proxmox VE source code, it's located at "/usr/share/perl5/PVE/". Not like people already knew, but just in case for those who didn't find the page in the documentation. https://pve.proxmox.com/wiki/Developer_Documentation
Click to expand...

FINALLY!
Thank you mate, it works like a charm :p:D;)

Edit: After adding this "etc/default/pveproxy" file, users need to:
systemctl restart pve-cluster.service
systemctl restart pveproxy.service
 
Last edited:
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