Unable to connect to web user interface

[TerryVog]

My FreeNAS server does not show up on the network. It says it should be available at 192.168.0.53 but it isn't. It doesn't even show the web user interface.

I had some trouble using my FreeNAS server after I upgraded to the latest version, so I restarted. And usually it gives the familiar 14 console setup options + the IP address 192.168.0.53. But this time it only showed the 14 options. I configured the IPv4-settings. Now it is showing the IP address as well, but I am still not able to connect.

What could I try to troubleshoot it and get it working again?

 

[j0hnby]

Hi TerryVog

Did you set a specific IP for the web interface to listen on? Try clearing it via the cli and restarting then. I had the same and this sorted it out.

 

[TerryVog]

Did you set a specific IP for the web interface to listen on? Try clearing it via the cli and restarting then.

How can I clear the IP via the command line interface? Resetting to factory defaults didn't help

 

[SweetAndLow]

Reset the networking using the options in the console.

Sent from my Nexus 5X using Tapatalk

 

[j0hnby]

Which version of FreeNAS are you using?

Doesn't sound like Corral as you don't have the horse on the screen so you'll probably be going into the shell. I can't remember directly (more of a Corral user at the moment) - but it's bound to be in the forum as an answer.

Maybe start by checking the web server is running for the GUI - a quick search turned up this, but it's a bit old: https://forums.freenas.org/index.php?threads/web-gui-not-accessible.18937/

Sorry I aren't being more specific

 

[TerryVog]

I think I'm running 9.10.3 with the newest updates, but I usually check my setup using the web user interface, so I can not check.

1) configure network interfaces
2) configure link aggregation
3) configure vlan interfaces
4) configure default route
5) configure static routes
6) configure dns
7) reset root password
8) reset to factory settings
9) shell
10) system update (requires networking)
11) create volume backup
12) restore volume from a backup
13) reboot
14) shutdown

So there is no 'reset the networking'. I would guess option 1 sounds the most likely option. Then it asks me to select an interface (with 1 option to choose from), and then: "Delete interface? (y/n)"

 

[melloa]

Try 1, select your interface, and Y to reset it. After that, reconfigure it.

 

[melloa]

Configuring to DHCP

 

[melloa]

Or manually

 

[TerryVog]

Or manually

Thanks, melloa! These are clear instructions; the kind I need. However, I still have some questions. In the attachment, the address for the default route is different from the address for the web user interface. How do I know what number to use? Would that be 192.168.0.1 in my case? Or should I make sure it is a unique address in my network? If so, how can I figure out which ones are in use?

Likewise, how do I know what addresses to fill in for the DNS configuration. Should I use 8.8.8.8, 8.8.4.4 and the IP address of my router?

 

[SweetAndLow]

Default router should the IP of your router/gateway.

Sent from my Nexus 5X using Tapatalk

 

[melloa]

Would that be 192.168.0.1 in my case?

Let's assume you have a windows PC connected to your router, so to answer your question, open a DOS (now known as command prompt) window and type ipconfig. You will see an output listing your IP address and your default gateway and based on your post above, your router's IP (Default gateway) should be 192.168.0.1.

With that in mind, you can assign an available IP within that subnet (192.168.0) to your server (i.e. 192.168.0.200).

Likewise, how do I know what addresses to fill in for the DNS configuration. Should I use 8.8.8.8, 8.8.4.4 and the IP address of my router?

8.8.8.8 and 8.8.4.4 are public DNS servers from the internet from Google: https://en.wikipedia.org/wiki/Google_Public_DNS. You can use them or any other publicly available ones. If your router (assuming you use one), is running the DNS service, it also can provide such functionality to your computers, so you can add its IP as well.

Usually your router will be provided by your ISP. So when you connect a computer to it, you will receive an IP from its DHCP and will point to the provider's DNS servers. That should surface and, in most cases, be faster as will be closer to your computer - inside the provider network, so you can use only your router IP address as DNS, no problem.

Edit: Usually I setup my router to fix the IP addresses of my servers, so I can let all of them using DHCP and have one central point of configuration, make sure I won't have conflicting IPs, etc. That might be the best second step for you: Learn how to configure your router :)

 

[melloa]

Which version of FreeNAS are you using?

Doesn't sound like Corral

Off topic for this conversation, but, only noticed your signature today (now) ;)

Might add the Yes, I like Corral to mine as well.

 

[TerryVog]

The weird thing is: I followed the instructions and I know what data to use. But I am still unable to connect to my NAS using the web interface. What else could I try?

 

[SweetAndLow]

The weird thing is: I followed the instructions and I know what data to use. But I am still unable to connect to my NAS using the web interface. What else could I try?

From the freenas console go to the shell and try to ping your router or another computer on your network. And what is the output of ifconfig?

Sent from my Nexus 5X using Tapatalk

 

[melloa]

The weird thing is: I followed the instructions and I know what data to use. But I am still unable to connect to my NAS using the web interface. What else could I try?

Now we are getting somewhere :)

From your PC ping the server IP address and provide output.

Assuming it is 10.10.10.200:

Code:

C:\Users\mello>ping 10.10.10.200

Pinging 10.10.10.200 with 32 bytes of data:
Reply from 10.10.10.200: bytes=32 time<1ms TTL=64
Reply from 10.10.10.200: bytes=32 time<1ms TTL=64
Reply from 10.10.10.200: bytes=32 time<1ms TTL=64
Reply from 10.10.10.200: bytes=32 time<1ms TTL=64

Ping statistics for 10.10.10.200:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
	Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\mello>

Go to your server shell and command: ifconfig and provide output. Below mine:

Code:

[root@mellonas] ~# ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
		options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
		ether 00:1b:21:9a:70:6c
		inet 10.10.10.200 netmask 0xffffff00 broadcast 10.10.10.255
		nd6 options=9<PERFORMNUD,IFDISABLED>
		media: Ethernet autoselect (1000baseT <full-duplex>)
		status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
		options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
		inet6 ::1 prefixlen 128
		inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
		inet 127.0.0.1 netmask 0xff000000
		nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
[root@mellonas] ~#

 

[TerryVog]

From the shell on the server I tried "ping -c 3 192.168.0.1" and got:

Code:

PING 192.168.0.1 (192.168.0.1): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host

I also tried from the terminal on my Mac "ping -c 3 192.168.0.53" and got:

Code:

PING 192.168.0.53 (192.168.0.53): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1

--- 192.168.0.53 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss

ifconfig gave me a long output that didn't fit on 1 screen. Am I supposed to type it here? Or what part should I pay attention to?

 

[melloa]

ifconfig gave me a long output that didn't fit on 1 screen. Am I supposed to type it here? Or what part should I pay attention to?

Look at mine. Does yours show an interface other than lo0? What? Mine only has one interface em0 ...

What does it say on that session, in inet, broadcast, status?

 

[SweetAndLow]

Look at mine. Does yours show an interface other than lo0? What? Mine only has one interface em0 ...

What does it say on that session, in inet, broadcast, status?

Have you tried just using DHCP? How are things plugged into your network. Setting up a static IP send to difficult.

The problem you have is your default gateway is not configured correctly. This is the no route to host error you get when trying to ping from the server.

Sent from my Nexus 5X using Tapatalk

 

[TerryVog]

Look at mine. Does yours show an interface other than lo0? What? Mine only has one interface em0 ...

What does it say on that session, in inet, broadcast, status?

I can't see the topmost one, but it is probably re0 because that is what mine says wherever you have em0. The only visible line says: "status: no carrier". Then I can see lo0, bridge0 and epair0a. Is there a parameter I can add to the ifconfig command to show just page 1 of the output?

Have you tried just using DHCP? How are things plugged into your network. Setting up a static IP send to difficult.

How do I do that?