An unexpected error has occurred:; nested exception is: java.net.SocketException: Software caused connection abort: recv failed. FaultCode: {http. After a couple of minutes of inactivity an OpenEdge Web Service can no longer be accessed errors (10893), (11506) and (10899).
I’m having problem launching the euler’s app on ShinyProxy. I can build the docker image without problem, and if I run it directly on Docker using the command: docker run -it -p 3838:3838 openanalytics/shinyproxy-template the app works as expected. However, when I try to run it on shinyproxy I get the following error: Status code: 500 Message: Failed to start container: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: org.apache.http.conn.HttpHostConnectException: Connect to localhost:2375 localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1 failed: Connection refused: connect I’m using Docker Toolbox on Windows 10. The docker’s daemon runs at IP 192.168.99.100. The docker setup options are just for various types of Linux systems. They're of no use if you're on windows. Hi, Since you use port 2376 I assume you have TLS enabled.
In that case, can you try this docker url? Docker: url: You may also have to have to set cert-path to avoid certificate resolution errors. Alternatively, you can use plain http via port 2375, but you have to enable this explicitly in docker-for-windows: The second error (waiting for proxy to launch) actually looks like a bug, where shinyproxy does not properly recover from a previous failed container launch.
We'll investigate this further. Regards, Frederick.
Hi, thank you for the response. Using the url you gave me above, I get the following error: Status code: 500 Message: Failed to start container: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target So the problem seems to be in the cert-path, am I right? How do I need to set it? Alternatively, how can I disable TLS in Docker Toolbox?
SOLVED RDP through VPN SSL doesn't work anymore We have a Fortigate 110C configured for Remote Access. We have configured Web Access Portal and published a bookmark to access a Windows 2008 R2 virtual Machine with RDP Native protocol. All was working fine when the Fortigate was under FortiOS 4.0 MR3 Patch 10. Since we upgraded our firewall to FortiOS 5.2.2, we are now unable to connect through RDP. When we use RDP Native, after having clicked on the bookmark, we are prompted to enter the Windows 2008 user and password.
Then, the dialog box displays 'Securing remote connection' indefinitely and never displays the Remote Desktop. When we use RDP, after having provided the required information, a Java applet is started, we can see the Remote Desktop for 1 or 2 seconds and the Java applet crashes with the following error messages: - javax.net.ssl.SSLException Connection has been shutdown: javax.net.ssl.SSLException:javax.net.ssl.SSLException: Software caused connection abort: recv failed (see attached screen capture) - javax.net.SocketException Software caused connection abort: recv failed The Remote Desktop to the Windows 2008 R2 works fine from a computer located in the same LAN than the virtual machine. Does anyone have the same issue? Thanks in advance for your help.
Hello, RDP through VPN SSL is now working fine on my Fortigate 110C Cluster with FortiOS 5.2.2. Here's the solution I've applied (thanks to Dave for the idea.):. Reverted back my FG110C cluster to FortiOS 5.0.6 (this is the older backup file I have for this cluster) = RDP VPN SSL is working fine. Upgraded my cluster to 5.2.2, applying ALL the patches between 5.0.6 and 5.2.2 (i.e.: 5.0.6 = 5.0.7 = 5.0.8 = 5.0.9 = 5.0.10 = 5.2.0 = 5.2.1 = 5.2.2) and RDP VPN SSL is working fine at each step of the upgrade path.Hope this can help someone else.