My Truenas EE 24.10.2.2 was previously upgraded from core and eventually to EE. Today after creating a script I tried to login to the GUI but it wouldn’t accept my u/pw. I rebooted and then got a grub error. So I reinstall the same version of EE from a USB and then uploaded my config. That prevented me from getting into the GUI as I’m running NPM and change Truenas to port 83 and 7443. ChatGPT had me do alot of things including editing my nginx.conf file to comment the ssl cert and another server line ::80 (not sure exactly). After getting into the GUI I couldn’t save setting as a key was missing (root user from old config) tried to create a new user truenas_admin but couldn’t get the ultimate privleges for it. Not sure how to proceed. Any advice would be great.
I’d probably start with “fresh install, then upload your saved config file,” to undo whatever ChatGPT told you to do (particularly since you don’t seem to remember it in any detail). Then, you should be able to bypass NPM by browsing to http://truenas_IP:83. Start there, and if you can’t log in, share what exactly happens.
Thanks Dan. I had installed EE from scratch originally and then couldn’t get into the GUI after I uploaded my recent config. I’m sure I’ll have the same problem. Any thoughts on how to proceed after the config is uploaded? Browsing to http://truenas_iP:83 didn’t work and https://truenas_ip:7443 and https://truenas.mydomain.com (from NPM) didn’t work either.
Without some detail about what “didn’t work” means, none. All that tells me is that what you expected it to do, and what it actually did, aren’t the same thing.
Got this server could not be reached errors. And other docker containers gave 502 error.
Started from scratch and installed the same version of EE 24.10.2.2 from a USB. Changed the password and gave thru the console a nameserver of 8.8.8.8 and gateway of 192.168.5.1 my router. Then CLI shows an IP of 192.168.5.100. I can’t access through my browser as I get this site cannot be reached. Trying to ping 192.168.5.100 from my desktop on the same network I get all packets lost.
Ok Installed from scratch and config uploaded. Now I get this site can’t be reached at http://truenasip:83, https://truenasip:7443 and http://truenasip . Can ping the truenas ip from my desktop. CLI says it can be reached at http://truenasip:83. Can access NPM and other docker container with IP:Port but not the truenas GUI.
Ordinarily you’d be using NPM to access your docker containers by name–does that work? Can you access the TrueNAS GUI through NPM?
Can you SSH to the server? Is nginx running (systemctl status nginx)? The middleware (systemctl status middlewared)?
Welcome to FreeNAS
root@freenasSuper:~# systemctl status nginx
× nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; preset: enabled)
Drop-In: /etc/systemd/system/nginx.service.d
└─override.conf
Active: failed (Result: exit-code) since Sat 2026-01-03 19:39:06 EST; 11h ago
Docs: man:nginx(8)
CPU: 13msJan 03 19:39:05 freenasSuper systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server…
Jan 03 19:39:05 freenasSuper nginx[9455]: 2026/01/03 19:39:05 [emerg] 9455#9455: cannot load certificate key “/etc/certificates/truenas_default.key”: BIO_new_file() failed (SSL: error:80000002:system library::No such file or directory:>
Jan 03 19:39:05 freenasSuper nginx[9455]: nginx: configuration file /etc/nginx/nginx.conf test failed
Jan 03 19:39:06 freenasSuper systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Jan 03 19:39:06 freenasSuper systemd[1]: nginx.service: Failed with result ‘exit-code’.
Jan 03 19:39:06 freenasSuper systemd[1]: Failed to start nginx.service - A high performance web server and a reverse proxy server.
Jan 03 19:39:35 freenasSuper systemd[1]: nginx.service: Unit cannot be reloaded because it is inactive.
middlewared is active and enabled.
Restoring the config database didn’t include the cert/key? That’s more than strange. What are the contents of /etc/certificates?
mkdir -p /etc/certificates
openssl req -x509 -nodes -days 365 \
-newkey rsa:2048 \
-keyout /etc/certificates/truenas_default.key \
-out /etc/certificates/truenas_default.crt \
-subj "/CN=truenas"
systemctl restart middlewared
systemctl restart nginx
I stop the NPM docker container and then ran those command and now I’m back into the GUI with http://truenasip. For some reason the cert key was missing after clean install and upload of my config.
Now make sure the cert is present in the GUI, and selected in the system settings, so that the same thing doesn’t happen again next time you reboot.
The GUI SSL Certificate: truenas_default
So I should be ok when I reboot?
The next issue is 2/4 apps are not working npm says stopped and won’t restart or delete. When I try to start I get [Errno 2] No such file or directory: '/mnt/.ix-apps/app_configs/npm/versions/1.2.21/templates/rendered'
Unifi Controller says crashed
[EFAULT] No compose files found for app 'unifi-controller'
My other docker containers are using dockge half are working and 1/2 not.
my arr stack is not for example with the error networks.default: external.name is deprecated. Please set name and external: true
network arr_default declared as external, but could not be found
All my docker data is located at /mnt/v1/docker/npm for npm for example.
I’d think so, but it’s not clear why you weren’t OK to begin with.
On the apps, I really don’t know what to tell you; I don’t do much with them. See if you can edit and save the NPM config; that may help. Might try the same for the Unifi controller.
As to the *arr stuff under Dockge, it looks like you have those apps using a Docker network, and I’ve always created those from the shell: docker network create arr_default.
the docker network command worked. Thanks. Don’t know why it I need to recreate the network.