[josber]

Hi im having this trouble with my runemate, i've read i might be internet conection problem, i run several test and same result my isp is running perfectly
I've being told to tag you @American Express any idea? attached logs

 

[american express]

I've being told to tag you @American Express any idea? attached logs

Whoever told you to do that is an idiot.

Are you playing over WiFi or ethernet? If WiFi, try an ethernet connection and see if you still get this issue.

The session expired error is almost always due to a bad network connection. If you use a VPN or Proxy, they can sometimes be the cause too.

Can you try the following within command prompt:

ping www.google.com -n 100

And post your results.

 

[josber]

Paquetes: enviados = 100, recibidos = 97, perdidos = 3
(3% perdidos),
 

And post your results.

packets: sent = 100,received = 97, lost = 3
(3% loss),
aproximate round trip times in mili-seconds:
minimun = 76 ms, maximun = 136, Average = 92ms (here i was using the internet while testing)

______second ping test_________

packets: sent = 100,received = 100, lost = 0
(0% loss),
aproximate round trip times in mili-seconds:
minimun = 43 ms, maximun = 57, Average = 76ms

 

[american express]

Paquetes: enviados = 100, recibidos = 97, perdidos = 3
(3% perdidos),
 

packets: sent = 100,received = 97, lost = 3
(3% loss),
aproximate round trip times in mili-seconds:
minimun = 76 ms, maximun = 136, Average = 92ms (here i was using the internet while testing)

______second ping test_________

packets: sent = 100,received = 100, lost = 0
(0% loss),
aproximate round trip times in mili-seconds:
minimun = 43 ms, maximun = 57, Average = 76ms

Are you playing over WiFi or ethernet? If WiFi, try an ethernet connection and see if you still get this issue.

The session expired error is almost always due to a bad network connection. If you use a VPN or Proxy, they can sometimes be the cause too.

 

[josber]

this session expiring only happens when running the bot, if i play it never unlogs me.. im wired conected to the router, my internet comes via microtik(wireless from isp)...

 

[bean.]

Is this everytime you try and bot? As I know this is an issue if you leave RM open for ages and not run anything. For example, this happens to me, if I leave RM open on my computer for the day, with no bot running, and then try to start a bot it will say session expired. Or if i put my computer to sleep.

So maybe just try restart the client and it should fix the issue.

 

[josber]

Is this everytime you try and bot? As I know this is an issue if you leave RM open for ages and not run anything. For example, this happens to me, if I leave RM open on my computer for the day, with no bot running, and then try to start a bot it will say session expired. Or if i put my computer to sleep.

So maybe just try restart the client and it should fix the issue.

no bro i'm able to run a bot everytime i open the RM client but it plays about 15-45minutes then the error comes up... i cant leave my pc alone for about 1 hour because when i come back im loged out from osre and the RM says "session expired" and even in the log the last thing it says is "session expired" in the RM log and BOT log... this is driving me crazy

 

[bean.]

Yeah must be a connection issue, or like lag spikes on your modem, is all I can think of. Happened to me too when my internet was running shit for a while. Maybe just try restart modem etc, worked for me

 

[folklore]

If you have multiple computers, you can try running that ping thing on different devices and see whether the packet loss problem is the computer's Ethernet hardware or the modem

 

[josber]

i've run the test several times and there's not packet loss issue...

 

[bean.]

Reformat your pc.

Problem solved

 

[josber]

mm i'll try in a fresh installed os and let you know
 
well... i run it on a fresh instaled win10, and same thing happening, yesterday i played about 10hrs by my self and the game didnt kick me so im pretty sure the session expiring issue is related to the RM... i did ping google -n 1000 and got 2% packet loss... i think you should check your "expiring method.." just my point of view... is not a problem happening only to me i've found a few others with the same.

 

[folklore]

No doubt there is a bug in RuneMate's networking if it can't retry on failure. afaik sessions renew every 15 or 30 mins so Runemate client should have plenty of time for retries

 

[josber]

well nothing to do i've read about 5 other similar threads and there's even one from 2015... 4years ago and still the same :/
 
@American Express i did the tracert

1 * * * Tiempo de espera agotado para esta solicitud.
2 * * * Tiempo de espera agotado para esta solicitud.
3 * * * Tiempo de espera agotado para esta solicitud.
4 * * * Tiempo de espera agotado para esta solicitud.
5 * * * Tiempo de espera agotado para esta solicitud.
6 * * * Tiempo de espera agotado para esta solicitud.
7 * * * Tiempo de espera agotado para esta solicitud.
8 * * * Tiempo de espera agotado para esta solicitud.
9 * * * Tiempo de espera agotado para esta solicitud.
10 * * * Tiempo de espera agotado para esta solicitud.
11 50 ms 47 ms 49 ms 104.25.114.115

and after ping www.runemate.com -n 100 got 4% packet loss.

Could this be my problem? any suggestion to let RM work at least 2hrs continously?

Logs with 3 differents bots. :

[Clouse] Downloaded 990 human mouse movements selected for you by Clouse.
Failed to extend the session... (900 seconds remaining)
Session does not exist or has expired. Please restart.
___________________________________________________________________
Failed to extend the session... (900 seconds remaining)
Session does not exist or has expired. Please restart.
Failed to extend the session... (448 seconds remaining)
Failed to extend the session... (223 seconds remaining)
___________________________________________________________________
OK
OK
OK
OK
OK
Failed to extend the session... (899 seconds remaining)
OK
OK
OK
OK
OK
OK
OK
OK
Session does not exist or has expired. Please restart.
Failed to extend the session... (448 seconds remaining)
Failed to extend the session... (223 seconds remaining)