Can't access webgui

S

starfox64

New Member
Mar 31, 2024
6
0
1
root@colo:~# service pveproxy restart
Job for pveproxy.service failed because the control process exited with error code.
See "systemctl status pveproxy.service" and "journalctl -xeu pveproxy.service" for details.
root@colo:~# systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
Active: activating (start) since Sun 2024-03-31 00:51:31 CDT; 1s ago
Process: 10774 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Cntrl PID: 10779 (pveproxy)
Tasks: 1 (limit: 464128)
Memory: 71.4M
CPU: 1.042s
CGroup: /system.slice/pveproxy.service
└─10779 /usr/bin/perl -T /usr/bin/pveproxy start

Mar 31 00:51:31 colo systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
root@colo:~#


Any ideas, all vm's are running and acceible via rdp, but I can't access web gui.
 
Artem.ws said:
Did you try to run this command manually - pvecm updatecerts ?
Click to expand...
https://imgur.com/E23teVo

Yes and it gave me this:
root@colo:~# service pveproxy restart
Job for pveproxy.service failed because the control process exited with error code.
See "systemctl status pveproxy.service" and "journalctl -xeu pveproxy.service" for details.
root@colo:~# pvecm updatecerts
(re)generate node files
merge authorized SSH keys and known hosts
root@colo:~#
 
I'm new to the cmd line, ssh stuff. Web GUI was the selling point for me.

Any help is greatly appreciated. I need to gain access back to web gui asap.
 
Artem.ws said:
/usr/bin/pveproxy stop

/usr/bin/pveproxy start -debug
Click to expand...
As requested, exactly as you pasted.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Mar 31 01:31:02 2024 from ***.***.**.**
root@colo:~# /usr/bin/pveproxy stop
root@colo:~# /usr/bin/pveproxy start -debug
start failed - Invalid prefix 01000010101110110100011110100001/29
root@colo:~#
 
Last edited:
starfox64 said:
As requested, exactly as you pasted.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Mar 31 01:31:02 2024 from ***.***.**.**
root@colo:~# /usr/bin/pveproxy stop
root@colo:~# /usr/bin/pveproxy start -debug
start failed - Invalid prefix 01000010101110110100011110100001/29
root@colo:~#
Click to expand...
Very strange error start failed - Invalid prefix 01000010101110110100011110100001/29
Your node is not in Cluster? If not,
Try this:
1. Create file /etc/default/pveproxy for example via nano, like this nano /etc/default/pveproxy
2. Insert this LISTEN_IP="YOUR_LOCAL_IP" for example LISTEN_IP="192.168.110.188"
3. Save file. If you use nano, ctrl+x and Y, than enter
4. Try to start /usr/bin/pveproxy start -debug
 
so i feel stupid, but there was this in that file when i opened nano /etc/default/pveproxy
ALLOW_FROM="10.0.0.1-10.0.0.5,192.168.0.0/22,66.187.71.161/29"
DENY_FROM="all"
POLICY="allow"

Deleted, rebooted, service works.

Note to self, don't edit files
 
starfox64 said:
so i feel stupid, but there was this in that file when i opened nano /etc/default/pveproxy
ALLOW_FROM="10.0.0.1-10.0.0.5,192.168.0.0/22,66.187.71.161/29"
DENY_FROM="all"
POLICY="allow"

Deleted, rebooted, service works.

Note to self, don't edit files
Click to expand...
well, by default, this file doesn't exist)))

You are welcome)
 
You must log in or register to reply here.
Top Bottom