Debian / Kralizec, no web-ui when changing static IP address

So I installed OMV "Kralizec" over Debian 7 "Wheezy".

I needed to create a bridge, but could not do so through the GUI, so I modified /etc/network/interfaces (I followed the guidelines from debian wiki).
At some point I had some issues with this configuration, so I proceeded to drop the bridge and get back to a single static IP address.
I finally tried to change this IP address from GUI, and got some further complication (empty /etc/network/interfaces).

I kind of lost track of all my actions here, but the situation is the following:
If I keep the server on the "old" IP address (192.168.1.9), no problems, everything works.
If I try to modify the IP address of the server through the Web-UI (for instance 192.168.1.8), I can't access the web interface (404 error from nginx), even after rebooting. I can ping the server, access the shares, connect via SSH.
If I revert (manual revert through SSH) to the "old" IP address, everything is back to normal.

I tried to solve the issue with omv-firstaid, same issues.

I don't understand what's going on...

root@NAS:/# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1e:8c:89:8e:7c  
          inet adr:192.168.1.8  Bcast:192.168.1.255  Masque:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2996 errors:0 dropped:96 overruns:0 frame:0
          TX packets:2849 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000 
          RX bytes:286188 (279.4 KiB)  TX bytes:524237 (511.9 KiB)
          Interruption:17 


lo        Link encap:Boucle locale  
          inet adr:127.0.0.1  Masque:255.0.0.0
          adr inet6: ::1/128 Scope:Hôte
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0 
          RX bytes:6127 (5.9 KiB)  TX bytes:6127 (5.9 KiB)

root@NAS:/# cat /etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback
iface lo inet6 loopback


# eth0 network interface
auto eth0
allow-hotplug eth0
iface eth0 inet static
    address 192.168.1.8
    gateway 192.168.1.1
    netmask 255.255.255.0
    dns-nameservers 192.168.1.1
    pre-down ethtool -s $IFACE wol g
iface eth0 inet6 manual
    pre-down ip -6 addr flush dev eth0

root@NAS:/# netstat -tulpen | grep 80
tcp6       0      0 :::80                   :::*                    LISTEN      0          7531        2793/nginx      
udp6       0      0 :::678                  :::*                                0          7180        2220/rpcbind

$ ping 192.168.1.8
PING 192.168.1.8 (192.168.1.8) 56(84) bytes of data.
64 bytes from 192.168.1.8: icmp_req=1 ttl=64 time=0.313 ms
64 bytes from 192.168.1.8: icmp_req=2 ttl=64 time=0.303 ms
64 bytes from 192.168.1.8: icmp_req=3 ttl=64 time=0.294 ms
64 bytes from 192.168.1.8: icmp_req=4 ttl=64 time=0.321 ms
64 bytes from 192.168.1.8: icmp_req=5 ttl=64 time=0.302 ms
^C
--- 192.168.1.8 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3997ms
rtt min/avg/max/mdev = 0.294/0.306/0.321/0.021 ms

Zitat von WastlJ

This reminds me on a thread I read not long ago. He set the IP address to static via CLI but it saved not properly and looked strange in the WebIF (two IP addresses)...

first you can make your WebIF available again via omv-firstaid (run in command line)
Have you tried to first set a static IP via the GUI and try if the WebIF is available, then do the rest via GUI?

Thanks for your answer.

I already tried to fix the WebIF via CLI "omv-firstaid", still get a 404. Note that the 404 is showed by Nginx, which means that the server is up and running on the IP, just not showing anything.

I tried to modify the static IP via the GUI, but then no WebIF available.

The strangest thing is that if I then revert the changes (via CLI, modifying /etc/network/interfaces) to the previous IP address (192.168.1.9), then I have access to the WebIF. It seems that this particular IP address is the only one where I can access the WebIF (all other services working fine).

Could it be a problem with Nginx ? An IP address hardcoded in a conf file somewhere ?

Zitat von tekkb

Is apache running?

service apache2 status

if it is:
service apache2 stop
update-rc.d -f apache2 remove
service nginx restart

No Apache service running (Apache is not even installed).

As a matter of fact I retried to change the IP address through the GUI, but I changed to another address (initial was 192.168.1.9, first try was 192.168.1.8, last try was 192.168.1.7), and now everything is working...

I don't know if the changes were just not taken into account, or if nginx was having troubles.

Anyway now that this is working, another surprising effect arised:
I cannot reach the Web GUI from internet.
I of course put my server IP address on DMZ, I can ping the machine, I can even connect through SSH, but the port 80 of the server seems to be closed, and I cannot connect when I'm not on my LAN network.

I noticed that when changing the port of the Web GUI (to 81), then I could see the port open and connect to the Web GUI.

I have the plugin "extplorer" installed, could it be the cause of this ?

Thank you for your support.

PS: I guess I should create a new thread but it seems that both issues are linked.