UI becoming unresponsive 15-30 seconds after login

TrueNAS General
1

Hello! I’m having an odd issue. I’ve got a relatively new install of TrueNAS running in a Proxmox VM. When I log into the web UI, I get maybe 15 to 30 seconds of functionality. The widgets and interface look and function normally. However, after that time period, the widgets stop responding. I tried to include a screenshot, but it won’t let me; multiple widgets have the text: “We are working in the background to generate relevant data. Please try again in a few minutes.”

At this point, navigation through the menus is still possible, but no data loads and no control actions can be taken. It will hang in this state for upwards of two minutes before logging me out and back in again, at which point the UI loads and behaves normally.

My security logout is set for 5 minutes; it isn’t that. (That security logout makes searching for this issue pretty difficult!) Other relevant info:

TrueNAS’ web UI is accessed through Nginx Proxy Manager with a custom local SSL cert. It’s on a management VLAN which is separate from the VLAN my workstation is on, and routing occurs through pfSense firewall rules.

Thanks in advance - hoping someone else has encountered something like this!

2

You have way too much network complexity to diagnose from the forums. If it was bare metal, I would say connect the TrueNAS management NIC directly to a management computer and see if the issue still occurs. Bypassing NPM, firewall and VLANs.

Are you having any issues with the NAS functions or is this just the web GUI? You can also try logging in over SSH for some diag

If you are 100% sure this isn’t network related, you can download a current System Configuration and do a fresh install over the boot-pool and reload the System Configuration.

3

The NAS functionality seems to continue uninterrupted during these issues - it’s only the WebUI that is misbehaving. I can’t easily connect directly to the VM, but I can move the TrueNAS management interface over so that it’s on the same VLAN and access it by IP. That’ll cut out the VLANs, routing, and NPM - thanks for the suggestion, I’ll give that a shot.