FreeNAS Mini E+ unable to access via web/ip ssh after update from 11.3stable to Core 12

skandy79

Cadet
Joined
Nov 25, 2022
Messages
1
I have a FreeNAS Mini E+ that I largely use for PLEX on my home network but also for things like image storage and documents etc.. I routinely move image/video files via windows shares mapped to my PC.

When I had the FreeNAS 11.3-stable configured I had a static ip. In this case it was 192.168.1.206 and indeed when looking at my network topography I do see the correct device at the indicated IP location:

Prior to upgrade https://freenas.local/ and IP worked for accessing the device and mapping drives for smb/samba.

According to the webGUI output there were no errors during the upgrade process.

I did see a login at: https://192.168.1.206/ui/sessions/signin and tried to signin with the previous root/pw that was set and it spun and asked me to check if the device was online. After that I no longer saw the TrueNAS login prompt. Now I just get:

The connection has timed out
An error occurred during a connection to 192.168.1.206.

I am using FF and yes I've cleared cache and cookies, used incognito, tried other browsers etc. I have also tried to ssh directly into the IP both with a user and without hoping to get a prompt of some kind.

My PLEX Server does appear to be up and running at: http://192.168.1.12:32400/web/index.html#!/ which was the IP assigned to the jail when it was running on 11.3-stable.

1669441224068.png


My PLEX running off the NAS.

Angry IP scanner shows:
IP: 192.168.1.206
Ping: 1899 ms
Hostname: freenas.localdomain
Ports: [n/a]
MAC Address: D0:50:99:D4:CB:10

1669441469274.png


Network sees the device and is not reporting any conflicts.

What am I missing?

This is for a small home office setup/personal use I just wanted to explore new features and see if I could finally update the PLEX jail (its been out of date for a long time).

TIA
Scott
 
Top