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

    • OMV 1.0

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • 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...

      Source Code

      1. root@NAS:/# ifconfig
      2. eth0 Link encap:Ethernet HWaddr 00:1e:8c:89:8e:7c
      3. inet adr:192.168.1.8 Bcast:192.168.1.255 Masque:255.255.255.0
      4. UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      5. RX packets:2996 errors:0 dropped:96 overruns:0 frame:0
      6. TX packets:2849 errors:0 dropped:0 overruns:0 carrier:0
      7. collisions:0 lg file transmission:1000
      8. RX bytes:286188 (279.4 KiB) TX bytes:524237 (511.9 KiB)
      9. Interruption:17
      10. lo Link encap:Boucle locale
      11. inet adr:127.0.0.1 Masque:255.0.0.0
      12. adr inet6: ::1/128 Scope:Hôte
      13. UP LOOPBACK RUNNING MTU:16436 Metric:1
      14. RX packets:24 errors:0 dropped:0 overruns:0 frame:0
      15. TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
      16. collisions:0 lg file transmission:0
      17. RX bytes:6127 (5.9 KiB) TX bytes:6127 (5.9 KiB)
      Display All


      Source Code

      1. root@NAS:/# cat /etc/network/interfaces
      2. # The loopback network interface
      3. auto lo
      4. iface lo inet loopback
      5. iface lo inet6 loopback
      6. # eth0 network interface
      7. auto eth0
      8. allow-hotplug eth0
      9. iface eth0 inet static
      10. address 192.168.1.8
      11. gateway 192.168.1.1
      12. netmask 255.255.255.0
      13. dns-nameservers 192.168.1.1
      14. pre-down ethtool -s $IFACE wol g
      15. iface eth0 inet6 manual
      16. pre-down ip -6 addr flush dev eth0
      Display All


      Source Code

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


      Source Code

      1. $ ping 192.168.1.8
      2. PING 192.168.1.8 (192.168.1.8) 56(84) bytes of data.
      3. 64 bytes from 192.168.1.8: icmp_req=1 ttl=64 time=0.313 ms
      4. 64 bytes from 192.168.1.8: icmp_req=2 ttl=64 time=0.303 ms
      5. 64 bytes from 192.168.1.8: icmp_req=3 ttl=64 time=0.294 ms
      6. 64 bytes from 192.168.1.8: icmp_req=4 ttl=64 time=0.321 ms
      7. 64 bytes from 192.168.1.8: icmp_req=5 ttl=64 time=0.302 ms
      8. ^C
      9. --- 192.168.1.8 ping statistics ---
      10. 5 packets transmitted, 5 received, 0% packet loss, time 3997ms
      11. rtt min/avg/max/mdev = 0.294/0.306/0.321/0.021 ms
      Display All
    • 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?
      OMV stoneburner | HP Microserver | 256GB Samsung 830 SSD for system | 4x 2TB in a RAID5
      OMV erasmus| Odroid XU4 | 5TB Data drive | 500GB Backup drive
    • WastlJ wrote:

      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 ?
    • tekkb wrote:

      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.
    • Sorry to bump an old topic but for prod. we still use (a still good!) OMV 1.9 Kralizec.

      This morning, after an (big) update and restart the GUI do not appear, instead I got message from Nginx :



      ( Big sweat!!!??? ...).... :S :S :S Oh la la...


      I try :

      service apache2 stop

      Then...

      service nginx restart


      And the GUI is back again. OUF ! .....
      Omv 3.x
      i5 16Gb 11To (Boot SSD16Gb)

      The post was edited 1 time, last by caseyj ().