Set static IP address -> Web interface unreachable

Quote from dervonnebenaan

Hey guys.

tl;dr: Whenever I set a static IP, I cannot reach the web interface anymore.

Details:
I just installed OMV, connected it to my home LAN and accessed it via the web interface. As advised in the docs, I decided to set a static IP address. Since DHCP had given me 192.168.0.132 and the guide says to pick an address outside of the routers DHCP range, I chose:

IP 10.0.0.2

Subnet 255.255.255.0

Gateway 193.168.0.1

After applying the changes, I was not able to reach the web interface (neither the new nor the old IP). So I plugged in keyboard+monitor and used omv-firstaid to reset the connection. I then tried again with IP 193.168.255.222 , but still no luck.

Any ideas what I'm doing wrong? I never managed to get a grip on this whole ipconfig stuff, so even the most simple and obvious solutions would be appreciated.

[I currently cannot access the routers admin interface because my flatmate has the password and is asleep right now. Hopefully that can be amended tomorrow.]

Display More

Why are you trying to set it outside the range of what the DHCP server likely provides? (ie, 192.168.0.2-255). I guess I see why you'd pick an address outside the DHCP range (I havent in 12yrs).. but with 255 IP's available, seems like an unecessary hassle.

The easier way to do this, would be to only allow the DHCP server to hand out IP's in a certain range (say, 192.168.1.2 - 192.168.1.200) then assign your server 201, which is outside that range.

I've never saw someone try to give an IP address that is completely different than the router IP, but i guess it could be done. Below, my range is obviously set to .100-.249, frankly, this is fine with me. When I clean install OMV, I've used .166 for so many years, setting that IP is like the 2nd thing I do after changing the admin password. It keeps me from having to reconfigure my clients. I guess with the range my router has, I could make it something like 192.168.1.50 and I'd never have a risk of a conflict... Or change my DHCP server to only give out IP's from .2-.165, and then I'd never have a risk

Quote from dervonnebenaan

Details:
I just installed OMV, connected it to my home LAN and accessed it via the web interface. As advised in the docs, I decided to set a static IP address. Since DHCP had given me 192.168.0.132 and the guide says to pick an address outside of the routers DHCP range, I chose:

IP 10.0.0.2

Subnet 255.255.255.0

Gateway 193.168.0.1

You also need to set some value in the DNS field, usually the same as the gateway or add something like 1.0.0.1 separated with a comma, in this case it could be:

193.168.0.1,1.0.0.1

You did it?

Quote from dervonnebenaan

Why does the Setup Guide recommend it? I suspect the reason is to prevent accidential address collisions.

The guide recommends it precisely for this reason, to avoid accidental collisions. But the normal thing is to use a similar network range, change only the last octet and limit that octet in DHCP to a certain possible number of IP addresses. Do not completely change network range.

That configuration seems correct. If it still doesn't work I would use omv-firstaid to reset the network interface to DHCP and then set a static IP.

Quote from dervonnebenaan

But the web interface remains unreachable unless I reset to DHCP.

Ctrl+Shift+R

Quote from chente

Also check this

Thread

[How-To] Fix full OS filesystem - GUI login loop

Symptoms

When you try to login to the GUI of OMV you are not being logged in, but the login page shows up again

Check, if a full root filesystem is the problem
ssh into your server (check the new user guide on how to ssh into your server) and run following command
df df will show you the usage of each filesystem
the output of df will look like this:
(Code, 19 lines)

The filesystem dev/sda1 which is mounted on "/" is the OS filesystem. The use of that filesystem is 100% --> the OS filesystem is full.

…

macom

Jul 23rd 2020

Considering he can apparently log in, I highly doubt that's the issue.

I mostly agree w/ Robroye on this. If he wants to set it outside the DHCP range, he's going to need to log in to his router and set his DHCP range, then put his server outside that range.. I believe routers cannot hand out more than 254 IP's (ie,192.168.1.254) so going over that is pointless.

Only thing we disagree on, is his DNS settings.

I don't think his router's IP will resolve that, as those are set by his service provider in most circumstances. I know he can't log in to the router, but usually you'll find your providers DNS somewhere in the router's web management tool. The simple way to test if your DNS servers are the issue, is just use Google's DNS (8.8.8.8,8.8.4.4) and see if that works correctly. I think most folks use Google's DNS anyway... I have for years.

Quote from KM0201

Considering he can apparently log in, I highly doubt that's the issue.

Wrong thread.

Quote from KM0201

I mostly agree w/ Robroye on this. If he wants to set it outside the DHCP range, he's going to need to log in to his router and set his DHCP range, then put his server outside that range.. I believe routers cannot hand out more than 254 IP's (ie,192.168.1.254) so going over that is pointless.

We are actually all saying the same thing in many different ways.

Quote from KM0201

I don't think his router's IP will resolve that,

Why not? The DNS established on the router should resolve the requests. If it does not resolve them, they are forwarded to the alternate DNS. Not knowing the network settings is the best advice, there could be a DNS server or other settings on the router that would be of no use if you don't set your gateway as DNS.

Quote from chente

Wrong thread.

We are actually all saying the same thing in many different ways.

Why not? The DNS established on the router should resolve the requests. If it does not resolve them, they are forwarded to the alternate DNS. Not knowing the network settings is the best advice, there could be a DNS server or other settings on the router that would be of no use if you don't set your gateway as DNS.

He literally posted a screenshot of him logging in in post #6

I don't know, I've never used my router IP to resolve DNS issues. Not saying it won't work, just never done it.

If he doesn't know his DNS servers, and does not want to use Google's as I suggested... They are easy to get (naturally he would have to be connected to the Internet as I said above).

resolvectl status | grep "DNS Server"

No matter what DNS he's using, that will return the IP's for them and he can just use the IP's (Obviously I'm using Google's DNS).

root@openmediavault:~# resolvectl status | grep "DNS Server"
   DNS Servers: 8.8.8.8 8.8.4.4
root@openmediavault:~# 

Quote from edmais

Unfortunatelly now OMV-firstaid is no longer working - seems file disapeared (Rasbery Pi4) - Any ideas how to fix that? Is it possible to reinstall OMV without loosing all the data and setup?

Pretty sure you could just run the omv-extras install script again, as long as you've not purged the OMV config files