Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    Fatal Error PHP Acme Certificates in Renew Column

    ACME
    2
    6
    100
    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.
    • J
      jpvonhemel last edited by

      Hello,

      Since updating to 23.01, I am now seeing the following PHP error associated with ACME/Let's Encrypt. I searched around the forum and redmine, but do not see anything like this error reported. Not sure if this is isolated to my system or a wider issue. Appreciate any guidance on this error.

      Thank you very much~!

      Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/acme/acme_certificates.php:261 Stack trace: #0 {main} thrown in /usr/local/www/acme/acme_certificates.php on line 261 PHP ERROR: Type: 1, File: /usr/local/www/acme/acme_certificates.php, Line: 261, Message: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/acme/acme_certificates.php:261 Stack trace: #0 {main} thrown

      1 Reply Last reply Reply Quote 0
      • J
        jpvonhemel last edited by jpvonhemel

        I am using HAProxy for SSL offloading, and noticed that my let's encrypt certificate expires on April 16, 2023, and I have the cron entry checked to renew the certificate. Not sure if HAProxy SSL offloading is part of this issue, so I figured I should note it here.

        1 Reply Last reply Reply Quote 0
        • J
          jpvonhemel last edited by jpvonhemel

          @jpvonhemel Thinking there is a problem with my certificate, but the error has removed the ability for me to delete the certificate and create a new one.

          f45bd6c0-05e1-4679-9b9e-5944399e9aa4-image.png

          1 Reply Last reply Reply Quote 0
          • J
            jpvonhemel last edited by

            Here is the crash report from pfSense. I did a reinstall to 22.04 and restored my backup config and the issue is continuing.

            Crash report begins. Anonymous machine information:

            amd64
            14.0-CURRENT
            FreeBSD 14.0-CURRENT #0 plus-RELENG_23_01-n256037-6e914874a5e: Fri Feb 10 20:30:29 UTC 2023 root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/obj/amd64/VDZvZksF/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBS

            Crash report details:

            PHP Errors:
            [19-Feb-2023 05:33:58 America/Denver] PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/acme/acme_certificates.php:261
            Stack trace:
            #0 {main}
            thrown in /usr/local/www/acme/acme_certificates.php on line 261

            No FreeBSD crash data found.

            1 Reply Last reply Reply Quote 0
            • K
              kapranos last edited by

              I have the same proble as you, I can not delete the certificate, I have accessed by SSH and do not see it in the certificate folders, you were able to solve it? thanks

              J 1 Reply Last reply Reply Quote 0
              • J
                jpvonhemel @kapranos last edited by

                @kapranos Sorry to hear, but glad it wasn't just me. Unfortunately my post did not gain any traction with Netgate, so I figured it was a problem unique to me. After a few days of frustration with the unstable upgrade, I nuked the firewall install, installed a clean image and reconfigured the firewall.

                I was able to import most of the settings from backup. For me, that was mostly DCHP reservations, nat and firewall rules, so it wasn't the end of the world. Going foward, I will be more careful with updates and backups. I believe there is a way to leverage the zfs file system to retain and boot from an old install, so I do need to look into that a bit more.

                I honestly do not know how it happened, but chalked it up to some sort of corruption on update or a really odd bug.

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