Hi all,

 

I have two identical servers but recently having issues with 1 of them. Now i am not sure if this is unraid related or something that happened after upgrading the network card in my opnsense firewall. 

 

Upon rebooting all systems i noticed i did not have access to all of the services hosted on server 2 through HAProxy on opnsense. I can access everything hosted on server 1 just fine. 

 

One thing i noticed is when opening the docker containers webui through unraid it loads the wrong local ip address (192.168.1.105). Normally in Settings > Network Settings > IPv4 address assignment: Static 192.168.1.104. I tried changing this to automatic and opnsense assigned a new lease, I then set the static mapping in opnsense to 192.168.1.104 and surly enough i can access unraid webui but same issue persists when accessing the docker containers.

 

I confirmed the container xml file is set correctly to

WebUI: http://[IP]:[PORT:8096]/ but it still opens at .105 even when unraid is running on .104. I also tried stop/ starting docker and rebooting.

 

Lastly to confirm it is unraid related i manually set the above webui parameter to the actual local ip (.104) and i was able to access the service through the HAProxy as expected.

 

holy-grail-diagnostics-20230731-2136.zip

Edited July 31, 20232 yr by KeyBoardDabbler

No idea if this is anything to go by, but if i look ath the dhcplog.txt i see the server originally wanted the 192.168.1.103 adress, got rejected because of an adress conflict, switched to 1.105 (which you saw) and only after your manual intervention went for the right adress.

 

are you sure, that you don't have any ip assignment on your router for this machine which points to something else then the 1.104 adress?

Jul 24 13:31:32 [1370]: dhcpcd-9.4.1 starting
Jul 24 13:31:32 [1372]: DUID 00:04:03:c0:02:18:04:4d:05:ee:1e:06:da:07:00:08:00:09
Jul 24 13:31:32 [1372]: br0: waiting for carrier
Jul 24 13:31:35 [1372]: br0: carrier acquired
Jul 24 13:31:36 [1372]: br0: soliciting a DHCP lease
Jul 24 13:31:41 [1372]: br0: probing for an IPv4LL address
Jul 24 13:31:42 [1372]: br0: offered 192.168.1.103 from 192.168.1.1
Jul 24 13:31:42 [1372]: br0: probing address 192.168.1.103/24
Jul 24 13:31:46 [1372]: br0: using IPv4LL address 169.254.136.49
Jul 24 13:31:46 [1372]: br0: adding route to 169.254.0.0/16
Jul 24 13:31:46 [1372]: br0: adding default route
Jul 24 13:31:47 [1372]: br0: leased 192.168.1.103 for 7200 seconds
Jul 24 13:31:47 [1372]: br0: adding route to 192.168.1.0/24
Jul 24 13:31:47 [1372]: br0: changing default route via 192.168.1.1
Jul 24 13:31:47 [1372]: br0: deleting route to 169.254.0.0/16
Jul 24 14:47:05 [1372]: br0: 18:c0:4d:88:92:db(18:c0:4d:88:92:db) claims 192.168.1.103
Jul 24 14:54:58 [1372]: br0: 18:c0:4d:88:92:db(18:c0:4d:88:92:db) claims 192.168.1.103
Jul 24 15:02:11 [1372]: br0: 18:c0:4d:88:92:db(18:c0:4d:88:92:db) claims 192.168.1.103
Jul 24 15:56:40 [1372]: br0: 18:c0:4d:88:92:db(18:c0:4d:88:92:db) claims 192.168.1.103
Jul 24 16:21:42 [1372]: br0: 18:c0:4d:88:92:db(18:c0:4d:88:92:db) claims 192.168.1.103
Jul 24 19:18:26 [1372]: br0: 18:c0:4d:88:92:db(18:c0:4d:88:92:db) claims 192.168.1.103
Jul 24 19:19:01 [1372]: br0: 18:c0:4d:88:92:db(18:c0:4d:88:92:db) claims 192.168.1.103
Jul 24 19:19:01 [1372]: br0: 18:c0:4d:88:92:db(18:c0:4d:88:92:db) claims 192.168.1.103
Jul 24 19:19:01 [1372]: br0: 10 second defence failed for 192.168.1.103
Jul 24 19:19:01 [1372]: br0: deleting route to 192.168.1.0/24
Jul 24 19:19:01 [1372]: br0: deleting default route via 192.168.1.1
Jul 24 19:19:01 [1372]: br0: rebinding lease of 192.168.1.103
Jul 24 19:19:01 [1372]: br0: probing address 192.168.1.103/24
Jul 24 19:19:01 [1372]: br0: 18:c0:4d:88:92:db(18:c0:4d:88:92:db) claims 192.168.1.103
Jul 24 19:19:01 [1372]: br0: DAD detected 192.168.1.103
Jul 24 19:19:02 [1372]: br0: soliciting a DHCP lease
Jul 24 19:19:03 [1372]: br0: offered 192.168.1.105 from 192.168.1.1
Jul 24 19:19:03 [1372]: br0: probing address 192.168.1.105/24
Jul 24 19:19:08 [1372]: br0: leased 192.168.1.105 for 7200 seconds
Jul 24 19:19:08 [1372]: br0: adding route to 192.168.1.0/24
Jul 24 19:19:08 [1372]: br0: adding default route via 192.168.1.1