Client SOCKS Proxy Error

[robertsongaming]

I've been getting this error, when it was working fine yesterday with no changes?

I have no proxy. I've tried reinstalling the client, deleting the folder, reinstalling Java, trying a different network, resetting pc and client. followed points on:

 

Nothing's working. Any help would be appreciated.

[Patterns]

First client ran fine, got the same error on a second client. Briefly ran the second client in Mirror mode, restarted it and went back to stealth injection and it started working. 

[run escapes]

yea im having this issue too sometimes it works sometimes it doesnt

EDIT: Worked fine yesterday but woke up today and starting having issues with this problem

Edited November 23, 2019 by run escapes

[Stormtrooper]

Same issue, cant find a way to fix it

[traybakes]

same issue my friends. just started today for me. i see another post saying update to osbot 2.5.61 and mine is currently osbot 2.5.60 but is not giving me the option like normal to update? 

[GoHokies]

same issue

[traybakes]

boys i found the cure! i started up runelite and log in then thought fuck that playing is for twats and logged out closed it and looked up at the sky asked god to let it work then tried opening the bot again and this time it loaded up fine. so maybe if you try load up another client then try this one again ? or i duno sorry. good luck ! peace and love. 

[Gunman]

1 hour ago, traybakes said:

same issue my friends. just started today for me. i see another post saying update to osbot 2.5.61 and mine is currently osbot 2.5.60 but is not giving me the option like normal to update? 

Reasons your bot isn't updating to 2.5.61 is because 2.5.61 is a dev version. Which means it can be buggy and is more of a release for mass testing. And I would not recommend downloading and using that build it does have some bugs.

EDIT: Bot is down btw
EDIT2: Bot keep going up and down so just open the bot every like 10-15 minutes if you can to check.

Edited November 23, 2019 by Gunman

[run escapes]

31 minutes ago, Gunman said:

Reasons your bot isn't updating to 2.5.61 is because 2.5.61 is a dev version. Which means it can be buggy and is more of a release for mass testing. And I would not recommend downloading and using that build it does have some bugs.

EDIT: Bot is down btw
EDIT2: Bot keep going up and down so just open the bot every like 10-15 minutes if you can to check.

Yea this is my experience too. tried to load up 10 bots but only 2 of them actually loaded up. Had to restart the other 8 like 4 or 5 times for them to work so i just figured fuck it and gonna wait for them to fix it  

[Protoprize]

For me, I just disabled my firewall and any tunneling software, seems to be all good?

[wildcats2020]

• When can we expect this issue to be fixed? and is the staff aware of this issue?

[Tinzilla]

I'm having this issue too!

Edited November 23, 2019 by Tinzilla

[Failed Zerk]

I was having the same problem. Heres an easy fix. If you're using windows 10 open windows defender firewall, go to advanced settings on the left hand side, click inbound rules then click new rule on the right hand side. Click program, then next. Now, right click on your osbot .jar file, go to properties, security, next to object name will be the path to the file. copy and paste it into the program path, click next again and click allow connection, name the rule osbot and save it, you will now be able to run osbot without a problem.

[Farmzz]

1 hour ago, gvance79 said:

I was having the same problem. Heres an easy fix. If you're using windows 10 open windows defender firewall, go to advanced settings on the left hand side, click inbound rules then click new rule on the right hand side. Click program, then next. Now, right click on your osbot .jar file, go to properties, security, next to object name will be the path to the file. copy and paste it into the program path, click next again and click allow connection, name the rule osbot and save it, you will now be able to run osbot without a problem.

Did not fix it, thanks though.

[Naked]

@Token @Patrick Have any insight on this? Seems to be widespread.

 

Edit: It appears to be a runescape server outage.

Edited November 24, 2019 by Naked