Server.callWithGET broken on Mac compiled plugins

d.healey

Open the projucer file create by HISE, go to file >> save and open in IDE. In xcode select build >> for running. This will create a debug build and once it's finished it should automatically launch the app and the debugger.

LeeC

@d-healey yeah works fine using the debugged build.

So is thinking that this an issue that I should raise as a bug?

I was really hoping that somebody else could check this real quick just incase there's something going on with configuration.

d.healey

@LeeC

yeah works fine using the debugged build.

I wasn't expecting that... try a debug build of the VST and see if that works. If it does then something in the optimisation must be breaking it which seems weird.

LeeC

@LeeC

yeah works fine using the debugged build.

I wasn't expecting that... try a debug build of the VST and see if that works. If it does then something in the optimisation must be breaking it which seems weird.

@d-healey yep same thing with the debug build of the VST/AU on mac. Really appreciate you guiding me through the troubleshooting on this... Not sure what else to try here.

d.healey

In Projucer, try different options in the Debug section, do it one option at a time, until it breaks like the release version. It might take a while, it's a brute force method to try and find the cause.

ulrik

@LeeC I tested in Logic Pro X, works!
Reaper v.5.9, both AUi and VST3 fails, I didn't compile any VST2 version
DSP-Quatro v.5.6, AUi works

I'm on Mac OS 10.14.6

ulrik

@ulrik Ableton Live 10, both AUi & VST3 fails

LeeC

@ulrik thanks for testing on your system.
It looks like we may have a problem and we might need to call Mr Hart!

I know a few people are planning on adding server functionality to their released plugins for
Authentication, upgrades and other things so this seems important I think.

What version of Logic Pro X did you check it on by the way?

Christoph Hart

Before I go into debugging this (which sounds annoying because it only happens in an optimised build if I understand this right), you might try a better test example that logs the response so you see what's happening

function logResponseCallback(status, obj)
{
    obj.StatusCode = status;
    FileSystem.getFolder(FileSystem.Desktop).getChildFile("log.txt").writeObject(obj);
}

LeeC

@Christoph-Hart sure I'll give this a try but from monitoring outbound traffic on my Mac, it appears that no calls are being made from the compiled plugin.
ie. Nothing gets to the server in order to get back obj.StatusCode= status;

I'll try it out and see.

Christoph Hart

In this case you'll get a 404 response after the server timeout (I think it's 20 seconds by default). So just to recap:

only macOS
only compiled plugin - inside HISE it works
only VST / AU plugins in any host
only the release build

Because that's kind of the most annoying debug setup, like take the worst option from all of those and combine in into a debugging hell...

LeeC

@Christoph-Hart yeah you're recap is spot on!

Sorry for adding this to your work load mate, I'll keep trying things my side to see if I can help get to the root cause.

Strange!

ulrik

@LeeC I use Logic Pro X v.10.5.1

Christoph Hart

OK it fails here too, however it's nothing in the HISE code that's wrong - I am passing this through to the system URL calls. No idea why it works in HISE then.

If I look at the macOS system console I can see this output:

standard	10:39:01.700160 +0100	Demo Project	27366555: RECEIVED OUT-OF-SEQUENCE NOTIFICATION: 139 vs 180, 512, <private>
standard	10:39:01.706930 +0100	Demo Project	Task <8E5DEF9F-CA4D-4A51-8321-2C8ECE6A798D>.<0> {strength 1, tls 8, ct 0, sub 0, sig 0, ciphers 1, bundle 0, builtin 0}
standard	10:39:01.707067 +0100	Demo Project	TIC Enabling TLS [3:0x60000072d5c0]
standard	10:39:01.707106 +0100	Demo Project	TIC TCP Conn Start [3:0x60000072d5c0]
standard	10:39:01.707191 +0100	Demo Project	[C3 Hostname#d7b4c9cf:443 tcp, url hash: 1c409223, tls] start
standard	10:39:01.707545 +0100	Demo Project	nw_connection_report_state_with_handler_locked [C3] reporting state preparing
standard	10:39:01.708224 +0100	Demo Project	Task <8E5DEF9F-CA4D-4A51-8321-2C8ECE6A798D>.<0> setting up Connection 3
standard	10:39:01.755940 +0100	Demo Project	nw_socket_handle_socket_event [C3.1:3] Socket received CONNECTED event
standard	10:39:01.756014 +0100	Demo Project	nw_endpoint_flow_protocol_connected [C3.1 IPv4#9956bdef:443 in_progress socket-flow (satisfied)] Transport protocol connected
standard	10:39:01.757153 +0100	Demo Project	TIC TLS Event [3:0x60000072d5c0]: 1, Pending(0)
standard	10:39:01.792222 +0100	Demo Project	TIC TLS Event [3:0x60000072d5c0]: 11, Pending(0)
standard	10:39:01.792276 +0100	Demo Project	TIC TLS Event [3:0x60000072d5c0]: 14, Pending(0)
standard	10:39:01.803606 +0100	Demo Project	System Trust Evaluation yielded status(0)
standard	10:39:01.807335 +0100	Demo Project	TIC TLS Trust Result [3:0x60000072d5c0]: 0
standard	10:39:01.807798 +0100	Demo Project	TIC TLS Event [3:0x60000072d5c0]: 2, Pending(0)
standard	10:39:01.832974 +0100	Demo Project	nw_endpoint_flow_protocol_connected [C3.1 IPv4#9956bdef:443 in_progress socket-flow (satisfied)] Output protocol connected
standard	10:39:01.833040 +0100	Demo Project	nw_connection_report_state_with_handler_locked [C3] reporting state ready
standard	10:39:01.833202 +0100	Demo Project	TIC TLS Event [3:0x60000072d5c0]: 20, Pending(0)
standard	10:39:01.833302 +0100	Demo Project	TIC TCP Conn Connected [3:0x60000072d5c0]: Err(16)
standard	10:39:01.833488 +0100	Demo Project	TIC TCP Conn Event [3:0x60000072d5c0]: 1
standard	10:39:01.833504 +0100	Demo Project	TIC TCP Conn Event [3:0x60000072d5c0]: 8
standard	10:39:01.833577 +0100	Demo Project	TIC TLS Handshake Complete [3:0x60000072d5c0]
standard	10:39:01.833684 +0100	Demo Project	Task <8E5DEF9F-CA4D-4A51-8321-2C8ECE6A798D>.<0> now using Connection 3
standard	10:39:01.833853 +0100	Demo Project	nw_endpoint_flow_protocol_connected [C3.1 IPv4#9956bdef:443 ready socket-flow (satisfied)] Output protocol connected
standard	10:39:01.833940 +0100	Demo Project	Task <8E5DEF9F-CA4D-4A51-8321-2C8ECE6A798D>.<0> sent request, body N
standard	10:39:02.456669 +0100	Demo Project	Task <8E5DEF9F-CA4D-4A51-8321-2C8ECE6A798D>.<0> received response, status 302 content C
standard	10:39:02.457511 +0100	Demo Project	Task <8E5DEF9F-CA4D-4A51-8321-2C8ECE6A798D>.<0> response ended
standard	10:39:02.457551 +0100	Demo Project	Task <8E5DEF9F-CA4D-4A51-8321-2C8ECE6A798D>.<0> done using Connection 3
standard	10:39:02.458344 +0100	Demo Project	Task <8E5DEF9F-CA4D-4A51-8321-2C8ECE6A798D>.<0> {strength 1, tls 8, ct 0, sub 0, sig 0, ciphers 1, bundle 0, builtin 0}
standard	10:39:02.458458 +0100	Demo Project	TIC Enabling TLS [4:0x600000718f00]
standard	10:39:02.458483 +0100	Demo Project	TIC TCP Conn Start [4:0x600000718f00]
standard	10:39:02.458548 +0100	Demo Project	[C4 Hostname#0aed465d:443 tcp, url hash: 1d02324f, tls] start
standard	10:39:02.458844 +0100	Demo Project	nw_connection_report_state_with_handler_locked [C4] reporting state preparing
standard	10:39:02.459336 +0100	Demo Project	Task <8E5DEF9F-CA4D-4A51-8321-2C8ECE6A798D>.<0> setting up Connection 4
standard	10:39:02.605609 +0100	Demo Project	nw_socket_handle_socket_event [C4.1:3] Socket received CONNECTED event
standard	10:39:02.605679 +0100	Demo Project	nw_endpoint_flow_protocol_connected [C4.1 IPv4#0ce3758c:443 in_progress socket-flow (satisfied)] Transport protocol connected
standard	10:39:02.606580 +0100	Demo Project	TIC TLS Event [4:0x600000718f00]: 1, Pending(0)
fehler	10:39:02.785101 +0100	Demo Project	boringssl_context_alert_callback_handler(3817) <private>[0x7fc65c5045d0] Alert level: fatal, description: handshake failure
fehler	10:39:02.785165 +0100	Demo Project	boringssl_session_errorlog(224) <private>[0x7fc65c5045d0] [boringssl_session_handshake_incomplete] SSL_ERROR_SSL(1): operation failed within the library
fehler	10:39:02.785196 +0100	Demo Project	boringssl_session_handshake_error_print(205) <private>[0x7fc65c5045d0] <private>
fehler	10:39:02.785225 +0100	Demo Project	boringssl_session_handshake_error_print(205) <private>[0x7fc65c5045d0] <private>
fehler	10:39:02.785250 +0100	Demo Project	boringssl_context_get_error_code(3638) <private>[0x7fc65c5045d0] SSL_AD_HANDSHAKE_FAILURE
standard	10:39:02.786954 +0100	Demo Project	nw_endpoint_flow_protocol_disconnected [C4.1 IPv4#0ce3758c:443 in_progress socket-flow (satisfied)] Output protocol disconnected
standard	10:39:02.787012 +0100	Demo Project	nw_socket_handle_socket_event [C4.1:3] Socket received READ_CLOSE event
standard	10:39:02.787312 +0100	Demo Project	nw_connection_report_state_with_handler_locked [C4] reporting state failed error handshake failure
standard	10:39:02.787487 +0100	Demo Project	TIC TCP Conn Event [4:0x600000718f00]: 3
fehler	10:39:02.787591 +0100	Demo Project	TIC TCP Conn Failed [4:0x600000718f00]: 3:-9824 Err(-9824)
standard	10:39:02.787669 +0100	Demo Project	TIC TCP Conn Cancel [4:0x600000718f00]
standard	10:39:02.787839 +0100	Demo Project	[C4 Hostname#0aed465d:443 tcp, url hash: 1d02324f, tls] cancel
standard	10:39:02.787977 +0100	Demo Project	[C4 Hostname#0aed465d:443 tcp, url hash: 1d02324f, tls] cancelled
standard	10:39:02.788054 +0100	Demo Project	0.000s [C4 <private> Hostname#0aed465d:443 resolver] path:start
standard	10:39:02.788118 +0100	Demo Project	0.000s [C4 <private> Hostname#0aed465d:443 resolver] path:satisfied
standard	10:39:02.788196 +0100	Demo Project	0.000s [C4 <private> Hostname#0aed465d:443 resolver] resolver:start_dns
standard	10:39:02.788258 +0100	Demo Project	0.007s [C4 <private> Hostname#0aed465d:443 resolver] resolver:receive_dns
standard	10:39:02.788341 +0100	Demo Project	0.007s [C4.1 <private> 192.168.178.16:49477<->IPv4#0ce3758c:443 socket-flow] path:start
standard	10:39:02.788406 +0100	Demo Project	0.007s [C4.1 <private> 192.168.178.16:49477<->IPv4#0ce3758c:443 socket-flow] path:satisfied
standard	10:39:02.788443 +0100	Demo Project	0.009s [C4.1 <private> 192.168.178.16:49477<->IPv4#0ce3758c:443 socket-flow] flow:start_connect
standard	10:39:02.788484 +0100	Demo Project	0.147s [C4.1 <private> 192.168.178.16:49477<->IPv4#0ce3758c:443 socket-flow] flow:finish_transport
standard	10:39:02.788536 +0100	Demo Project	0.147s [C4 <private> Hostname#0aed465d:443 resolver] flow:finish_transport
standard	10:39:02.788646 +0100	Demo Project	0.328s [C4.1 <private> 192.168.178.16:49477<->IPv4#0ce3758c:443 socket-flow] flow:failed_connect handshake failure
standard	10:39:02.788719 +0100	Demo Project	0.328s [C4 <private> Hostname#0aed465d:443 resolver] flow:failed_connect
standard	10:39:02.788761 +0100	Demo Project	0.329s [C4] path:cancel
standard	10:39:02.789105 +0100	Demo Project	nw_connection_report_state_with_handler_locked [C4] reporting state cancelled error handshake failure
standard	10:39:02.789208 +0100	Demo Project	TIC TCP Conn Destroyed [4:0x600000718f00]
standard	10:39:02.789259 +0100	Demo Project	NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9824)
fehler	10:39:02.789287 +0100	Demo Project	Task <8E5DEF9F-CA4D-4A51-8321-2C8ECE6A798D>.<0> HTTP load failed (error code: -1200 [3:-9824])
fehler	10:39:02.789317 +0100	Demo Project	NSURLConnection finished with error - code -1200
standard	10:39:32.823794 +0100	Demo Project	TIC TCP Conn Cancel [3:0x60000072d5c0]
standard	10:39:32.823847 +0100	Demo Project	[C3 Hostname#d7b4c9cf:443 tcp, url hash: 1c409223, tls] cancel
standard	10:39:32.823912 +0100	Demo Project	[C3 Hostname#d7b4c9cf:443 tcp, url hash: 1c409223, tls] cancelled

There's a lot of things to check, but something that catches my eye is the HTTP status 302, and the SSL_HANDSHAKE_FAILED errors at the end. Have you tried another domain? I can imagine that the filehoster does a lot of redirecting and somehow this messes up with the system.

Christoph Hart

Yes, kind of what I was expecting:

Error Domain=NSURLErrorDomain Code=-1200 "An SSL error has occurred and a secure connection to the server cannot be made." UserInfo={_kCFStreamErrorCodeKey=-9824, NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, NSUnderlyingError=0x600000c87ae0 {Error Domain=kCFErrorDomainCFNetwork Code=-1200 "An SSL error has occurred and a secure connection to the server cannot be made." UserInfo={NSErrorFailingURLStringKey=https://download1981.mediafire.com/ufgigkkchdag/brk7qgc382u8j64/HiseServerTest.json, NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, _kCFNetworkCFStreamSSLErrorOriginalValue=-9824, _kCFStreamPropertySSLClientCertificateState=0, NSLocalizedDescription=An SSL error has occurred and a secure connection to the server cannot be made., _kCFStreamErrorDomainKey=3, NSErrorFailingURLKey=https://download1981.mediafire.com/ufgigkkchdag/brk7qgc382u8j64/HiseServerTest.json, _kCFStreamErrorCodeKey=-9824}}, NSLocalizedDescription=An SSL error has occurred and a secure connection to the server cannot be made., NSErrorFailingURLKey=https://download1981.mediafire.com/ufgigkkchdag/brk7qgc382u8j64/HiseServerTest.json, NSErrorFailingURLStringKey=https://download1981.mediafire.com/ufgigkkchdag/brk7qgc382u8j64/HiseServerTest.json, _kCFStreamErrorDomainKey=3}

Please try another server - it looks like this file-hosting site has some issues.

LeeC

@Christoph-Hart thanks for looking into it.
I'll try another file-hosting site and see what we get.

LeeC

@Christoph-Hart I just tried using Dropbox and it fails with this also.
I'm keen to try with a few others hosts. If anybody else has any file hosting recommendations or can test things out at all please chime in

Christoph Hart

There's a tool on macOS that you can run with any URL and it validates everything.

nscurl --ats-diagnostics https://download1981.mediafire.com/ufgigkkchdag/brk7qgc382u8j64/HiseServerTest.json

This spits out a lot of errors. Although

nscurl --ats-diagnostics https://forum.hise.audio/topic/3885/server-callwithget-broken-on-mac-compiled-plugins/33

also produces the error every time that TLSv1.3 is being used (whatever this is lol). The TLS versions below 1.3 run fine though so maybe HISE is using an older version for whatever weird reason...

LeeC

@Christoph-Hart interesting...

I was actually literally in the process of testing using:

Server.setBaseURL("https://forum.hise.audio/");

Server.callWithGET("api/users?section=sort-posts", {}, function(status, response)

as I came across an example that you created in the 'Who is it?' post by @ulrik. Your example pulled back profile images for HISE users.

Compiling as I type and will feedback...

Christoph Hart

Yeah I did that already and it worked here :) So as it seems we don't need to care about the errors in TLS1.2, but the media fire URL threw these errors with all versions down to TLS1.0, so that's your answer.

Server.callWithGET broken on Mac compiled plugins

36

1.9k

10.7k

93.0k