I have a dedicated headless 2012 Mac mini running Sierra, which I’ve been using for Roon from the start. It’s plugged into an Ayre DAC. I recently had the mini down for a month, and since booting it back up I haven’t been able to login to Roon. I get this message:
Network error: Please check your internet connection
The mini otherwise is able to access the internet.
Thanks.
Hi @L_L,
Have you tried rebooting again after getting the error message?
Can you describe your networking setup?
Do you have any firewall or antivirus running on the Core? If you disable them temporarily is there any change?
Thanks for the response,
I have no firewall other than the one included in System Preferences, and I’ve tried to log in with it off, and I’ve also tried rebooting. The network is accessed with WiFi, but Safari works just fine. I haven’t changed anything about the setup, which has worked fine for as long as I’ve had Roon, which is over 3 years.
Hi @L_L,
Did you update to the latest version of Roon? Did this just start happening after the update?
Please use the directions found here and send us over a set of logs using a shared Dropbox link.
Thanks!
I do have the latest version of Roon, and I now tried plugging the mini into a monitor and ethernet, so it has fast, clean internet access, but the problem persists. I don’t use dropbox, so please let me know how else to get you the zipped log files. Thanks.
Hi @L_L,
You can upload the logs here: https://workdrive.zohoexternal.com/external/5dHjIc9agIk-LVTzf
Thanks!
Thanks. Done.
@dylan -
Yep, got the same error today, on a Remote on a NUC and 3 iOS tablets.
My Core just runs Server, so don’t know about that.
Everything worked. There was just this pink error message box when I went to the Overview screen.
Rebooting seemed to solve the problems, but I had to reboot the NUC twice. I also did a hard reset on all my tablets.
I didn’t have a problem after the latest update, but the problem seemed to occur after my first daily restart of my Core machine.
So this is a Roon error message, not a system error message, yes?
Hi @L_L,
We’ve reviewed the logs that you sent over and it looks like there are some networking errors, specifically DNS errors, that are causing this issue to occur:
02/22 00:25:36 Warn: [appupdater] Couldn't connect to update server: System.Net.WebException: Error: NameResolutionFailure
at System.Net.WebConnection.Connect (System.Net.WebOperation operation, System.Threading.CancellationToken cancellationToken) [0x00044] in <bc69ad8632744cfba18f9705e53c6302>:0
at System.Net.WebConnection.InitConnection (System.Net.WebOperation operation, System.Threading.CancellationToken cancellationToken) [0x000cc] in <bc69ad8632744cfba18f9705e53c6302>:0
at System.Net.WebOperation.Run () [0x0009a] in <bc69ad8632744cfba18f9705e53c6302>:0
at System.Net.WebCompletionSource`1[T].WaitForCompletion () [0x00094] in <bc69ad8632744cfba18f9705e53c6302>:0
at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task`1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func`1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000f8] in <bc69ad8632744cfba18f9705e53c6302>:0
at System.Net.HttpWebRequest.GetResponse () [0x00016] in <bc69ad8632744cfba18f9705e53c6302>:0
at Sooloos.Updater+WebUpdate.Load (System.String updateurl) [0x00028] in <4351bba580eb4f198ba49f66f69991bd>:0
at Sooloos.Updater+WebUpdate.CheckForUpdate (System.String serial, System.String userid, System.String product, System.String branding, System.String desired_branch, Sooloos.Version version, Sooloos.Updater+WebUpdate& update) [0x000a7] in <4351bba580eb4f198ba49f66f69991bd>:0
at Sooloos.Updater+<>c__DisplayClass26_0.<ScanOnce>b__0 (System.Object <p0>) [0x0002a] in <4351bba580eb4f198ba49f66f69991bd>:0
02/22 00:25:36 Warn: while posting support data: System.Net.WebException: Error: NameResolutionFailure
at System.Net.WebConnection.Connect (System.Net.WebOperation operation, System.Threading.CancellationToken cancellationToken) [0x00044] in <bc69ad8632744cfba18f9705e53c6302>:0
at System.Net.WebConnection.InitConnection (System.Net.WebOperation operation, System.Threading.CancellationToken cancellationToken) [0x000cc] in <bc69ad8632744cfba18f9705e53c6302>:0
at System.Net.WebOperation.Run () [0x0009a] in <bc69ad8632744cfba18f9705e53c6302>:0
at System.Net.WebCompletionSource`1[T].WaitForCompletion () [0x00094] in <bc69ad8632744cfba18f9705e53c6302>:0
at System.Net.HttpWebRequest.GetRequestStream () [0x00016] in <bc69ad8632744cfba18f9705e53c6302>:0
at Sooloos.Support.LogPoster.Post (System.String url, System.Collections.Generic.IEnumerable`1[T] postables) [0x0017b] in <a3653ba1dae545a79f1d50081573dd5a>:0
What router are you using? Have you tried rebooting it since experiencing this issue? Can you try using Cloudflare or Google DNS and see if there is any change?
I’m using a Comcast business modem with a built in router, so I don’t understand how the DNS could be screwing up. I am going to get a new external router, but can you explain what specifically is wrong with the DNS? Thanks.
Well not really, I think. The “Error: NameResolutionFailure” in the log acts as a pointer to the problem; DNS - there is a problem resolving the IP Address from the name, probably because of a DNS setup error. To work out exactly what the problem is requires looking at your DNS setup; it should be configured in the Router along with the DHCP set-up, but can also be configured on individual devices, which can throw a spanner in the works. So it is not possible for someone remotely to determine exactly what is wrong without access to your network.
For example, I run my own DNS server (PiHole) on my network, but nobody external could know that from the error given above, without looking at the actual DNS setup on my network.
Have a look at the DNS and DHCP setup on your network and jot down the details to start with, that will help diagnosing the possible solution. Good luck, but I hope this helps a little towards getting you sorted.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.