FireGlance · FAQ
Questions, answered.
Straight answers about FireGlance 1.0. Still stuck? See support or write to [email protected].
Connection
FireGlance can't connect. What do I check first?
Install the pfSense REST API package (pfREST) on the firewall: pfSense has no built-in REST API, and the package isn't in the Package Manager, so install it from the firewall shell with the command for your pfSense version at pfrest.org. Reinstall it after every pfSense upgrade. Use the same host and port as the webConfigurator with Use HTTPS on, be on the firewall's network or VPN, allow Local Network access, then tap Test Connection: it tells you exactly what failed.
It says HTTPS required.
FireGlance never sends your API key or password over plain HTTP. Turn on Use HTTPS for the firewall (the webConfigurator uses HTTPS on port 443 by default) and test again.
Authentication failed, or permission denied.
Authentication failed means the key or password was rejected: create a new key in the webConfigurator under System, REST API, Keys. Permission denied means the key works but the user lacks REST API read privileges.
Certificates and keys
It says the certificate isn't trusted and shows a fingerprint.
That's normal: pfSense usually runs a self-signed certificate. Compare the SHA-256 fingerprint with the one on the firewall (System, Certificates), then tap Trust This Certificate. FireGlance then accepts only that exact certificate for that firewall.
The certificate changed and FireGlance refuses to connect.
This protects you from interception. If you replaced the certificate yourself, open Settings, Firewalls, tap the sliders icon, tap Remove pinned certificate, then test again and approve the new fingerprint. This also applies if you switch the firewall to a publicly trusted certificate, for example from ACME.
Where is my API key or password stored?
In the iOS Keychain on this iPhone, one entry per firewall. It is sent only to that firewall, only over HTTPS. Deleting a firewall in FireGlance deletes its key.
Alerts and widgets
How do alerts work, and why are they late?
Alerts are part of Pro; turn them on in Settings, Alerts. While the app is open it checks every 5 seconds. When it is closed, iOS decides when FireGlance may check: at most every 15 minutes, and often less. Each background check looks at the firewall you have selected, and your iPhone must be able to reach it. An alert stays active until FireGlance sees the firewall healthy again, so there is no recovery notice while it can't reach the firewall. Demo mode never sends notifications.
Why does the widget show 0 throughput?
After a background check the throughput figures show 0, because one check can't measure a rate. The medium widget shows an as-of time, and the small one shows it when the data is old; open the app for live throughput.
Purchases and privacy
What is free and what is Pro?
FireGlance is free for one firewall, with the full dashboard, interfaces, gateways, services and DHCP leases. Pro is a one-time $9.99 purchase (the App Store shows your local price), never a subscription, and adds multiple firewalls, the log viewer, Home Screen widgets and alerts.
How do I restore Pro?
Use the Apple Account you bought with. Open Settings, Pro, See what's in Pro, and tap Restore Purchases. When it works, Settings shows Pro unlocked.
Does Pro work with Family Sharing?
No. FireGlance Pro is not shared through Family Sharing; each Apple Account buys its own.
What happens after a refund?
Refunds are handled by Apple at reportaproblem.apple.com. Your saved firewalls and settings stay on your iPhone, and Pro features lock until you buy or restore Pro.
Does FireGlance change my firewall or collect my data?
No. FireGlance only reads. It has no account, analytics or server of ours. To delete everything, delete each firewall in Settings (this removes its key), then delete the app.
Coming soon
FireGlance is heading to the App Store.
Drop a line and I'll tell you the day it lands.
FireGlance is an independent project and is not affiliated with, endorsed by, or supported by Netgate. "pfSense" is a registered trademark of Rubicon Communications, LLC (Netgate), used here only to describe compatibility. The pfSense REST API package ("pfREST") is an independent open-source project by its own authors.