ML
    • Register
    • Login
    • Search
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups

    Solved Proxmo upgrades hung

    IT Discussion
    proxmox proxmox 7 upgrade error certificate
    1
    4
    86
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JaredBusch
      JaredBusch last edited by

      I have 2 PVE 7 systems running at home. Mostly just to have a non-client, non-production, setup handy.

      I could not log in to the web interface of the cluster by FQDN or the direct IP of either unit in the cluster. FQDN did through a cert expired error. So, something is going wrong, as the certificate manager is supposed to handle thing.

      SSH works just. I know the password, confirmed by using it for SSH.

      Things I saw on a google search did not help. So a reboot. Still did not help. So I ran updates from the CLI, not it has been stuck at 98% for 10 minutes on both systems.

      a9490af9-d56c-41e5-a476-96d26c211fef-image.png

      1 Reply Last reply Reply Quote 1
      • JaredBusch
        JaredBusch last edited by

        It finally finished..
        5624900b-cb96-41ee-b8f1-29373e262692-image.png

        While I was waiting, I looked at pvecm status and found out it thought I had 4 nodes (see expected votes), when I only have 2 nodes.

        76a4d9f9-18ba-4fe5-af47-4ea037892bfc-image.png

        I used pvecm expected 2 on both and suddenly the updates moved on and I was able to log in to the web interface immediately.
        d5ecd18f-8e07-4222-afea-0b04d215775c-image.png

        In the web interface, it showed a pve3 and pve4. These were some test setups I did months ago.
        I deleted the nodes from the CLI and everything looks clean again.
        782c49e5-1457-499d-8c58-5afbc3c2efda-image.png

        1 Reply Last reply Reply Quote 0
        • JaredBusch
          JaredBusch last edited by

          When I tried to manually renew the certificate from the command line, it said I have been rate limited.

          [email protected]:~# pvenode acme cert renew
          Loading ACME account details
          Placing ACME order
          Error: POST to https://acme-v02.api.letsencrypt.org/acme/new-order {   "type": "urn:ietf:params:acme:error:rateLimited",   "detail": "Error creating new order :: too many certificates (5) already issued for this exact set of domains in the last 168 hours: pm.daerma.com: see https://letsencrypt.org/docs/rate-limits/",   "status": 429 }
          Task Error: POST to https://acme-v02.api.letsencrypt.org/acme/new-order {   "type": "urn:ietf:params:acme:error:rateLimited",   "detail": "Error creating new order :: too many certificates (5) already issued for this exact set of domains in the last 168 hours: pm.daerma.com: see https://letsencrypt.org/docs/rate-limits/",   "status": 429 }
          
          1 Reply Last reply Reply Quote 1
          • JaredBusch
            JaredBusch last edited by

            Looks like the cert expired in April, so I bet PVE has been hammering ACME.....
            32871168-1371-420a-820b-730a56825a4d-image.png

            1 Reply Last reply Reply Quote 1
            • JaredBusch
              JaredBusch last edited by

              It finally finished..
              5624900b-cb96-41ee-b8f1-29373e262692-image.png

              While I was waiting, I looked at pvecm status and found out it thought I had 4 nodes (see expected votes), when I only have 2 nodes.

              76a4d9f9-18ba-4fe5-af47-4ea037892bfc-image.png

              I used pvecm expected 2 on both and suddenly the updates moved on and I was able to log in to the web interface immediately.
              d5ecd18f-8e07-4222-afea-0b04d215775c-image.png

              In the web interface, it showed a pve3 and pve4. These were some test setups I did months ago.
              I deleted the nodes from the CLI and everything looks clean again.
              782c49e5-1457-499d-8c58-5afbc3c2efda-image.png

              1 Reply Last reply Reply Quote 0
              • Topic has been marked as solved  JaredBusch JaredBusch 
              • First post
                Last post