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

    updated package, php error when accessing certificates tab

    Scheduled Pinned Locked Moved ACME
    3 Posts 2 Posters 14 Views 2 Watching
    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.
    • B Offline
      Burn3r
      last edited by

      Tried updating certificate via acme and it failed. So I updated the package and then I started getting crash reports so I updated the OS to 25.07.01 and still getting crash reports whenever I attempt to open "certificates" under system on the GUI.

      Crash report begins. Anonymous machine information:

      arm64
      15.0-CURRENT
      FreeBSD 15.0-CURRENT #1 plus-RELENG_25_07_1-n256513-49844af35a5d: Fri Aug 15 19:23:38 UTC 2025 root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-25_07_1-main/obj/aarch64/1qUIUnwj/var/jenkins/workspace/pfSense-Plus-snapshots-25_07_1-main/sourc

      Crash report details:

      PHP Errors:
      PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/system_camanager.php:443
      Stack trace:
      #0 {main}
      thrown in /usr/local/www/system_camanager.php on line 443

      No FreeBSD crash data found.

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG Offline
        Gertjan @Burn3r
        last edited by

        @Burn3r

        First, make a 'manual' backup of your config, here : Diagnostics > Backup & Restore

        Then : a precaution : Go here : /tmp/acme/[your-cert-name] and get a copy of the file named "acme_issuecert.log" as this file contains what happened when - thus telling you what went wrong and why if the issue was acme related. Something I doubt.
        You have get a copy of this log file, as a reboot will clean out the /tmp/ folder.

        Then, Diagnostics > Configuration History, and restore a save backup from just before the issue started.
        pfSense will most probably restart, and you'll be good.

        What for "what happened" part.

        Can you confirm that this https://github.com/pfsense/pfsense/blob/7a44ce9bb635699139f9ee04c2b8c9bf978f17dd/src/usr/local/www/system_camanager.php#L443 is the same line as your file /usr/local/www/system_camanager.php line 443 ?
        I guess it is, as, like me, you use pfSense 25.07.1.

        Open the config.xml file you've backed up. Use a editor like Notepad++.
        Look for the first occurrence of

        <cert>
        

        which has only one tab in front of it.
        Like here :

        1eaa3293-5aa4-403c-abb2-1513cbacec5c-image.png

        Check that every <cert> ... </cert> block has a <refid>xxxxxxxxx</refid>.
        There are as many <cert> ... </cert> as you have Certificates (this page : System > Certificates > Certificates )
        Your issue was : one of them is missing this <refid> ?

        Btw : you can also check the <ca> ... </ca> section, these also have to have a <refid> also.

        If doubt, paste them all here - you can remove the <cert> ...</cert> and <prv> ... </prv> lines.

        Btw : I use the pfSense acme.sh package 1.0 also, no issues what so ever.

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        B 1 Reply Last reply Reply Quote 0
        • B Offline
          Burn3r @Gertjan
          last edited by

          @Gertjan so I did a restore to backup and was able to get everything working from there. OpenVPN tab was also throwing errors. Not really sure what happened but seems like something didn't upgrade properly.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.