stream_socket_client(): SSL operation failed with code 1 - apple-push-notifications

stream_socket_client(): SSL operation failed with code 1. OpenSSL Error messages:
error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error
I got error when I try to send a notification using Apple portal. Can you help me with global solutions.?

Related

Laravel websockets throwing curl error when trying to publish an event

Good day everyone, i have setup laravel websockets but when i try to publish a public event i get this curl error
cURL error 77: error setting certificate verify locations:\n CAfile: /etc/ssl/certs/ca-certificates.crt\n CApath: /etc/ssl/certs..
if i change the filename of my certs to ca-certificates.crt.. the websocket wont connect and when i try to publish event, it throws the curl error
Pusher error: cURL error 35: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure..
What do i need to do to solve this...Thanks

: API error (404): network hlfv11_hyperledger not found

✖ Starting business network definition. This may take a minute...
Error: Error trying to start business network. Error: No valid responses from any peers.
Response from attempted peer comms was an error: Error: failed to execute transaction b5c260c02b4792c4ae4b85b3d4ccb4565a495da399d27917dccc1a84244e631f: error starting container: error starting container: API error (404): network hlfv11_hyperledger not found
Response from attempted peer comms was an error: Error: failed to execute transaction b5c260c02b4792c4ae4b85b3d4ccb4565a495da399d27917dccc1a84244e631f: error starting container: error starting container: API error (404): network hlfv11_hyperledger not found
This looks like it is a Docker problem trying to start a new ChainCode container on a Docker Network bridge called "hlfv11_hyperledger" which doesn't exist.
(The word 'network' here is ambiguous in the error message :-( )
This is the same problem and hopefully the same solution as a previous post.

Spillway Transfer failed

I am sending data from Predix Machine through spillway and websocket river, I am getting following error:
Spillway Transfer Failed. Details: "Status for transfer UUID
"87ab8c74-8c34-41cb-b4ba-3666d84ad4c7" in River "WS Sender Service-1".
State: FAILED Status Code: -1100
Status Message: Request 87ab8c74-8c34-41cb-b4ba-3666d84ad4c7 timed out".
What does it mean? what is the error as I am unable to find what this status code is?

NSLogger Viewer

is NSLogger Viewer working for anyone? I'm running Xcode8b6 and can't get any of the sample files to actually log something into the app.
I even rebuild NSLoggerViewer from scratch and when running it in the debug mode, it reports following issue:
2016-08-28 21:13:51.208393 NSLogger[32974:1208999] CFNetwork SSLHandshake failed (-9806)
2016-08-28 21:13:51.208580 NSLogger[32974:1208999] Stream error occurred: stream=<__NSCFInputStream: 0x6180001046e0> self=<LoggerNativeTransport 0x600000083390 listenerPort=63262 publishBonjourService=1 secure=1> error=Error Domain=NSOSStatusErrorDomain Code=-9806 " : t" UserInfo={_kCFStreamErrorCodeKey=4294957490, _kCFStreamErrorDomainKey=3}
2016-08-28 21:14:48.142366 NSLogger[32974:1208999] incoming connection
2016-08-28 21:14:48.143200 NSLogger[32974:1208999] setupSSLForStream, stream=<__NSCFInputStream: 0x610000104ec0> self=<LoggerNativeTransport 0x600000083390 listenerPort=63262 publishBonjourService=1 secure=1> serverCerts=(
"<SecIdentity 0x608000269440 [0x7fffe148cbd0]>",
"<cert(0x1005884d0) s: NSLogger self-signed SSL i: NSLogger self-signed SSL>"
)
Does anyone have any idea what's going on here?

Upgrade to new XCode; can't built in Xamarin

I think that one of the last XCode upgrades that came in last week appears to have broken my Xamarin iOS builds. They fail with:
Failed to locate a valid instance of CoreSimulatorService in the bootstrap. Adding it now.
Or
.../SignInUniversalController_iPhone.storyboard: Error: 2016-07-31 12:11:38.046 ibtoold[23284:2756861] [MT] IBPlatformTool: *** Failed to launch tool with description <IBCocoaTouchPlatformToolDescription: 0x7fce44256b20> System content 1x for IBCocoaTouchFramework-NineOneAndLater w/ default fidelity:
Failed to find or create execution context for description <IBCocoaTouchPlatformToolDescription: 0x7fce44256b20> System content 1x for IBCocoaTouchFramework-NineOneAndLater w/ default fidelity (Failure reason: Software caused connection abort): Failed to find a suitable device for the type SimDeviceType : com.apple.dt.Xcode.IBSimDeviceType.iPad-1x with runtime SimRuntime : 9.3 (13E230) - com.apple.CoreSimulator.SimRuntime.iOS-9-3 (Failure reason: Failed to create SimDeviceSet at path /Users/eric/Library/Developer/Xcode/UserData/IB Support/Simulator Devices. You'll want to check the logs in ~/Library/Logs/CoreSimulator to see why creating the SimDeviceSet failed.): Failed to initialize simulator device set. (Failure reason: Failed to subscribe to notifications from CoreSimulatorService.): Error returned in reply to notification request: Connection invalid (Failure reason: Software caused connection abort)
2016-07-31 12:11:46.096 ibtoold[23284:2756861] [MT] IBPlatformTool: Wrote failed marshalling request diagnostics to path: /var/folders/t9/t9xl93t50ql14mr0lxmmw_2r0000gn/T/IB-agent-diagnostics_2016-07-31_12-11-46_067000
Error: Internal error. Please file a bug at bugreport.apple.com and attach "/var/folders/t9/t9xl93t50ql14mr0lxmmw_2r0000gn/T/IB-agent-diagnostics_2016-07-31_12-11-46_067000".
The logs mentioned in the first error message doesn't appear to be more verbose than the above:
Failed to find or create execution context for description <IBCocoaTouchPlatformToolDescription: 0x7fce44256b20> System content 1x for IBCocoaTouchFramework-NineOneAndLater w/ default fidelity (Failure reason: Software caused connection abort): Failed to find a suitable device for the type SimDeviceType : com.apple.dt.Xcode.IBSimDeviceType.iPad-1x with runtime SimRuntime : 9.3 (13E230) - com.apple.CoreSimulator.SimRuntime.iOS-9-3 (Failure reason: Failed to create SimDeviceSet at path /Users/eric/Library/Developer/Xcode/UserData/IB Support/Simulator Devices. You'll want to check the logs in ~/Library/Logs/CoreSimulator to see why creating the SimDeviceSet failed.): Failed to initialize simulator device set. (Failure reason: Failed to subscribe to notifications from CoreSimulatorService.): Error returned in reply to notification request: Connection invalid (Failure reason: Software caused connection abort)
Error Domain=NSPOSIXErrorDomain Code=53 "Software caused connection abort" UserInfo={NSLocalizedDescription=Failed to find or create execution context for description <IBCocoaTouchPlatformToolDescription: 0x7fce44256b20> System content 1x for IBCocoaTouchFramework-NineOneAndLater w/ default fidelity, NSUnderlyingError=0x7fce44152c40 {Error Domain=NSPOSIXErrorDomain Code=53 "Software caused connection abort" UserInfo={NSUnderlyingError=0x7fce441b8150 {Error Domain=NSPOSIXErrorDomain Code=53 "Software caused connection abort" UserInfo={NSLocalizedFailureReason=Failed to subscribe to notifications from CoreSimulatorService., NSLocalizedDescription=Failed to initialize simulator device set., NSUnderlyingError=0x7fce44155b00 {Error Domain=NSPOSIXErrorDomain Code=53 "Software caused connection abort" UserInfo=0x7fce441c31b0 (not displayed)}}}, NSLocalizedFailureReason=Failed to create SimDeviceSet at path /Users/eric/Library/Developer/Xcode/UserData/IB Support/Simulator Devices. You'll want to check the logs in ~/Library/Logs/CoreSimulator to see why creating the SimDeviceSet failed., NSLocalizedDescription=Failed to find a suitable device for the type SimDeviceType : com.apple.dt.Xcode.IBSimDeviceType.iPad-1x with runtime SimRuntime : 9.3 (13E230) - com.apple.CoreSimulator.SimRuntime.iOS-9-3}}}
This is an iPhone project, but uses a Universal component; I note that since the above says iPad.
When it fails, it opens up the Storyboard editor and it appears to be OK there; there's nothing that seems surprising at first glance.
XCode: Version 7.3.1 (7D1014)
Xamarin: Latest Stable; no updates available
Any insight or thoughts? Thanks!

Resources