TIC TCP Conn Failed [3:0x1c4166180]: 12:8 Err(-65554) - URGENT

Hi all, i need urgent help on some issue that i have never faced before. I´m wonking on an app that is mostly webservice based, and I´m getting this error on the app when deploying the app on my movile phone (iPhone with iOS 11.2.6), and I´m using (Xcode 9.2)

The error is this:

2018-03-05 00:16:30.920248-0300 SADE[4133:1941243] TIC TCP Conn Failed [3:0x1c4166180]: 12:8 Err(-65554)

2018-03-05 00:16:30.923274-0300 SADE[4133:1941243] Task <D9F1C739-E844-456B-A8DA-643F7F6A12E7>.<2> HTTP load failed (error code: -1003 [12:8])

2018-03-05 00:16:30.923766-0300 SADE[4133:1941243] Task <D9F1C739-E844-456B-A8DA-643F7F6A12E7>.<2> finished with error - code: -1003

The app works on the simulator, so seems to be a problem on the device.


I´ve try doing "nscurl --ats-diagnostic [url of service]" and I´m getting some FAIL, but some PASS also, for example:

TLSv1.0 with PFS disabled and insecure HTTP allowed

Result : PASS


Then I set the configurations in my info.plist in the app and nothing, same error.


I´m using request over a VPN (that works) and doing request to a https url

This is the code that I´m executing:

URLSession.shared.dataTask(with: request, completionHandler: { (data, response, error) in


I need help on this PLEASE!!!!

I think you’re having DNS problems. Error -65554 is

kDNSServiceErr_NoSuchRecord
and error -1003 is
NSURLErrorCannotFindHost
.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

I am having a very similar problem. I am facing an issue where my traffic is also running over VPN/LTE on iOS 11.2 / Xcode 9.3.

The issue I am facing is that my traffic is getting kCFStreamErrorDomainSSL, -9802 errors, but it is happening interminitently. Which is confusing to me because usually SSL handshake issues do not happen interminitently if there are problems.


Here is the error that I am seeing.

TIC TCP Conn Failed: 3:-9802 Err(-9802) NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9802)
Task <12096FD3-6E60-4E5A-84AF-BAED4E648F49>.<1> HTTP load failed (error code: -1200 [3:-9802])
CFNetwork Diagnostics [1:1671] 09:31:24.078 {
Response Error: (null) Request: <CFURLRequest 0x1c81aad40 [0x1b4c082b0]> {url = urlHere, cs = 0x0} Error:
Error Domain=kCFErrorDomainCFNetwork Code=-1200 "(null)"
UserInfo={_kCFStreamPropertySSLClientCertificateState=0, _kCFNetworkCFStreamSSLErrorOriginalValue=-9802, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9802}}


I used the nscurl tool and have confirmed with the server engineers that the correct TLS version is being used. What I am confused about is why this issue is happening interminitently.


Any thoughts on this issue and what could be happening here?

Error -9802 is

errSSLFatalAlert
, which typically means that the TLS client has received a fatal alert message from the server. You can learn more about this in Section 7.2 Alert Protocol of RFC 5246.

This error can be generated internally by the TLS client but I wouldn’t expect that to happen intermittently. In my experience most intermittent errors are actually the result of problems on the server side. For example, I often see symptoms like this when the server is actually a load balancer and that load balancer has got confused.

There are two ways you can investigate this:

  • Using an RVI packet trace (per QA1176 Getting a Packet Trace), which allows you to see whether things went wrong on one specific connection.

  • Via detailed BoringSSL logging [1].

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

[1] I recently tested this and here’s a description of what I did:

  1. I started with macOS 10.13.4 running Xcode 9.3 with an iPhone 6s running 11.2.6 connected via USB.

  2. I launched the Console app.

  3. I selected the iPhone from the list on the left.

  4. I made sure that both Action > Include Info Messages and Action > Include Debug Messages were enabled.

  5. I entered “com.apple.network.boringssl” into the search box and press Return.

  6. I used the menu attached to the resulting search token to change the search key from Any to Subsystem.

  7. I also used that menu to change the type from Contains to Equals.

  8. I ran my test app from Xcode.

  9. In that app I tapped the Test button to start a test; this loads the

    <https://example.com>
    URL.
  10. In Console I saw very detailed logging output from BoringSSL.

I'm also facing the same issue when the deployed app using Xcode 9.4 on iPhone with iOS 11.3 and 11.4

I´m using request over a VPN and doing request to an https URL using dataTask(with: newRequest, completionHandler:) of URLSession


Here is part of the log:


2018-06-11 11:07:29.199709+0800 MYAPP[909:673049] [] nw_path_evaluator_request_nexus_and_stats NECP_CLIENT_ACTION_REQUEST_NEXUS_INSTANCE [65: No route to host]

2018-06-11 11:07:29.199781+0800 MYAPP[909:673049] [] nw_endpoint_flow_setup_channel [29 [Server IP address], in_progress channel-flow (satisfied)] failed to request nexus instance: Error Domain=kNWErrorDomainPOSIX Code=65 "No route to host" UserInfo={NSDescription=No route to host}

2018-06-11 11:07:29.199864+0800 MYAPP[909:673049] TIC TCP Conn Failed [21:0x1d417fb00]: 1:65 Err(65)

2018-06-11 11:07:29.199942+0800 MYAPP[909:673049] Task <4672A997-DDC1-4C72-B104-B1C8847FB07E>.<1> HTTP load failed (error code: -1004 [1:65])

2018-06-11 11:07:29.200022+0800 MYAPP[909:673092] Task <4672A997-DDC1-4C72-B104-B1C8847FB07E>.<1> finished with error - code: -1004

Error-Optional(Error Domain=NSURLErrorDomain Code=-1004 "Could not connect to the server." UserInfo={NSUnderlyingError=0x1c8453aa0 {Error Domain=kCFErrorDomainCFNetwork Code=-1004 "(null)" UserInfo={_kCFStreamErrorCodeKey=65, _kCFStreamErrorDomainKey=1}}, NSErrorFailingURLStringKey=https://[Server IP address], NSErrorFailingURLKey=https://[Server IP address] _kCFStreamErrorDomainKey=1, _kCFStreamErrorCodeKey=65, NSLocalizedDescription=Could not connect to the server.})


Please help to check, thanks!!

I’m not sure why you think your problem is related to the previous problems. The low-level error number here is 65, that is,

EHOSTUNREACH
, which typically means that the address you’re trying to communicate with is not reachable for some reason. Given that you seems to be connecting via IP address, rather than DNS name, it’s likely that there’s no route to that IP address.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Thank you very much for your help in this matter, Quinn. The problem ended upon being the VPN server closing the connections that tooks a very long time to setup. This was the random part that was strange to us. In short the VPN server waited for 10 seconds and if the connection was not properly setup in 10 seconds it closed the connection with a reset and it manifest as a 9802 in the error logs. I did end up diagnosing this issue using Wireshark and the remote virtual interface, so thank you for that tip. It was much appreciated.

TIC TCP Conn Failed [3:0x1c4166180]: 12:8 Err(-65554) - URGENT
 
 
Q