Unable to access TrueNAS Web UI via hostname (works via IP)

Hi all,

I’m running into a strange issue accessing my TrueNAS Web UI and hoping someone here has seen this before.

Setup / Details:

  • TrueNAS hostname: mlb-nas-pth-003

  • Domain: cedeno.local

  • IP address: 192.168.30.3

  • Web UI via IP: :white_check_mark: Works

    • https://192.168.30.3
  • Web UI via hostname: :cross_mark: Blocked

    • https://mlb-nas-pth-003.cedeno.local

What works:

  • I can ping mlb-nas-pth-003.cedeno.local

  • DNS resolves correctly to 192.168.30.3

  • Other systems on the same domain (e.g. mlb-fw-phy-254.cedeno.local) are accessible via hostname without any issues

Error received in browser:

Website Blocked. This website has been blocked by your network administrator.

Things I’ve checked / considered:

  • DNS resolution looks correct

  • No issues accessing other hosts via hostname

  • Accessing TrueNAS directly by IP works perfectly

At this point I’m wondering if this could be:

  • A browser security / DNS filtering issue

  • Something related to TrueNAS middleware, certificates, or hostname validation

  • A firewall / DNS filtering rule behaving differently for this host

Has anyone run into something similar with TrueNAS and hostnames? Any ideas on where to look next would be greatly appreciated.

Thanks in advance!

I’d turn off https mode or access it via port 80 instead. It’s gonna be using a self signed cert and browsers can be picky about that.

My Nas is behind a reverse proxy being served a true https certificate and that works for me. But if the reverse proxy is offline I use the regular http address.

1 Like