Untangle stops working overnight (everynight!)

[fvnet]

Hello dear friends,
I've had my Untangle (with a custom small form Supermicro) for over 4 years or something. I remember reaching some 800 days uptime and everyone in building was happy.
However starting from 3 days ago the device stops doing any traffic at all overnight, interface is showing just fine and a reboot fixes it.
I am attaching a screenshot to view.
I thought it had something to do with automatic upgrades ( I am still at 16.5.2) so I turned that off, but still stuck today.
I used Winscp to find the UVM logs and attaching some part here.

I would appreciate some advice, something is being wrong here

Feb 10 01:24:08 localhost  [ReportsContextImpl] INFO  getTimeZoneOffset calculated value = 7200000
Feb 10 01:24:21 localhost  [ReportsContextImpl] INFO  getTimeZoneOffset calculated value = 7200000
Feb 10 01:24:33 localhost  [ReportsContextImpl] INFO  getTimeZoneOffset calculated value = 7200000
Feb 10 01:26:44 localhost  [MailSenderImpl] INFO  Successfully sent message 'Untangle Daily: Daily (2023-02-09) [untangle.ourhome.local]' to 1 recipients
Feb 10 01:26:54 localhost  [ExecManagerImpl] INFO  ExecManager.exec(pkill -f "Xvfb :1 -screen 5 800x400x8")
Feb 10 01:26:54 localhost  [ExecManagerImpl] INFO  ExecManager.exec(pkill -f "Xvfb :1 -screen 5 800x400x8") = -15 took 6 ms.
Feb 10 01:44:46 localhost  [ExecManagerImpl] INFO  Suspicious command (find /usr/share/untangle/settings -regextype sed -regex '.*/\(network.*\|devices\.js\|hosts\.js\|users\.js\|untangle-certificates/.*\)' -exec echo {} \;) Continuing.
Feb 10 01:44:46 localhost  [ExecManagerImpl] INFO  ExecManager.exec(find /usr/share/untangle/settings -regextype sed -regex '.*/\(network.*\|devices\.js\|hosts\.js\|users\.js\|untangle-certificates/.*\)' -exec echo {} \;)
Feb 10 01:44:46 localhost  [ExecManagerImpl] INFO  ExecManager.exec(find /usr/share/untangle/settings -regextype sed -regex '.*/\(network.*\|devices\.js\|hosts\.js\|users\.js\|untangle-certificates/.*\)' -exec echo {} \;) = 0 took 115 ms.
Feb 10 02:03:12 localhost  [HostTableImpl] INFO  Removing host table entry: 172.16.245.62
Feb 10 02:07:27 localhost  [NetcapHook] WARN  Unknown destination interface: [2]192.168.10.199:53561 -> [0]20.107.81.129:443. Killing session.
Feb 10 02:07:30 localhost  [NetcapHook] WARN  Unknown destination interface: [2]192.168.10.199:53561 -> [0]20.107.81.129:443. Killing session.
Feb 10 02:08:27 localhost  [NetcapHook] WARN  Unknown destination interface: [2]192.168.10.199:53594 -> [0]20.107.81.129:443. Killing session.
Feb 10 02:10:35 localhost  [ExecManagerImpl] INFO  ExecManager.exec(/usr/share/untangle/bin/ut-system-mgr-helpers.sh upgradesAvailable)
Feb 10 02:10:36 localhost  [ExecManagerImpl] INFO  ExecManager.exec(/usr/share/untangle/bin/ut-system-mgr-helpers.sh upgradesAvailable) = 0 took 1003 ms.
Feb 10 02:12:04 localhost  [NetcapHook] WARN  Unknown destination interface: [2]192.168.10.199:55058 -> [0]192.168.10.1:53. Killing session.
Feb 10 02:12:04 localhost  [NetcapHook] WARN  Unknown destination interface: [2]192.168.10.199:55058 -> [0]192.168.10.1:53. Killing session.
Feb 10 02:12:05 localhost  [NetcapHook] WARN  Unknown destination interface: [2]192.168.10.199:55058 -> [0]192.168.10.1:53. Killing session.
Feb 10 02:12:07 localhost  [NetcapHook] WARN  Unknown destination interface: [2]192.168.10.199:55058 -> [0]192.168.10.1:53. Killing session.​

[fvnet]

OK, i might have a possible culprit here.
My brother in law in his apartment has a Synology NAS and everynight he has this cloud syncing on so his photos and videos are uploaded to Dropbox. I had his NAS in bypass rules and did some testing. Once NAS started uploading the whole network became unstable, consuming all upload speed and even untangle was sort of sluggish. I removed the NAS IP from bypass rule and tested again. NAS uploaded normally with full speed but at least whole network was responsive and untangle web interface wasn't sluggish.
Strange things lately with our favorite firewall distro. Come on Untangle!!

[fvnet]

I would like to verify this. Indeed, after extensive testing (used a laptop to upload a 5GB file to cloud with its static IP bypassed) when a device does heavy uploading and its static IP is in bypass rule, the whole network becomes unstable, unresponsive, other devices in network are almost halted.
When I remove the IP from bypass rule everything works fine, the device keeps uploading at high speed.

[gravenscroft]

Check your default priority setting in Config > Network > Advanced > QoS > QoS Rules. It sounds like either your default priority is Very High or that device is somehow falling into a rule that grants it Very High priority. When it's bypassed, it's subject to those rules, so it's probably soaking up your entire network's worth of bandwidth. When it's not bypassed, it's subject to any configuration you have in the Bandwidth Control app.

[fvnet]

Hello, thank you for the reply. I checked again, the Qos is not enabled and the Bandwidth app is not installed.
I have this specific device as mentioned for more than 4 years and this late finding really puzzles me. I am starting to think if something has to do with our provider, we recently switched for VDSL 200/20 to Fiber to the Home 100/100.