Skip to content

Installing 2.7.0 results in "HTTP code 500" in API #830

Closed

Description

@HovKlan-DH

Describe the bug
After installing the newest 2.7.0 version on my Netgate 4200 then I can no longer control the API and I get HTTP code 500.

To Reproduce
Steps to reproduce the behavior:

  • Make sure I do not have any API installed from previously:
    • pkg-static delete pfSense-pkg-RESTAPI
  • Install newest version for my router with version 25.11-RELEASE (amd64) installed:
    • pkg-static -C /dev/null add https://github.com/pfrest/pfSense-pkg-RESTAPI/releases/latest/download/pfSense-25.11-pkg-RESTAPI.pkg
  • Querying this end-point (which works with previous version): /api/v2/firewall/rule will give this error:

{"code":500,"status":"internal server error","response_id":"ENDPOINT_RECEIVED_UNEXPECTED_ERROR","message":"Undefined constant ``\n#0 \/usr\/local\/pkg\/RESTAPI\/Core\/BaseTraits.inc(56): constant()\n#1 \/usr\/local\/pkg\/RESTAPI\/Core\/Auth.inc(297): RESTAPI\\Core\\Auth::log()\n#2 \/usr\/local\/pkg\/RESTAPI\/Core\/Endpoint.inc(615): RESTAPI\\Core\\Auth::attempt_multi_auth()\n#3 \/usr\/local\/pkg\/RESTAPI\/Core\/Endpoint.inc(1048): RESTAPI\\Core\\Endpoint->check_auth()\n#4 \/usr\/local\/www\/api\/v2\/firewall\/rule\/index.php(9): RESTAPI\\Core\\Endpoint->process_request()\n#5 {main}","data":[]}

pfSense Version & Package Version:

  • API version: 2.7.0
  • Hardware: Netgate 4200 with 25.11-RELEASE (amd64) installed

Activity

  1. changed the title [-]After installing 25.11[/-] [+]After installing 25.11 I get HTTP 500 in API[/+] on Jan 19, 2026
  2. changed the title [-]After installing 25.11 I get HTTP 500 in API[/-] [+]After installing 2.7.0 I get HTTP 500 in API[/+] on Jan 19, 2026
  3. changed the title [-]After installing 2.7.0 I get HTTP 500 in API[/-] [+]Installing 2.7.0 results in "HTTP code 500" in API[/+] on Jan 19, 2026
  4. jaredhendrickson13 commented on Jan 19, 2026

    @jaredhendrickson13
    Member

    Hmm if you go into the REST API settings within the UI and hit save does it start working again?

  5. HovKlan-DH commented on Jan 19, 2026

    @HovKlan-DH
    Author

    Hmm if you go into the REST API settings within the UI and hit save does it start working again?

    Yes, that fixes the problem :-)

  6. jaredhendrickson13 commented on Jan 19, 2026

    @jaredhendrickson13
    Member

    Thanks! Seems like it's not automatically applying defaults for new settings for some, I'll get a patch out for this asap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions