java.net.SocketException: Reply from SOCKS server has bad version 60

Oracle Community | 843798 | 1 decade ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    Firewall HTTP connection Error

    Oracle Community | 1 decade ago | 843798
    java.net.SocketException: Reply from SOCKS server has bad version 60
  2. 0

    Unable to parse XML file using DocumentBuilder

    Stack Overflow | 8 years ago
    java.net.SocketException: Operation timed out: connect:could be due to invalid address
  3. 0

    Create ProxyServer using Socket on Android device

    Stack Overflow | 2 years ago | Юрій Прайзнер
    java.net.SocketException: SOCKS connection failed 08-21 20:05:59.991 972-994/com.example.ura.player W/System.err﹕ at java.net.PlainSocketImpl.socksConnect(PlainSocketImpl.java:326) 08-21 20:06:00.007 972-972/com.example.ura.player W/EGL_emulation﹕ eglSurfaceAttrib not implemented
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    socket connection not working

    Oracle Community | 1 decade ago | 807597
    java.net.SocketException: Invalid argument or cannot assign requested address

    Root Cause Analysis

    1. java.net.SocketException

      Reply from SOCKS server has bad version 60

      at java.net.PlainSocketImpl.getSOCKSReply()
    2. Java RT
      PlainSocketImpl.connect
      1. java.net.PlainSocketImpl.getSOCKSReply(Unknown Source)
      2. java.net.PlainSocketImpl.doSOCKSConnect(Unknown Source)
      3. java.net.PlainSocketImpl.connectToAddress(Unknown Source)
      4. java.net.PlainSocketImpl.connect(Unknown Source)
      4 frames