Ping for Truenas Scale server returns 422 error
In all my years of web development I have never once seen a 422 error 😂 but here I am.TL;DR The status ping for my truenas scale server is returning a 422 code. I realise this is more of a truenas related issue but it only gives me this code on Homarr. App Setup - Internal and External url: The url of my truenas dashboard(truenas.local:81/ui/dashboard)
Port 81 because I use traefik on port 80Error Info I checkout the chrome console and opened up the failed ping object and it says it failed with a 422 status code. Content not found? I have copy-pasted the URL from the dashboard I use to access truenas. Most Likely Cause I think the issue is Homarr for some reason not using port 81 in this case. The log specifically says that
truenas.local failed NOT truenas.local:81. This is different to my qbittorrent, which the console says it successfully pinged torrent.local:10095.
Any help would be appreciated 😄
Solution:Jump to solution
The ping still returned 422 though? I ended up fixing it by just changing the internal address to the unsecure ip and port, rather than the traefik/pihole dashboard address
3 Replies
Hey, I run truenas as well and wth is that 422 x)
Try running your machine's IP instead of truenas.local (with the same port)
I think your torrent client is pinged correctly thanks to traefik, but truenas dashboard doesn't go through it
(also, quick advice, use
heavyscript dns -a, it'll give you all the locally resolvable addresses for your services and what port they run on)Turns out I forgot to add the :81 to the end 😛
I copy pasted but my browser must have removed the port 😂
Thx for your help though
I haven't marked it as solved because I'm on mobile at the moment
Solution
The ping still returned 422 though? I ended up fixing it by just changing the internal address to the unsecure ip and port, rather than the traefik/pihole dashboard address