Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Off Topic
    4. Proxmox
    5. Proxmox WebIf nicht erreichbar

    NEWS

    • Amazon Alexa - ioBroker Skill läuft aus ?

    • Monatsrückblick – September 2025

    • Neues Video "KI im Smart Home" - ioBroker plus n8n

    Proxmox WebIf nicht erreichbar

    This topic has been deleted. Only users with topic management privileges can see it.
    • Negalein
      Negalein Global Moderator @crunchip last edited by

      @crunchip sagte in Proxmox WebIf nicht erreichbar:

      aber wieder verschwinden. Wenn...

      Danke

      ich hab mit nano /etc/network/interfaces das File editiert.

      auto lo
iface lo inet loopback

iface enp0s31f6 inet manual

auto vmbr0
iface vmbr0 inet static
        address 10.0.1.206/23
        gateway 10.0.1.1
        bridge-ports enp0s31f6
        bridge-stp off
        bridge-fd 0

      dann mit systemctl restart pveproxy.service den Service neu gestartet.

      ● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2025-10-12 13:34:15 CEST; 7min ago
    Process: 69400 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=111)
    Process: 69402 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 69403 (pveproxy)
      Tasks: 4 (limit: 18839)
     Memory: 132.8M
        CPU: 9.075s
     CGroup: /system.slice/pveproxy.service
             ├─69403 pveproxy
             ├─69820 pveproxy worker
             ├─69821 pveproxy worker
             └─69822 pveproxy worker

Oct 12 13:42:03 pve pveproxy[69403]: starting 2 worker(s)
Oct 12 13:42:03 pve pveproxy[69403]: worker 69820 started
Oct 12 13:42:03 pve pveproxy[69403]: worker 69821 started
Oct 12 13:42:03 pve pveproxy[69818]: worker exit
Oct 12 13:42:03 pve pveproxy[69820]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 13:42:03 pve pveproxy[69821]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 13:42:03 pve pveproxy[69403]: worker 69818 finished
Oct 12 13:42:03 pve pveproxy[69403]: starting 1 worker(s)
Oct 12 13:42:03 pve pveproxy[69403]: worker 69822 started
Oct 12 13:42:03 pve pveproxy[69822]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.

      ip addr & route -n zeiigt aber noch

      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: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 6c:4b:90:43:c9:19 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 6c:4b:90:43:c9:19 brd ff:ff:ff:ff:ff:ff
    inet 10.0.1.206/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::6e4b:90ff:fe43:c919/64 scope link
       valid_lft forever preferred_lft forever

      Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.0.1.1        0.0.0.0         UG    0      0        0 vmbr0
10.0.1.0        0.0.0.0         255.255.255.0   U     0      0        0 vmbr0
      crunchip 1 Reply Last reply Reply Quote 0
      • Negalein
        Negalein Global Moderator @crunchip last edited by Negalein

        @crunchip

        nach einem reboot zeigt ip addr jetzt die passende IP.

        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: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 6c:4b:90:43:c9:19 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 6c:4b:90:43:c9:19 brd ff:ff:ff:ff:ff:ff
    inet 10.0.1.206/23 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::6e4b:90ff:fe43:c919/64 scope link
       valid_lft forever preferred_lft forever

        aber https://10.0.1.206:8006/ geht trotzdem noch nicht. 😞

        dann hab ich mit nano /etc/network/interfaces:auto vmbr0 ein neues File erstellt.

        iface vmbr0 inet static
address 10.0.1.206/23
gateway 10.0.1.1
bridge-ports enp0s31f6
bridge-stp off
bridge-fd 0

        ● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2025-10-12 13:59:51 CEST; 3s ago
    Process: 1524 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=111)
    Process: 1525 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 1527 (pveproxy)
      Tasks: 4 (limit: 18839)
     Memory: 132.7M
        CPU: 943ms
     CGroup: /system.slice/pveproxy.service
             ├─1527 pveproxy
             ├─1528 pveproxy worker
             ├─1529 pveproxy worker
             └─1530 pveproxy worker

Oct 12 13:59:50 pve pvecm[1524]: Unable to load access control list: Connection refused
Oct 12 13:59:51 pve pveproxy[1527]: starting server
Oct 12 13:59:51 pve pveproxy[1527]: starting 3 worker(s)
Oct 12 13:59:51 pve pveproxy[1527]: worker 1528 started
Oct 12 13:59:51 pve pveproxy[1527]: worker 1529 started
Oct 12 13:59:51 pve pveproxy[1527]: worker 1530 started
Oct 12 13:59:51 pve pveproxy[1528]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 13:59:51 pve systemd[1]: Started PVE API Proxy Server.
Oct 12 13:59:51 pve pveproxy[1529]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 13:59:51 pve pveproxy[1530]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.

        funktioniert aber auch nicht

        crunchip 1 Reply Last reply Reply Quote 0
        • crunchip
          crunchip Forum Testing Most Active @Negalein last edited by

          @negalein sagte in Proxmox WebIf nicht erreichbar:

          ip addr & route -n zeiigt aber noch

          Weil du nur den proxy und nicht den Netzwerkdienst neu gestartet hast.

          @negalein sagte in Proxmox WebIf nicht erreichbar:

          aber https://10.0.1.206:8006/ geht trotzdem noch nicht.

          🤔
          Ist die 206 auch frei, oder Vllt schon anderweitig belegt?

          Gibt's im LOG etwas zu sehen? Ist die Fehlermeldung von oben noch vorhanden?

          Möglichkeit wäre noch testhalber von statisch auf DHCP stellen um eventuelle Fehler auszuschließen.

          Negalein 1 Reply Last reply Reply Quote 0
          • crunchip
            crunchip Forum Testing Most Active @Negalein last edited by

            @negalein sagte in Proxmox WebIf nicht erreichbar:

            failed to load local private

            Dann mal doch die etc/hosts anschauen

            1 Reply Last reply Reply Quote 0
            • Negalein
              Negalein Global Moderator @crunchip last edited by

              @crunchip sagte in Proxmox WebIf nicht erreichbar:

              Weil du nur den proxy und nicht den Netzwerkdienst neu gestartet hast.

              ah, deshalb.
              Nach reboot hat er die richtige IP gehabt.
              Aber GUI geht nicht.

              Ist die 206 auch frei, oder Vllt schon anderweitig belegt?

              Ja, definitiv frei

              Gibt's im LOG etwas zu sehen?

              wo find ich das?

              Ist die Fehlermeldung von oben noch vorhanden?

              Ja

              Möglichkeit wäre noch testhalber von statisch auf DHCP stellen um eventuelle Fehler auszuschließen.

              in der /etc/network/interfaces:auto?

              
iface vmbr0 inet DHCP
address 10.0.1.206/23
gateway 10.0.1.1
bridge-ports enp0s31f6
bridge-stp off
bridge-fd 0

              so?

              etc/hosts

              127.0.0.1 localhost.localdomain localhost
10.0.1.206 proxmox-3.fritz.box

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
              crunchip 2 Replies Last reply Reply Quote 0
              • crunchip
                crunchip Forum Testing Most Active @Negalein last edited by

                @negalein moment, ich geh gleich mal an den Rechner, vom Handy is das immer etwas umständlich.

                1 Reply Last reply Reply Quote 1
                • crunchip
                  crunchip Forum Testing Most Active last edited by crunchip

                  @negalein sagte in Proxmox WebIf nicht erreichbar:

                  wo find ich das

                  wie üblich in var/log

                  /var/log/: Enthält eine Vielzahl von Systemprotokollen, darunter:
syslog: Allgemeine Systemmeldungen.
auth.log: Authentifizierungsereignisse.
syslog-ng: Protokolldateien von Syslog-ng (falls konfiguriert).
apt/history.log: Zeigt die History von Paketinstallationen an.
/var/log/pve/: Enthält Proxmox-spezifische Logs.
/var/log/messages/: Enthält eine Auswahl von Systemmeldungen.

                  allerdings seit proxmox v8(debian12)
                  abruf mit
                  z.b.

                  journalctl -f

                  speziell proxy

                  journalctl -u pveproxy

                  @negalein sagte in Proxmox WebIf nicht erreichbar:

                  so?

                  auto vmbr0
iface vmbr0 inet dhcp
    bridge-ports enp0s31f6
    bridge-stp off
    bridge-fd 0

                  edit
                  möglichkeit wäre noch

                  GUI per CLI wieder aktivieren: Falls die Netzumstellungen zu Problemen geführt haben, kann per CLI ein Reset oder eine Reparatur versucht werden:

                  systemctl restart pve-manager

                  oder

                  apt-get install --reinstall pve-manager

                  und dann Logs auf Fehler kontrollieren.

                  edit2

                  SSL-Zertifikate defekt: Ein defektes Zertifikat kann die Weboberfläche blockieren. Prüfe Logs auf Fehler zu SSL oder Zertifikat.​

Browser-Cache oder HTTPS erzwingen: Lösche den Browser-Cache oder teste mit einem anderen Browser.
                  Negalein 2 Replies Last reply Reply Quote 0
                  • Negalein
                    Negalein Global Moderator @crunchip last edited by

                    @crunchip sagte in Proxmox WebIf nicht erreichbar:

                    systemctl restart pve-manager

                    Failed to restart pve-manager.service: Operation refused, unit pve-guests.service may be requested by dependency only (it is configured to refuse manual start/stop).
See system logs and 'systemctl status pve-manager.service' for details.

                    ct 12 14:53:51 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Oct 12 14:53:51 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Oct 12 14:53:52 pve pveproxy[3628]: worker exit
Oct 12 14:53:52 pve pveproxy[890]: worker 3628 finished
Oct 12 14:53:52 pve pveproxy[890]: starting 1 worker(s)
Oct 12 14:53:52 pve pveproxy[890]: worker 3632 started
Oct 12 14:53:52 pve pveproxy[3629]: worker exit
Oct 12 14:53:52 pve pveproxy[3630]: worker exit
Oct 12 14:53:52 pve pveproxy[3632]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 14:53:52 pve pveproxy[890]: worker 3629 finished
Oct 12 14:53:52 pve pveproxy[890]: starting 1 worker(s)
Oct 12 14:53:52 pve pveproxy[890]: worker 3633 started
Oct 12 14:53:52 pve pveproxy[890]: worker 3630 finished
Oct 12 14:53:52 pve pveproxy[890]: starting 1 worker(s)
Oct 12 14:53:52 pve pveproxy[890]: worker 3634 started
Oct 12 14:53:52 pve pveproxy[3633]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 14:53:52 pve pveproxy[3634]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 14:53:55 pve pmxcfs[3631]: [main] crit: Unable to get local IP address
Oct 12 14:53:55 pve pmxcfs[3631]: [main] crit: Unable to get local IP address
Oct 12 14:53:55 pve systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Oct 12 14:53:55 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Oct 12 14:53:55 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Oct 12 14:53:55 pve systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped.
Oct 12 14:53:55 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 676.
Oct 12 14:53:55 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Oct 12 14:53:55 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Oct 12 14:53:57 pve pveproxy[3632]: worker exit
Oct 12 14:53:57 pve pveproxy[890]: worker 3632 finished
Oct 12 14:53:57 pve pveproxy[890]: starting 1 worker(s)
Oct 12 14:53:57 pve pveproxy[890]: worker 3641 started
Oct 12 14:53:57 pve pveproxy[3633]: worker exit
Oct 12 14:53:57 pve pveproxy[3634]: worker exit
Oct 12 14:53:57 pve pveproxy[3641]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 14:53:57 pve pveproxy[890]: worker 3633 finished
Oct 12 14:53:57 pve pveproxy[890]: starting 1 worker(s)
Oct 12 14:53:57 pve pveproxy[890]: worker 3642 started
Oct 12 14:53:57 pve pveproxy[890]: worker 3634 finished
Oct 12 14:53:57 pve pveproxy[890]: starting 1 worker(s)
Oct 12 14:53:57 pve pveproxy[890]: worker 3643 started
Oct 12 14:53:57 pve pveproxy[3642]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 14:53:57 pve pveproxy[3643]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 14:53:59 pve pmxcfs[3635]: [main] crit: Unable to get local IP address
Oct 12 14:53:59 pve pmxcfs[3635]: [main] crit: Unable to get local IP address
Oct 12 14:53:59 pve systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Oct 12 14:53:59 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Oct 12 14:53:59 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Oct 12 14:53:59 pve systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped.
Oct 12 14:53:59 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 677.
Oct 12 14:53:59 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Oct 12 14:53:59 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Oct 12 14:54:01 pve cron[843]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Oct 12 14:54:02 pve pveproxy[3641]: worker exit
Oct 12 14:54:02 pve pveproxy[890]: worker 3641 finished
Oct 12 14:54:02 pve pveproxy[890]: starting 1 worker(s)
Oct 12 14:54:02 pve pveproxy[890]: worker 3646 started
Oct 12 14:54:02 pve pveproxy[3642]: worker exit
Oct 12 14:54:02 pve pveproxy[3646]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 14:54:02 pve pveproxy[3643]: worker exit
Oct 12 14:54:02 pve pveproxy[890]: worker 3642 finished
Oct 12 14:54:02 pve pveproxy[890]: starting 1 worker(s)
Oct 12 14:54:02 pve pveproxy[890]: worker 3647 started
Oct 12 14:54:02 pve pveproxy[890]: worker 3643 finished
Oct 12 14:54:02 pve pveproxy[890]: starting 1 worker(s)
Oct 12 14:54:02 pve pveproxy[890]: worker 3648 started
Oct 12 14:54:02 pve pveproxy[3647]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 14:54:02 pve pveproxy[3648]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 14:54:03 pve pmxcfs[3644]: [main] crit: Unable to get local IP address
Oct 12 14:54:03 pve pmxcfs[3644]: [main] crit: Unable to get local IP address
Oct 12 14:54:03 pve systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Oct 12 14:54:03 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Oct 12 14:54:03 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Oct 12 14:54:03 pve systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped.
Oct 12 14:54:04 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 678.
Oct 12 14:54:04 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Oct 12 14:54:04 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Oct 12 14:54:07 pve pveproxy[3646]: worker exit
Oct 12 14:54:07 pve pveproxy[890]: worker 3646 finished
Oct 12 14:54:07 pve pveproxy[890]: starting 1 worker(s)
Oct 12 14:54:07 pve pveproxy[890]: worker 3650 started
Oct 12 14:54:07 pve pveproxy[3647]: worker exit
Oct 12 14:54:07 pve pveproxy[3650]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 14:54:07 pve pveproxy[3648]: worker exit
Oct 12 14:54:07 pve pveproxy[890]: worker 3647 finished
Oct 12 14:54:07 pve pveproxy[890]: starting 1 worker(s)
Oct 12 14:54:07 pve pveproxy[890]: worker 3651 started
Oct 12 14:54:07 pve pveproxy[890]: worker 3648 finished
Oct 12 14:54:07 pve pveproxy[890]: starting 1 worker(s)
Oct 12 14:54:07 pve pveproxy[890]: worker 3652 started
Oct 12 14:54:07 pve pveproxy[3651]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 14:54:07 pve pveproxy[3652]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 14:54:08 pve pmxcfs[3649]: [main] crit: Unable to get local IP address
Oct 12 14:54:08 pve pmxcfs[3649]: [main] crit: Unable to get local IP address
Oct 12 14:54:08 pve systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Oct 12 14:54:08 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Oct 12 14:54:08 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Oct 12 14:54:08 pve systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped.
Oct 12 14:54:08 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 679.
Oct 12 14:54:08 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Oct 12 14:54:08 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Oct 12 14:54:12 pve pveproxy[3650]: worker exit
Oct 12 14:54:12 pve

                    systemctl status pve-manager.service

                    ● pve-guests.service - PVE guests
     Loaded: loaded (/lib/systemd/system/pve-guests.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sun 2025-10-12 14:04:14 CEST; 53min ago
    Process: 899 ExecStartPre=/usr/share/pve-manager/helpers/pve-startall-delay (code=exited, status=0/SUCCESS)
    Process: 900 ExecStart=/usr/bin/pvesh --nooutput create /nodes/localhost/startall (code=exited, status=111)
   Main PID: 900 (code=exited, status=111)
        CPU: 747ms

Oct 12 14:04:13 pve systemd[1]: Starting PVE guests...
Oct 12 14:04:14 pve pvesh[900]: ipcc_send_rec[1] failed: Connection refused
Oct 12 14:04:14 pve pvesh[900]: ipcc_send_rec[2] failed: Connection refused
Oct 12 14:04:14 pve pvesh[900]: ipcc_send_rec[3] failed: Connection refused
Oct 12 14:04:14 pve pvesh[900]: Unable to load access control list: Connection refused
Oct 12 14:04:14 pve systemd[1]: pve-guests.service: Main process exited, code=exited, status=111/n/a
Oct 12 14:04:14 pve systemd[1]: pve-guests.service: Failed with result 'exit-code'.
Oct 12 14:04:14 pve systemd[1]: Failed to start PVE guests.
                    crunchip 1 Reply Last reply Reply Quote 0
                    • Negalein
                      Negalein Global Moderator @crunchip last edited by

                      @crunchip sagte in Proxmox WebIf nicht erreichbar:

                      apt-get install --reinstall pve-manager

                      Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Reinstallation of pve-manager is not possible, it cannot be downloaded.
0 upgraded, 0 newly installed, 0 to remove and 161 not upgraded.
                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • crunchip
                        crunchip Forum Testing Most Active @Negalein last edited by

                        @negalein sagte in Proxmox WebIf nicht erreichbar:

                        pve-ssl.key: failed

                        dann mach mal

                        pvecm updatecerts -f
systemctl restart pveproxy

                        Prüfe, ob die IP angezeigt wird mit hostname -I

                        Negalein 1 Reply Last reply Reply Quote 0
                        • Thomas Braun
                          Thomas Braun Most Active @Negalein last edited by

                          @negalein sagte in Proxmox WebIf nicht erreichbar:

                          and 161 not upgraded.

                          Pfleg die Kiste. Da hängt einiges in der Pipeline.

                          Negalein 1 Reply Last reply Reply Quote 1
                          • Negalein
                            Negalein Global Moderator @crunchip last edited by

                            @crunchip sagte in Proxmox WebIf nicht erreichbar:

                            pvecm updatecerts -f

                            ipcc_send_rec[1] failed: Connection refused
ipcc_send_rec[2] failed: Connection refused
ipcc_send_rec[3] failed: Connection refused
Unable to load access control list: Connection refused

                            hostname -I

                            10.0.1.206

                            @thomas-braun sagte in Proxmox WebIf nicht erreichbar:

                            Pfleg die Kiste. Da hängt einiges in der Pipeline.

                            I know!
                            die lag monatelang in der Schublade.
                            Wird sofort erledigt, sobald wieder alles läuft.

                            Thomas Braun crunchip 2 Replies Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @Negalein last edited by

                              @negalein sagte in Proxmox WebIf nicht erreichbar:

                              Wird sofort erledigt, sobald wieder alles läuft.

                              Ich würde das ja andersherum angehen.
                              ZUERST die Basis klar kriegen und erst DANACH die darauf aufbauenden Dinge konfigurieren.

                              Negalein crunchip 2 Replies Last reply Reply Quote 0
                              • crunchip
                                crunchip Forum Testing Most Active @Negalein last edited by

                                @negalein sagte in Proxmox WebIf nicht erreichbar:

                                ipcc_send_rec[1] failed: Connection refused ipcc_send_rec[2] failed: Connection refused ipcc_send_rec[3] failed: Connection refused Unable to load access control list: Connection refused

                                systemctl status pve-cluster
systemctl restart pve-cluster
journalctl -u pve-cluster -b --no-pager | tail -40
                                Negalein 1 Reply Last reply Reply Quote 0
                                • Negalein
                                  Negalein Global Moderator @Thomas Braun last edited by

                                  @thomas-braun sagte in Proxmox WebIf nicht erreichbar:

                                  Ich würde das ja andersherum angehen.

                                  gerade dabei 🙂

                                  1 Reply Last reply Reply Quote 0
                                  • crunchip
                                    crunchip Forum Testing Most Active @Thomas Braun last edited by

                                    @thomas-braun wird aber schwierig ohne funktionierendes Netzwerk

                                    Thomas Braun 1 Reply Last reply Reply Quote 0
                                    • Thomas Braun
                                      Thomas Braun Most Active @crunchip last edited by

                                      @crunchip sagte in Proxmox WebIf nicht erreichbar:

                                      ohne funktionierendes Netzwerk

                                      Grundsätzlich scheint doch da was zu sein.
                                      Sonst hätte apt-get ja nicht ausrechnen können, das 161 Pakete zum Update anstehen.

                                      crunchip uweklatt 2 Replies Last reply Reply Quote 0
                                      • crunchip
                                        crunchip Forum Testing Most Active @Thomas Braun last edited by

                                        @thomas-braun ja, aber gewisse Dinge können dann aber nicht umgesetzt werden bzw bestimmte Befehle nicht auf Proxmoxebene ausgeführt werden, solange der Proxmox Cluster-Dienst bzw. Corosync nicht laufen, deshalb greifen auch die obigen Befehle nicht

                                        1 Reply Last reply Reply Quote 0
                                        • Negalein
                                          Negalein Global Moderator @crunchip last edited by

                                          @crunchip sagte in Proxmox WebIf nicht erreichbar:

                                          systemctl status pve-cluster

                                          ● pve-cluster.service - The Proxmox VE cluster filesystem
     Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
     Active: activating (start) since Sun 2025-10-12 15:27:11 CEST; 1ms ago
Cntrl PID: 930 (pmxcfs)
      Tasks: 1 (limit: 18839)
     Memory: 128.0K
        CPU: 199us
     CGroup: /system.slice/pve-cluster.service
             └─930 /usr/bin/pmxcfs

Oct 12 15:27:11 pve systemd[1]: Starting The Proxmox VE cluster filesystem...

                                          systemctl restart pve-cluster

                                          Job for pve-cluster.service failed because the control process exited with error code.
See "systemctl status pve-cluster.service" and "journalctl -xe" for details.

                                          journalctl -xe

                                          ░░ The job identifier is 8927 and the job result is done.
Oct 12 15:30:03 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
░░ Subject: A start job for unit pve-cluster.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pve-cluster.service has begun execution.
░░
░░ The job identifier is 8927.
Oct 12 15:30:07 pve pmxcfs[1084]: [main] crit: Unable to get local IP address
Oct 12 15:30:07 pve pmxcfs[1084]: [main] crit: Unable to get local IP address
Oct 12 15:30:07 pve systemd[1]: pve-cluster.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 pve-cluster.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 255.
Oct 12 15:30:07 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pve-cluster.service has entered the 'failed' state with result 'exit-code'.
Oct 12 15:30:07 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
░░ Subject: A start job for unit pve-cluster.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pve-cluster.service has finished with a failure.
░░
░░ The job identifier is 8927 and the job result is failed.
Oct 12 15:30:07 pve systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped.
░░ Subject: A start job for unit corosync.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit corosync.service has finished successfully.
░░
░░ The job identifier is 8930.
Oct 12 15:30:07 pve pveproxy[1081]: worker exit
Oct 12 15:30:07 pve pveproxy[1082]: worker exit
Oct 12 15:30:07 pve pveproxy[889]: worker 1081 finished
Oct 12 15:30:07 pve pveproxy[889]: starting 1 worker(s)
Oct 12 15:30:07 pve pveproxy[889]: worker 1082 finished
Oct 12 15:30:07 pve pveproxy[889]: worker 1085 started
Oct 12 15:30:07 pve pveproxy[1083]: worker exit
Oct 12 15:30:07 pve pveproxy[1085]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 15:30:07 pve pveproxy[889]: worker 1083 finished
Oct 12 15:30:07 pve pveproxy[889]: starting 2 worker(s)
Oct 12 15:30:07 pve pveproxy[889]: worker 1086 started
Oct 12 15:30:07 pve pveproxy[889]: worker 1087 started
Oct 12 15:30:07 pve pveproxy[1086]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 15:30:07 pve pveproxy[1087]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1917.
Oct 12 15:30:08 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 22.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit pve-cluster.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Oct 12 15:30:08 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
░░ Subject: A stop job for unit pve-cluster.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit pve-cluster.service has finished.
░░
░░ The job identifier is 9103 and the job result is done.
Oct 12 15:30:08 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
░░ Subject: A start job for unit pve-cluster.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pve-cluster.service has begun execution.
░░
░░ The job identifier is 9103.
                                          crunchip 1 Reply Last reply Reply Quote 0
                                          • uweklatt
                                            uweklatt @Thomas Braun last edited by

                                            Wenn man die Netzwerkmaske ändert, sollte es bei allen Geräten im zugehörigen Netzwerk identisch eingestellt werden. Danach den Netzwerkstack neu starten (z.B. mit einem Reboot).
                                            Sind ALLE Beteiligten Geräte umgestellt?

                                            Tschau
                                            Uwe

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            961
                                            Online

                                            32.3k
                                            Users

                                            81.1k
                                            Topics

                                            1.3m
                                            Posts

                                            5
                                            70
                                            1340
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo