TrueNAS, at a glance.
Tillarr checks that your TrueNAS answers, and always over HTTPS. TrueNAS revokes an API key that arrives over plain HTTP, so Tillarr never offers an http address for it.
TrueNASChecking…Up
AnsweredChecking…Home address · 18 ms
CheckedChecking…Just now
What you see
- Whether it answers, how quickly, and which address answered
- A tap to open its own web page
What's next
After 1.0: a health card, over HTTPS only.
Connect TrueNAS
What to have ready when you add it in Tillarr.
- Its address. Usually https://your-server. Add a remote address too, and Tillarr uses it when home doesn't answer.
- Nothing else. Watching needs no key and no login, so it's free and can't change anything in TrueNAS.
Good to know
- TrueNAS revokes an API key sent over HTTP, which is why Tillarr only uses HTTPS for it.
- Still on TrueNAS's self-signed certificate? Tillarr shows its fingerprint once for you to trust, and checks it on every visit.
How Tillarr checks TrueNAS
Without a key, Tillarr asks for / to see that TrueNAS is up. Every request goes from your device straight to your server, never through us.
Questions
Why does Tillarr require HTTPS for TrueNAS?
TrueNAS revokes an API key it receives over plain HTTP. Requiring HTTPS keeps that from happening.
Does Tillarr show TrueNAS pool health?
Not yet. The first beta watches TrueNAS; a health card is planned after 1.0.
Does Tillarr see TrueNAS's version?
Not yet. The check reads the title of its sign-in page, which doesn't include it.