Bug 60079 - Error: SecureChannelFailure (Unknown Secure Transport error `Negotiation'.)
Summary: Error: SecureChannelFailure (Unknown Secure Transport error `Negotiation'.)
Status: RESOLVED NORESPONSE
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: XI 11.2 (d15-4)
Hardware: PC Mac OS
: --- normal
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-10-10 08:35 UTC by Alain
Modified: 2017-12-18 19:37 UTC (History)
5 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description Alain 2017-10-10 08:35:23 UTC
Hi,

I have a problem when I call my webservices. I do not know why, but now I have this message:

Error: SecureChannelFailure (Unknown Secure Transport error `Negotiation '.)

I found this on IOS and on Xamarin.MAC.

I am in the 2 projects in NSURLSession and I have the same problem.

I am sending you the information I use:

=== Visual Studio Community 2017 for Mac (Preview) ===

Version 7.2 Preview (7.2 build 634)
Installation UUID: af98516b-7b3c-413e-ba1b-95a1baeaccc6
Runtime:
	Mono 5.4.0.201 (2017-06/71277e78f6e) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 504000201

=== NuGet ===

Version : 4.3.1.4445

=== .NET Core ===

Runtime : Non installé
SDK : Non installé
SDK MSBuild : /Library/Frameworks/Mono.framework/Versions/5.4.0/lib/mono/msbuild/15.0/bin/Sdks

=== Xamarin.Profiler ===

Version : 1.5.6
Emplacement : /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

=== Apple Developer Tools ===

Xcode 9.0 (13247)
Build 9A235

=== Xamarin.iOS ===

Version: 11.2.0.8 (Visual Studio Community)
Hash: 9a9f0541
Branch: d15-4-xi
Build date: 2017-09-20 14:57:51-0400

=== Xamarin.Android ===

Version : 8.0.0.33 (Visual Studio Community)
Android SDK: /Users/macbookrogister/Library/Developer/Xamarin/android-sdk-macosx
	Versions Android prises en charge :
		6.0(Niveau d’API 23)
		7.1(Niveau d’API 25)

Version des outils du SDK : 25.2.5
Version des outils de plateforme du SDK : 25.0.5
Version des outils de génération du SDK : 25.0.1

Java SDK: /usr
java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)

Code EPL d'Android Designer disponible ici :
https://github.com/xamarin/AndroidDesigner.EPL

=== Xamarin.Mac ===

Version: 3.99.9.11 (Visual Studio Community)

=== Xamarin Inspector ===

Version: 1.3.2
Hash: 461f09a
Branch: 1.3-release
Build date: Tue, 03 Oct 2017 18:26:57 GMT
Client compatibility: 1

=== Build Information ===

Release ID: 702000634
Git revision: cab57de4a7f8c07b8d910d14fff83942cd3f02bf
Build date: 2017-10-02 13:18:41-04
Xamarin addins: a8da992c78f7eb65b3cdb3f951c34a30337cab35
Build lane: monodevelop-lion-d15-4

=== Operating System ===

Mac OS X 10.13.0
Darwin 17.0.0 Darwin Kernel Version 17.0.0
    Thu Aug 24 21:48:19 PDT 2017
    root:xnu-4570.1.46~2/RELEASE_X86_64 x86_64
Comment 1 Alex Soto [MSFT] 2017-10-10 19:49:18 UTC
Please include your full build logs, crash reports (if any), and the most important thing, a test case (to reproduce).
Comment 2 Alain 2017-10-11 09:33:10 UTC
Alex,

I'm outside our offices today and I do the test again and I no longer have the error.

I don't understand what is happening and why I have this message because it does not happen with all the functions of the same WebService that I use. I noticed that yesterday by chance on this function.

Today on this same function, it works but I'm not in-house (maybe it changes something). I will do the test in-house next Monday because I'm not in the office before.

Here the problem happens on Xamarin.MAC, I have not tested on Xamarin.IOS if I had the same problem on the same function.

I have already noticed that some of our customers also have this message from outside but sometimes this seems temporary (or maybe connected in 4G in an area then goes back to WIFI, I do not know.)

Alain
Comment 3 Alain 2017-10-12 09:17:29 UTC
Alex,

I have the log of some of our users and here are the messages they sometimes have but not all the time (fortunately) : 

Error getting response stream (ReadDone2): ReceiveFailure

Error: SecureChannelFailure (Remote prematurely closed connection.)

Why can we have these kinds of errors? Is this due to a configuration of our IIS server ?

Alain
Comment 4 Alain 2017-10-13 14:17:44 UTC
I come back to you because I have done internal testing.

On Xamarin.IOS, no problems.

On Xamarin.Mac, I find that on our development server that has no certificate (but works in https) it works. On our production server where there is a certificate, we have this problem.

Outside, it works.

But as I reported on Xamarin.IOS and Xamarin.MAC, we sometimes have these messages also from outside but not all the time ....

Do you have an explanation ?

Alain
Comment 5 Chris Hamons 2017-10-13 19:19:17 UTC
@Alain - Unfortunately without more to go on than pieces of the error message, there is no way we could give you a reasonable explanation of a problem no one currently understands. 

May I suggest the following:

- If at all possible, create a sample that reproduces the error. Maybe figure out what networking code is erroring and try running it in a tight loop for a hour
- After that, if possible please provide that test code so we can determine if there is a bug on our end, or is a bug in the usage.
- You could also consider bisecting older Xamarin.iOS / Mac versions to see if this problem has always occurred or is a recent change.
Comment 6 Manuel de la Peña [MSFT] 2017-11-16 15:23:29 UTC
@Alain could your please provide the information that @Chris requested?
Comment 7 Timothy Risi 2017-12-18 19:37:36 UTC
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!