Overview 💥
The Liongard PFSense Inspector relies on supported API endpoints and system components to retrieve configuration and security data from PFSense devices.
However, PFSense firmware 2.2 is significantly outdated, end-of-life, and not compatible with the Inspector’s current requirements. As a result, you may see symptoms such as:
Missing objects or incomplete records
Blank inspector sections
Partial or inconsistent data returns
Continuous inspection failures
This guide provides detailed troubleshooting steps, best practices, and support guidance to fully resolve issues related to PFSense firmware 2.2.
Why This Happens? 🤔
Firmware 2.2 is missing or contains deprecated API endpoints required by Liongard.
The device:
Does not expose expected command output structures
Uses older libraries incompatible with Inspector parsing
Has multiple known bugs fixed in later releases
Is no longer supported by Netgate or Liongard
Does not meet security, API, or SSH interaction requirements
Because of this, the Inspector cannot retrieve expected data, resulting in missing or partial output.
✔ Root Causes Summary
Root Cause Category | Description |
Unsupported firmware | PFSense 2.2 is end-of-life and missing required API/CLI functionality. |
Outdated backend libraries | System utilities do not produce modern outputs the Inspector relies on. |
Unsupported SSH behavior | Legacy SSH handling causes the Inspector to miss output blocks. |
Deprecated API routes | Later firmware added or fixed API endpoints not present in 2.2. |
Custom configs/plugins | Older plugins may block or alter expected output formats. |
Symptoms 🤒
You may experience one or more of the following:
Inspector lands but most sections show no data
Some data sets (routes, interfaces, firewall rules) completely missing
“No records found” throughout inspector categories
Unexpected errors within inspector logs
Partial completion with heavy gaps
Steps to Resolve 👨💻
1️⃣ Upgrade PFSense Firmware (Required Fix)
Firmware 2.2 is not compatible.
The only resolution is upgrading your device to a modern and supported version.
Recommended versions:
PFSense 2.4.5+
Preferably PFSense 2.6.x or PFSense Plus for long-term support
After upgrading:
Confirm the device boots cleanly
Reboot again if recommended
Validate that all core services initialize correctly
2️⃣ Re-run the Inspector (Preferably in CCDM Mode)
Once firmware is updated:
Open Liongard
Edit into the Inspector
Click Clear Cache + Debug Mode (CCDM)
Run a fresh inspection
This forces Liongard to discard old, cached 2.2 output and retrieve the newly supported data structures.
3️⃣ Validate Credentials & Permissions
Even after upgrading, data may still be missing if:
Wrong credentials were saved
User permissions changed across firmware upgrade
SSH or API access policies were altered
Checklist:
Validation Step | What to Check |
Credentials | Ensure username/password or SSH key is correct |
Permissions | User must have full admin-level access |
SSH/API access | Confirm access methods weren’t disabled during upgrade |
4️⃣ Check for Custom Configurations or Plugins
Old installations often contain leftover packages or scripts.
Verify:
No deprecated addons interfering with API output
No custom firewall rules blocking the Inspector
No scripts modifying CLI output (common on old installations)
5️⃣ Review Inspector Logs
If data is still missing, retrieve logs:
Look for parsing errors
Look for unexpected output formats
Watch for SSH timeouts or missing commands
Generate logs via:
Inspector → Actions → Download Logs
6️⃣ Confirm System Environment
Ensure:
Adequate CPU/RAM
No filesystem corruption
No high CPU load preventing Inspector from reading data
PBFS installations upgraded from extremely old versions may need a clean reinstall.
Common Scenarios & Resolutions 🧑🏫
Scenario | Why It Happens | Fix |
Inspector lands but shows no data | Outdated API output on 2.2 | Firmware upgrade + CCDM run |
Some categories missing (ex: DNS, Firewall rules) | Partial support in 2.2 | Firmware upgrade |
SSH connects but returns unexpected structures | Deprecated command versions | Upgrade + remove custom scripts |
Data missing after upgrade | Credentials/permissions changed | Re-enter credentials + re-run |
Still missing subsets | Plugins interfering | Disable/remove plugins |
Errors persist despite fixes | Cached 2.2 data | CCDM run required |
Best Practices 🌟
To avoid future issues:
Always maintain PFSense on supported firmware
Review firmware release notes for changes impacting API/SSH output
Maintain a dedicated account for Liongard with stable permissions
Document system modifications (packages, scripts, firewall rules)
Re-run CCDM after major network device upgrades
Advanced Verification (Optional but Recommended) 🚀
SSH Version Check
Ensure SSH services run a modern version:
ssh -V
API Call Check (if API-enabled)
curl -k https://<pfsense-ip>/api/v1/system/info
Validate System Health
top df -h dmesg
When to Contact Liongard Support 🦁
If you have:
Upgraded firmware
Re-entered credentials
Performed CCDM run
Confirmed no plugins/custom scripts interfere
Verified logs still show missing/inconsistent data
Then contact Liongard Support with:
Collect Before Submitting Ticket :
Required Data | How to Get It |
Inspector logs | Inspector → Actions → Download Logs |
Firmware version | Dashboard → System Info |
Credential type used | Username/Password or SSH key |
Any custom configuration details | Plugins, custom scripts, firewall changes |
Screenshots | Inspector sections showing missing data |
Providing this ensures a faster resolution.
References 📚
Third-Party Link Disclaimer ‼️
We may reference external third-party resources solely as additional guidance.
Liongard does not own, control, or guarantee the accuracy, security, or reliability of third-party sites. Please use them at your own discretion and risk.