macOS 10.13.1 - Unable to connect

I'm posted to here after working with tech support on this issue.

I did a full uninstall of Logos on my Mac to try and address an issue I was having with the media tab. After downloading the DMG again and trying to launch it I get an "Unable to connect". I tried on several other wifi networks to no avail. Another mac running the same OS and logos version (7) on my home networking is running fine. There are no configuration differences between them of note and neither are running extra security software.

Here is what my Logos.log looks like:

I ran tcpdump -k NP and piped it to a text file, then grepped out the logos stuff. This is what I get:

08:17:38.103303 (proc Logos:12152) IP 192.58.0.23.https > 172.17.2.105.59057: Flags [.], ack 175, win 32779, options [nop,nop,TS val 1195680295 ecr 887929733], length 0

08:17:38.103595 (proc Logos:12152) IP 192.58.0.23.https > 172.17.2.105.59057: Flags [.], seq 1:1383, ack 175, win 32779, options [nop,nop,TS val 1195680303 ecr 887929733], length 1382

08:17:38.103606 (proc Logos:12152) IP 192.58.0.23.https > 172.17.2.105.59057: Flags [.], seq 1383:2765, ack 175, win 32779, options [nop,nop,TS val 1195680303 ecr 887929733], length 1382

08:17:38.104064 (proc Logos:12152) IP 192.58.0.23.https > 172.17.2.105.59057: Flags [P.], seq 2765:4147, ack 175, win 32779, options [nop,nop,TS val 1195680303 ecr 887929733], length 1382

08:17:38.148889 (proc Logos:12152) IP 192.58.0.23.https > 172.17.2.105.59057: Flags [P.], seq 4147:4167, ack 175, win 32779, options [nop,nop,TS val 1195680338 ecr 887929778], length 20

08:17:38.352760 (proc Logos:12152) IP 192.58.0.23.https > 172.17.2.105.59057: Flags [.], ack 176, win 32779, options [nop,nop,TS val 1195680466 ecr 887929903], length 0

08:17:38.352780 (proc Logos:12152) IP 192.58.0.23.https > 172.17.2.105.59057: Flags [F.], seq 4167, ack 176, win 32779, options [nop,nop,TS val 1195680472 ecr 887929903], length 0

This is the LogosError.log brick that keeps repeating:

Program Version: 7.10 (7.10.0.0019)
Time: 2017-11-11 08:30:11 -07:00 (2017-11-11T15:30:11Z)
Error building request (POST https://auth.logos.com/oauth/v1/users/signin?allowSession=False).
System.Net.WebException: Error: TrustFailure (CertificateUnknown) ---> Mono.Security.Interface.TlsException: CertificateUnknown
at Mono.AppleTls.AppleTlsContext.EvaluateTrust () [0x000a4] in <3f171a10af8741af8366aeeac9dda8dd>:0
at Mono.AppleTls.AppleTlsContext.RequirePeerTrust () [0x00008] in <3f171a10af8741af8366aeeac9dda8dd>:0
at Mono.AppleTls.AppleTlsContext.ProcessHandshake () [0x00046] in <3f171a10af8741af8366aeeac9dda8dd>:0
at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncProtocolRequest asyncRequest, Mono.Net.Security.AsyncOperationStatus status) [0x0002a] in <3f171a10af8741af8366aeeac9dda8dd>:0
at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (Mono.Net.Security.AsyncOperationStatus status) [0x0006b] in <3f171a10af8741af8366aeeac9dda8dd>:0
at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation () [0x0000d] in <3f171a10af8741af8366aeeac9dda8dd>:0
at Mono.Net.Security.AsyncProtocolRequest.StartOperation () [0x0003c] in <3f171a10af8741af8366aeeac9dda8dd>:0
at Mono.Net.Security.AsyncProtocolRequest.StartOperation (Mono.Net.Security.AsyncOperation operation) [0x00024] in <3f171a10af8741af8366aeeac9dda8dd>:0
at Mono.Net.Security.MobileAuthenticatedStream.ProcessAuthentication (System.Net.LazyAsyncResult lazyResult) [0x00057] in <3f171a10af8741af8366aeeac9dda8dd>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <29cdfba67fa048509041e9d40014a204>:0
at Mono.Net.Security.MobileAuthenticatedStream.ProcessAuthentication (System.Net.LazyAsyncResult lazyResult) [0x00078] in <3f171a10af8741af8366aeeac9dda8dd>:0
at Mono.Net.Security.MobileAuthenticatedStream.AuthenticateAsClient (System.String targetHost, System.Security.Cryptography.X509Certificates.X509CertificateCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x0000c] in <3f171a10af8741af8366aeeac9dda8dd>:0
at Mono.Net.Security.Private.MonoSslStreamWrapper.AuthenticateAsClient (System.String targetHost, System.Security.Cryptography.X509Certificates.X509CertificateCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x00006] in <3f171a10af8741af8366aeeac9dda8dd>:0
at Mono.Net.Security.MonoTlsStream.CreateStream (System.Byte[] buffer) [0x0007b] in <3f171a10af8741af8366aeeac9dda8dd>:0
at System.Net.WebConnection.CreateStream (System.Net.HttpWebRequest request) [0x00073] in <3f171a10af8741af8366aeeac9dda8dd>:0
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.EndGetRequestStream (System.IAsyncResult asyncResult) [0x0003a] in <3f171a10af8741af8366aeeac9dda8dd>:0
at Libronix.Utility.Net.WebServiceRequestBase`1+<>c__DisplayClass7_3[TResponse].<BeginGetResponse>b__4 (System.IAsyncResult ar) [0x00000] in /Volumes/Code/Jenkins/workspace/Logos-Desktop-Mac-Beta-Ship/Utility/src/Libronix.Utility/Net/WebServiceRequestBase.cs:357

Techsupport took me to this page and said all is well in terms of the cert: https://downloads.logoscdn.com

I'm at a loss - any thoughts?

Find more posts tagged with

Comments

Tim

Apologies, I replied without having scoured your logs in detail first. Um, can you check the versions of mono between your machines? they ought to be the same, but since this seems to be related to mono it is worth confirming.

Have you by any chance installed/uninstalled X11 on one of the machines but not the other?

I see you aren't running extra security, but have you tried going into the Apple firewall options and explicitly giving logos permission to connect?

Josh Czinger

https://community.logos.com/discussion/comment/934229#Comment_934229

Hi Tim,

Thanks for the replies.

I have never explicitly installed mono on either machine. My assumption is that the logos app adds what it needs at runtime. To test this I uninstalled mono completely as per the mono uninstall instructions (http://www.mono-project.com/docs/about-mono/supported-platforms/osx/) :

sudo rm -rf /Library/Frameworks/Mono.framework

sudo pkgutil --forget com.xamarin.mono-MDK.pkg

sudo rm -rf /etc/paths.d/mono-commands

I also removed the .mono directly from my user for good measure

After restarting the Logos app these folders were recreated.

I've explicitly installed X11 on this machine in the past, but that was a long time ago and Logos 7 has been running many times since then. I uninstalled it anyway for good measure to no avail.

The apple firewall has been turned off and it has not helped either.

Josh Czinger

https://community.logos.com/discussion/comment/934241#Comment_934241

I thought I'd try Logos 6 to see if it worked and it does. I simply deleted Logos 7 from applications and copied over Logos 6 from the DMG and its working fine.

After I got it open and the resources downloaded I tried to install logos 7 again, but it didn't work. It still gets stuck at "Unable to Connect" after entering in my credentials.

Tim

https://community.logos.com/discussion/comment/934245#Comment_934245

Interesting that it is something explicitly related to 7 and not 6. Yes mono does come with Logos, it is one of the open software licenses they use. I asked about X.11 because if you look at the Mono documentation under about --> logos, roughly 2/3 the way down the scrolling page, it looks like it is related to X.11. It is possible that X.11 made a change to your machine in the past that did not bite you until this latest update when Logos did something that conflicted. I just upgraded to 10.13.1 last night on my MBP but don't have X.11 installed on it, and am not sure I want to try just for testing purposes since it is a work necessary machine for me. Sorry!

Is X.11 installed on your other machine that has Logos 7 working?

Josh Czinger

https://community.logos.com/discussion/comment/934323#Comment_934323

X.11 is not explicitly installed on the other system. If it has anything it is just what came along from Logos.

The broken system had X.11 and Logos 7 working on it for some time before this error. I had the latest version of Logos 7 running and uninstalled it to try to fix the broken Media pane.

I suspect that some item was removed when I did the uninstall that is not getting recreated now.

Reading more about this certificate error in mono it appears that there is a certificate store kept inside of mono that the application needs to be able to read/write to. Several of these errors were addressed by developers by adding a line above the certificate usage code. I'm not sure if that's the same thing that's going on here, but it might be.

Martin Potter

https://community.logos.com/discussion/comment/934325#Comment_934325

Josh,

I'm sorry you are having issue with the application. Recent versions of Mono use the system provide SSL implementation which removes the necessity for the old copy of the certificate store along with support for more up-to-date SSL implementation. The error you are getting seems to indicate that there is an issue validating the certificate for the site https://auth.logos.com. Can you please visit https://auth.logos.com in Safari, click on the padlock that appears in the address bar and take a screenshot of the trust details for the site certificate and the root certificate?

It should look like the following for the site certificate:

and this for the root certificate:

Thank you,
Martin

Josh Czinger

https://community.logos.com/discussion/comment/934417#Comment_934417

here they are:

Tim

https://community.logos.com/discussion/comment/934419#Comment_934419

certificates fall well outside the realm of my IT experience, but I find it interesting that there is a disparity of ending dates on the root certificates, although I cannot think of a reason that would cause problems, unless it is an indication that the certificate on Josh's computer is corrupt.

Martin Potter

https://community.logos.com/discussion/comment/934419#Comment_934419

Josh,

Thank you. It looks like you have explicitly trusted the "Go Daddy Secure Certificate Authority - G2" on that machine, which is why you do not have the "Go Daddy Root Certificate Authority - G2" certificate in your chain. If you open Keychain Access and change the "Go Daddy Secure Certificate Authority - G2" to "Use System Defaults" and change the other values under trust for that certificate to their default of "no value specified", it should allow you to connect again.

Josh Czinger

https://community.logos.com/discussion/comment/934430#Comment_934430

Martin,

Nice work. I found the two go daddy certs that I had trusted and deleted them as they were older than what was currently available. After that I went back to auth.logos.com and found that I got the intermediate cert as well.

Logging into Logos 7 works like a charm now. On top of that, my Media pane is working as well.

Thanks very much!

Josh