Started out with UNRAID this morning and began transferring my Plex and Channels DVR server to it, as well as a  bunch of files that I want to archive.   Initially I was accessing it the web GUI via http://tower, and my server had received the IP address of 10.0.0.43 via DHCP,  I switched the IP address to a fixed address of 10.0.0.3.  Afterwards I can now only access the web UI via the IP address, and not by using http://tower address or tower name.  The server also still shows up as "TOWER" when I explore the network using a windows machine, but it will not display any shares.

 

I think I obviously broke something when I switched the IP to a different fixed address.  It's not at all critical, but I'm hoping the fix to get the server accessible by its name again will be pretty easy.   Can anyone point me in the right direction?

 

Thanks!

4 minutes ago, MandolinJeff said:

my server had received the IP address of 10.0.0.43 via DHCP,  I switched the IP address to a fixed address of 10.0.0.3.

The best way to do this is to let the server continue to use DHCP, but in the router, reserve the IP address you want for the server by its MAC address. That way everything on the network is managed at the router, and you won't have things using an IP already in use.

I'm using OPNSense as a router.  So I'm using a small range of IP's that I set aside for use as fixed IP's.  AFAIK it doesn't really do reserved leases.  At least not the way most consumer routers do. 

Edited August 29, 20205 yr by MandolinJeff

44 minutes ago, MandolinJeff said:

AFAIK it doesn't really do reserved leases.

OPNSense calls it a static lease.

57 minutes ago, MandolinJeff said:

Afterwards I can now only access the web UI via the IP address, and not by using http://tower address or tower name.  The server also still shows up as "TOWER" when I explore the network using a windows machine, but it will not display any shares.

And this might just be a matter of the rest of the network needing a little time to see the change before it knows the new IP for that name.

 

Many of us use the Dynamix Local Master plugin to make Unraid the "master" so it is the computer doing name resolution on the local network. Unraid would need to be on 24/7 for this.

17 minutes ago, jonathanm said:

OPNSense calls it a static lease.

And the address range for a static IP has to be reserved for static IP's.  So if I let it assign an address from the DHCP pool and then try to make it static, I'll have to carve that address out from the DHCP pool. So instead I changed it to a range (3) I already had set up for static IPs.  Either way it looks like I may be going back to 43 regardless. 

 

I now suspect it has to do with TLD and DNS Rebinding being blocked by OPNSense.

Edited August 29, 20205 yr by MandolinJeff
Add info

On 8/29/2020 at 7:40 PM, MandolinJeff said:

And the address range for a static IP has to be reserved for static IP's.  So if I let it assign an address from the DHCP pool and then try to make it static, I'll have to carve that address out from the DHCP pool. So instead I changed it to a range (3) I already had set up for static IPs.  Either way it looks like I may be going back to 43 regardless. 

 

I now suspect it has to do with TLD and DNS Rebinding being blocked by OPNSense.

Did you figure this out? Just moved to OPNSense and can ping the Unraid server, but can't access through any webgui path.

Just figured it out.

For future OPNSense users, go to System: Settings: Administration. then, under Alternate Hostnames, enter "myunraid.net"

That allows me to access local web GUI normally.