[SOLVED] no web interface, only ssh access

T

Th3ddy

New Member
Feb 11, 2025
13
3
3
Hi everyone, I really need your help. I no longer have a web interface and my services/VMs no longer start. I only have access to PVE via ssh.

If it is log can help you. Because I don't understand. Thank you for your help.

Code: 
root@pve:~# systemctl restart pveproxy
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@pve:~# systemctl status pveproxy.service
× pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Tue 2025-07-29 05:58:01 PST; 37s ago
    Process: 5219 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 5221 ExecStart=/usr/bin/pveproxy start (code=exited, status=255/EXCEPTION)
        CPU: 595ms

Jul 29 05:58:01 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
Jul 29 05:58:01 pve systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
Jul 29 05:58:01 pve systemd[1]: pveproxy.service: Start request repeated too quickly.
Jul 29 05:58:01 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Jul 29 05:58:01 pve systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.


Then this command:

Code: 
root@pve:~# journalctl -xeu pveproxy.service
░░
░░ The job identifier is 2475 and the job result is done.
Jul 29 05:58:00 pve systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
░░ Subject: A start job for unit pveproxy.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has begun execution.
░░
░░ The job identifier is 2475.
Jul 29 05:58:00 pve pveproxy[5218]: syntax error at /usr/share/perl5/PVE/API2/Subscription.pm line 215, near "message"
Jul 29 05:58:00 pve pveproxy[5218]: Global symbol "$no_subscription_info" requires explicit package name (did you forget to declare "my $no_subscript>
Jul 29 05:58:00 pve pveproxy[5218]: Global symbol "$no_subscription_info" requires explicit package name (did you forget to declare "my $no_subscript>
Jul 29 05:58:00 pve pveproxy[5218]: syntax error at /usr/share/perl5/PVE/API2/Subscription.pm line 222, near "if"
Jul 29 05:58:00 pve pveproxy[5218]: Global symbol "$has_permission" requires explicit package name (did you forget to declare "my $has_permission"?) >
Jul 29 05:58:00 pve pveproxy[5218]: Global symbol "$info" requires explicit package name (did you forget to declare "my $info"?) at /usr/share/perl5/>
Jul 29 05:58:00 pve pveproxy[5218]: Global symbol "$info" requires explicit package name (did you forget to declare "my $info"?) at /usr/share/perl5/>
Jul 29 05:58:00 pve pveproxy[5218]: Global symbol "$url" requires explicit package name (did you forget to declare "my $url"?) at /usr/share/perl5/PV>
Jul 29 05:58:00 pve pveproxy[5218]: Global symbol "$info" requires explicit package name (did you forget to declare "my $info"?) at /usr/share/perl5/>
Jul 29 05:58:00 pve pveproxy[5218]: Global symbol "$server_id" requires explicit package name (did you forget to declare "my $server_id"?) at /usr/sh>
Jul 29 05:58:00 pve pveproxy[5218]: Global symbol "$info" requires explicit package name (did you forget to declare "my $info"?) at /usr/share/perl5/>
Jul 29 05:58:00 pve pveproxy[5218]: Global symbol "$info" requires explicit package name (did you forget to declare "my $info"?) at /usr/share/perl5/>
Jul 29 05:58:00 pve pveproxy[5218]: Global symbol "$url" requires explicit package name (did you forget to declare "my $url"?) at /usr/share/perl5/PV>
Jul 29 05:58:00 pve pveproxy[5218]: Global symbol "$info" requires explicit package name (did you forget to declare "my $info"?) at /usr/share/perl5/>
Jul 29 05:58:00 pve pveproxy[5218]: syntax error at /usr/share/perl5/PVE/API2/Subscription.pm line 235, near "}"
Jul 29 05:58:00 pve pveproxy[5218]: /usr/share/perl5/PVE/API2/Subscription.pm has too many errors.
Jul 29 05:58:00 pve pveproxy[5218]: Compilation failed in require at /usr/share/perl5/PVE/API2/Nodes.pm line 59.
Jul 29 05:58:00 pve pveproxy[5218]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Nodes.pm line 59.
Jul 29 05:58:00 pve pveproxy[5218]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 16.
Jul 29 05:58:00 pve pveproxy[5218]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 16.
Jul 29 05:58:00 pve pveproxy[5218]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 13.
Jul 29 05:58:00 pve pveproxy[5218]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 13.
Jul 29 05:58:00 pve pveproxy[5218]: Compilation failed in require at /usr/bin/pveproxy line 11.
Jul 29 05:58:00 pve pveproxy[5218]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 29 05:58:00 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=255/EXCEPTION
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit pveproxy.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 255.
Jul 29 05:58:00 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service has entered the 'failed' state with result 'exit-code'.
Jul 29 05:58:00 pve systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
░░ Subject: A start job for unit pveproxy.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 2475 and the job result is failed.
Jul 29 05:58:00 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 4.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit pveproxy.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jul 29 05:58:00 pve systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
░░ Subject: A stop job for unit pveproxy.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit pveproxy.service has finished.
░░
░░ The job identifier is 2584 and the job result is done.
Jul 29 05:58:00 pve systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
░░ Subject: A start job for unit pveproxy.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has begun execution.
░░
░░ The job identifier is 2584.
Jul 29 05:58:01 pve pveproxy[5221]: syntax error at /usr/share/perl5/PVE/API2/Subscription.pm line 215, near "message"
Jul 29 05:58:01 pve pveproxy[5221]: Global symbol "$no_subscription_info" requires explicit package name (did you forget to declare "my $no_subscript>
Jul 29 05:58:01 pve pveproxy[5221]: Global symbol "$no_subscription_info" requires explicit package name (did you forget to declare "my $no_subscript>
Jul 29 05:58:01 pve pveproxy[5221]: syntax error at /usr/share/perl5/PVE/API2/Subscription.pm line 222, near "if"
Jul 29 05:58:01 pve pveproxy[5221]: Global symbol "$has_permission" requires explicit package name (did you forget to declare "my $has_permission"?) >
Jul 29 05:58:01 pve pveproxy[5221]: Global symbol "$info" requires explicit package name (did you forget to declare "my $info"?) at /usr/share/perl5/>
Jul 29 05:58:01 pve pveproxy[5221]: Global symbol "$info" requires explicit package name (did you forget to declare "my $info"?) at /usr/share/perl5/>
Jul 29 05:58:01 pve pveproxy[5221]: Global symbol "$url" requires explicit package name (did you forget to declare "my $url"?) at /usr/share/perl5/PV>
Jul 29 05:58:01 pve pveproxy[5221]: Global symbol "$info" requires explicit package name (did you forget to declare "my $info"?) at /usr/share/perl5/>
Jul 29 05:58:01 pve pveproxy[5221]: Global symbol "$server_id" requires explicit package name (did you forget to declare "my $server_id"?) at /usr/sh>
Jul 29 05:58:01 pve pveproxy[5221]: Global symbol "$info" requires explicit package name (did you forget to declare "my $info"?) at /usr/share/perl5/>
Jul 29 05:58:01 pve pveproxy[5221]: Global symbol "$info" requires explicit package name (did you forget to declare "my $info"?) at /usr/share/perl5/>
Jul 29 05:58:01 pve pveproxy[5221]: Global symbol "$url" requires explicit package name (did you forget to declare "my $url"?) at /usr/share/perl5/PV>
Jul 29 05:58:01 pve pveproxy[5221]: Global symbol "$info" requires explicit package name (did you forget to declare "my $info"?) at /usr/share/perl5/>
Jul 29 05:58:01 pve pveproxy[5221]: syntax error at /usr/share/perl5/PVE/API2/Subscription.pm line 235, near "}"
Jul 29 05:58:01 pve pveproxy[5221]: /usr/share/perl5/PVE/API2/Subscription.pm has too many errors.
Jul 29 05:58:01 pve pveproxy[5221]: Compilation failed in require at /usr/share/perl5/PVE/API2/Nodes.pm line 59.
Jul 29 05:58:01 pve pveproxy[5221]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Nodes.pm line 59.
Jul 29 05:58:01 pve pveproxy[5221]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 16.
Jul 29 05:58:01 pve pveproxy[5221]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 16.
Jul 29 05:58:01 pve pveproxy[5221]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 13.
Jul 29 05:58:01 pve pveproxy[5221]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 13.
Jul 29 05:58:01 pve pveproxy[5221]: Compilation failed in require at /usr/bin/pveproxy line 11.
Jul 29 05:58:01 pve pveproxy[5221]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Jul 29 05:58:01 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=255/EXCEPTION
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit pveproxy.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 255.
Jul 29 05:58:01 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service has entered the 'failed' state with result 'exit-code'.
Jul 29 05:58:01 pve systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
░░ Subject: A start job for unit pveproxy.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 2584 and the job result is failed.
Jul 29 05:58:01 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit pveproxy.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jul 29 05:58:01 pve systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
░░ Subject: A stop job for unit pveproxy.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit pveproxy.service has finished.
░░
░░ The job identifier is 2693 and the job result is done.
Jul 29 05:58:01 pve systemd[1]: pveproxy.service: Start request repeated too quickly.
Jul 29 05:58:01 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service has entered the 'failed' state with result 'exit-code'.
Jul 29 05:58:01 pve systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
░░ Subject: A start job for unit pveproxy.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 2693 and the job result is failed.
 
bbgeek17 said:
Hi @Th3ddy , it seems like you used one of the methods to "enhance" PVE by removing the subscription nag. I'd recommend to trace your steps back to undo it, or reach out to the publisher for help.

Good luck

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
I confirm that the problem comes from the Subscription.pm file that I modified incorrectly... I corrected it and my server is operational. Thank you
 
You must log in or register to reply here.
Top Bottom