Cannot access TrueNAS through the web interface

TrueNAS General
1

I cannot access TrueNAS through the web interface.

After I enter the IP of the TrueNAS I get black screen with a notice:
“Connecting to TrueNAS … Make sure the TrueNAS system is powered on and connected to the network.”

I have tried on different browsers. And also as a Guest in Google Chrome. And in incognito mode in Google chrome. And also in Firefox. I also cleared the cache of the browsers. I get black screen with a notice.

The server is powered on.

I can ping the server.

I have also tried to forcefully shutdown (unplug) the server and turn it back on. In the meantime the Ping failed and resumed when the server booted.

What else can I do?

I don’t have SSH enabled, so I can’t login that way.

I believe the version is TrueNAS 12.8?

2

Welcome,

Is your browser defaulting to connecting with a HTTPS session (port 443) but the NAS is only set to reply on HTTP (port 80)? Did you ever enable SSL via @Dan’s script or the GUI on your NAS?

3

I’d say you really should have it enabled, but it’s water under the bridge at this point.

What’s showing on the server console? At this point I’m guessing we’re dealing with a failed/failing boot device, but it’s really hard to say without knowing more.

1 Like
4

Yup, if it’s not a HTTP/HTTPS issue then the next logical step is to monitor the boot process and perhaps log in and make necessary changes via the console. I hope @Bostjan can do that!

5

This strikes me as somewhat unlikely, given that something is showing up. If that were the issue, I’d expect a connection error. But definitely not sure here.

6

Attach a monitor and keyboard to it or use IPMI if available to see what the console shows.

7

I attached a monitor and keyboard to it. I was able to log in (console?).

Then I ran these two commands (below) and it helped. After that I could login through the Web UI.

service middlewared restart

service nginx restart
2 Likes
8

Would probably be worth raising a bug for this as middlewared/nginx failing unexpectedly until a service restart is odd (especially seeing as it had seemed to persist through reboot).

1 Like
9

Stumbled upon this topic to troubleshoot the problem. Just happened to me, and it seems related to the experimental containers feature (TrueNAS SCALE 25.10 Goldeye)

I was running a download in a container using the lgogdownloader utility through a tmux session in a ubuntu-resolute container when it happened.

 sudo systemctl status middlewared
× middlewared.service - TrueNAS Middleware
     Loaded: loaded (/lib/systemd/system/middlewared.service; enabled; preset: enabled)
     Active: failed (Result: resources) since Sat 2026-07-18 22:23:33 EDT; 4min 56s ago
   Duration: 2w 4d 9h 57.874s
      Tasks: 10 (limit: 18376)
     Memory: 41.5M
        CPU: 2h 52min 32.346s
     CGroup: /system.slice/middlewared.service
             └─3018489 /usr/bin/incus exec ubuntu-resolute /bin/bash

Jul 18 22:20:33 dxp2800 systemd[1]: middlewared.service: Failed to run 'start' task: Device or resource busy
Jul 18 22:20:33 dxp2800 systemd[1]: Starting middlewared.service - TrueNAS Middleware...
Jul 18 22:22:03 dxp2800 systemd[1]: middlewared.service: State 'stop-sigterm' timed out. Skipping SIGKILL.
Jul 18 22:23:33 dxp2800 systemd[1]: middlewared.service: State 'final-sigterm' timed out. Skipping SIGKILL. Entering failed mode.
Jul 18 22:23:33 dxp2800 systemd[1]: middlewared.service: Failed with result 'resources'.
Jul 18 22:23:33 dxp2800 systemd[1]: middlewared.service: Unit process 3018489 (incus) remains running after unit stopped.
Jul 18 22:23:33 dxp2800 systemd[1]: Failed to start middlewared.service - TrueNAS Middleware.
Jul 18 22:23:33 dxp2800 systemd[1]: middlewared.service: Consumed 2h 52min 32.317s CPU time.

I had to sudo incus list, then sudo incus stop ubuntu-resolute, then sudo systemctl restart middlewared to bring it back.