1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Bug Failed to bind to game client (WINDOWS 10)

Discussion in 'Client & Site Support' started by Jimchance69, Sep 7, 2018.

  1. Jimchance69

    Joined:
    Sep 6, 2018
    Messages:
    1
    Likes Received:
    0
    I'm sure many of you have had this issue, and yes I have tried everything that I have seen on the forums and elsewhere. Here is my log:

    [Debug] Java Home: c:\program files (x86)\runemate\jre
    [Debug] Java Version: 8u121 x86 (Oracle Corporation)
    [Debug] Maximum Heap Size: 743MB
    [Debug] RuneMate Version: 2.87.0
    [Debug] Operating System: Windows 10 x64
    [Debug] C:\Users\kaiden\jagexcache is a cache root according to the registry.
    Checking for a new game client every second for two minutes or until one is found.
    Found a new game instance after 5 seconds.
    [Clouse] Downloaded 1000 human mouse movements selected for you by Clouse.
    java.lang.Exception: Failed to bind to the virtual machine.
    at nul.iiIiIIiiiIIIi.for(asc:31)
    at nul.IIiiIIiiiiiii.run(pad:107)
    Caused by: java.rmi.ConnectException: Connection refused to host: 10.8.8.56; nested exception is:
    java.net.ConnectException: Connection timed out: connect
    at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619)
    at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
    at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
    at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:342)
    at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
    at nul.iIiIiIiiIIiII.for(qvc:185)
    at nul.iiIiIIiiiIIIi.for(asc:137)
    ... 1 more
    Caused by: java.net.ConnectException: Connection timed out: connect
    at java.net.DualStackPlainSocketImpl.connect0(Native Method)
    at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    at java.net.Socket.connect(Socket.java:589)
    at java.net.Socket.connect(Socket.java:538)
    at java.net.Socket.<init>(Socket.java:434)
    at java.net.Socket.<init>(Socket.java:211)
    at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)
    at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:148)
    at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)
    ... 7 more
     
  2. Negrita

    Joined:
    Jan 28, 2017
    Messages:
    491
    Likes Received:
    183
    looks firewall related. But feel free to contact me on Slack and I'll try to fix it.
     
    Jimchance69 likes this.
  3. youramazingames

    Joined:
    Oct 24, 2015
    Messages:
    79
    Likes Received:
    13
    If you work out a fix, please send it!
     
  4. Negrita

    Joined:
    Jan 28, 2017
    Messages:
    491
    Likes Received:
    183
    Can't reproduce it, so I'd have to TV someone who has the issue
     
  5. Dont Ban me Bro

    Joined:
    Jul 28, 2018
    Messages:
    52
    Likes Received:
    12
    I figured it all out now. I have been trying in everything I could imagine.
    It turns out it is actually not the firewall but the antivirus itself.

    Turn off the antivirus and it works perfectly. Turn it on and it crashes it.

    Using AVG atm.
     
  6. raffy

    Joined:
    Sep 12, 2018
    Messages:
    1
    Likes Received:
    0
    Getting this same response on a macbook air. Any solutions?
    Getting this same response on a macbook air. Any solutions? Do you mind TV'ing with me?
     

    Attached Files:

  7. BrokenSword

    BrokenSword Banned for Scamming

    Joined:
    Aug 4, 2018
    Messages:
    65
    Likes Received:
    8
    Whenever I get this I just close Runemate, close the Runescape client, then open Runemate back up and open the Runescape client from within Runemate and it works fine.
     
  8. paulsamaroo

    Joined:
    Jun 20, 2015
    Messages:
    279
    Likes Received:
    31
    Had the same issue. Seems like a firewall issue. When I disabled my Avast antivirus, and enabled Windows Defender, when I launched a bot, Windows UAC prompted me to allow network access to Jagex Launcher. Problem solved.
     
    Dont Ban me Bro likes this.

Share This Page

Loading...