17 minutes ago, Squid said:

• On the router, disable any DMZ
• On the router, remove any port forwarding thats not required for applications (ie: Port Forwarding 1194 for OpenVPN or 32400 for Plex is OK, but forwarding 443 or 22 or 80 is never OK)
• Make damn well sure that the router has a hard password for its administration (and disable any remote administration options in it).  Never, never, never use the default login and password for any router on the earth.  (Using default login and password is OK however if you're located on the moon)

Okie man. Definitely ll check those.

Facing this issue from noon. WebUI is available but not anywhere in the windows explorer.

tower-diagnostics-20181126-0118.zip

tower-diagnostics-20181126-0118.zip

Something wrong with your network connection. This is repeated over and over in your syslog:

Nov 25 23:31:29 Tower emhttpd: error: get_limetech_time, 240: Connection timed out (110): -2 (7)
### [PREVIOUS LINE REPEATED 5627 TIMES] ###
Nov 26 01:06:44 Tower kernel: e1000e: eth0 NIC Link is Down
Nov 26 01:06:44 Tower kernel: bond0: link status definitely down for interface eth0, disabling it
Nov 26 01:06:44 Tower kernel: device eth0 left promiscuous mode
Nov 26 01:06:44 Tower kernel: bond0: now running without any active interface!
Nov 26 01:06:44 Tower kernel: br0: port 1(bond0) entered disabled state
Nov 26 01:06:54 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Nov 26 01:06:54 Tower kernel: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex
Nov 26 01:06:54 Tower kernel: bond0: making interface eth0 the new active one
Nov 26 01:06:54 Tower kernel: device eth0 entered promiscuous mode
Nov 26 01:06:54 Tower kernel: bond0: first active interface up!
Nov 26 01:06:54 Tower kernel: br0: port 1(bond0) entered blocking state
Nov 26 01:06:54 Tower kernel: br0: port 1(bond0) entered forwarding state

 

3 hours ago, trurl said:

Something wrong with your network connection. This is repeated over and over in your syslog:

Nov 25 23:31:29 Tower emhttpd: error: get_limetech_time, 240: Connection timed out (110): -2 (7)
### [PREVIOUS LINE REPEATED 5627 TIMES] ###
Nov 26 01:06:44 Tower kernel: e1000e: eth0 NIC Link is Down
Nov 26 01:06:44 Tower kernel: bond0: link status definitely down for interface eth0, disabling it
Nov 26 01:06:44 Tower kernel: device eth0 left promiscuous mode
Nov 26 01:06:44 Tower kernel: bond0: now running without any active interface!
Nov 26 01:06:44 Tower kernel: br0: port 1(bond0) entered disabled state
Nov 26 01:06:54 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Nov 26 01:06:54 Tower kernel: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex
Nov 26 01:06:54 Tower kernel: bond0: making interface eth0 the new active one
Nov 26 01:06:54 Tower kernel: device eth0 entered promiscuous mode
Nov 26 01:06:54 Tower kernel: bond0: first active interface up!
Nov 26 01:06:54 Tower kernel: br0: port 1(bond0) entered blocking state
Nov 26 01:06:54 Tower kernel: br0: port 1(bond0) entered forwarding state

 

Could it be the network switch? I suspect the second switch being the culprit.

8 hours ago, ThePhotraveller said:

Could it be the network switch?

Yes, or the cable.

I still think it is a hardware issue. Something is faulty somewhere. Check everything and yes don't ever expose your server to the net without proper security. This forum is full of recent threads of people getting hacked.