Hi @Brandon ,
Thanks for your patience here. I activated diagnostics mode and I noticed that you are getting quite a lot of network reachability errors in your logs.
This error can happen if you have a faulty cable/driver/switch and the connection keeps being re-negotiated over and over again or if your switch has some kind of Energy Efficiency setting where it turns the connection on/off.
Do you only have one networking interface active at this time? These network reachability messages come from the Operating System itself:
Line 4907: 06/05 22:55:15 Trace: [broker/accounts] network reachability changed. refreshing
Line 4927: 06/05 22:55:15 Trace: [client/roonbridges] network reachability changed, sending discovery query
Line 4935: 06/05 22:55:15 Debug: [tidal] network reachability changed. refreshing token
Line 4950: 06/05 22:55:16 Trace: [roonapi] network reachability changed. Kicking off discovery cycle
Line 4954: 06/05 22:55:16 Trace: [mobile] [remoteconnectivity] Port Verification started due to: network reachability changed, port verification not in progress, starting a new attempt
Line 4979: 06/05 22:55:17 Trace: [remoting/brokerserver] network reachability changed. Kicking off discovery cycle
Line 5007: 06/05 22:56:20 Trace: [broker/accounts] network reachability changed. refreshing
Line 5032: 06/05 22:56:20 Trace: [client/roonbridges] network reachability changed, sending discovery query
Line 5040: 06/05 22:56:20 Debug: [tidal] network reachability changed. refreshing token
Line 5056: 06/05 22:56:21 Trace: [roonapi] network reachability changed. Kicking off discovery cycle
Line 5057: 06/05 22:56:21 Trace: [mobile] [remoteconnectivity] Port Verification started due to: network reachability changed, port verification not in progress, starting a new attempt
Line 5071: 06/05 22:56:22 Trace: [remoting/brokerserver] network reachability changed. Kicking off discovery cycle
This is a known-issue, being investigated here: