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 the Game Client because of an Exception Bug

Discussion in 'Client & Site Support' started by Skelitorus, May 13, 2020.

Tags:
  1. Skelitorus

    Joined:
    Apr 18, 2020
    Messages:
    1
    Likes Received:
    2
    Hello, my client was working perfectly fine when it just stopped working and gave me that 'Failed to Bind to the Game Client because of an Exception' crap..I unistalled/reinstalled RM/OSRS, cleared caches....a bunch of stuff but it still does not work. Please help!
     
    MrXelaXD and Jdoggg like this.
  2. Jdoggg

    Joined:
    May 9, 2020
    Messages:
    1
    Likes Received:
    0
    I am in the same boat...
     
  3. MrXelaXD

    Joined:
    May 14, 2020
    Messages:
    1
    Likes Received:
    0
    The same happens to me
     
  4. brbol

    Joined:
    Jul 18, 2018
    Messages:
    1
    Likes Received:
    0
    hi @Cloud i have the same problem Failed to bind to the game cleint because of an exception
     
  5. Holden Brad147

    Joined:
    Jul 4, 2020
    Messages:
    7
    Likes Received:
    2
    same problem


    [Debug] Java Home: c:\program files (x86)\runemate\jre
    [Debug] Java Version: 1.8.0_181 x86 (Oracle Corporation)
    [Debug] Maximum Heap Size: 743MB
    [Debug] RuneMate Version: 2.107.1
    [Debug] Operating System: Windows 10 x64
    [Debug] C:\Users\Holden\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 4 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.iIiiiiiiiiIII(ybd:78)
    at nul.iIiiiIiiiiiII.iIiiiiiiiiIII(ybd:137)
    at nul.IiiIiIiiiIiII.run(fwc:73)
    Caused by: java.rmi.ConnectException: Connection refused to host: 192.168.254.64; 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:338)
    at sun.rmi.registry.RegistryImpl_Stub.lookup(RegistryImpl_Stub.java:112)
    at nul.iiIIIIiiIiiii.iIiiiiiiiiIII(uxc:64)
    at nul.iIiiiIiiiiiII.iIiiiiiiiiIII(ybd:25)
    ... 2 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)
    ... 8 more
     

Share This Page

Loading...