So one of my proxy IP's keeps giving me a bot initialization error, however I have checked that it's online and working with Proxifier. It was working a couple hours ago with Osbot so I know the information is in correct. So I'm not sure what the issue is? The information is in correct and the proxy is online, yet I'm now getting instant bot initialization error ? I've never had this happen before, any ideas? (Injection mode)

Edited April 20, 20178 yr by Convergence

4 minutes ago, Convergence said:

So one of my proxy IP's keeps giving me a bot initialization error, however I have checked that it's online and working with Proxifier. It was working a couple hours ago with Osbot so I know the information is in correct. So I'm not sure what the issue is? The information is in correct and the proxy is online, yet I'm now getting instant bot initialization error ? I've never had this happen before, any ideas?

 

getting the same issue but on regular connection. never had it happen on previous version of bot. 

Same issue here. Several proxies, various IP ranges, mirrored or injected. Was working fine in .118 this morning now I can't connect at all.

Edited April 20, 20178 yr by sudoinit6

same here

Same

If you are all using Mirror Client, it is currently broken with the newest version of OSBot that @Alek pushed (.119). I have alerted him of the issue and they are working on a fix

2 minutes ago, Failed4life said:

If you are all using Mirror Client, it is currently broken with the newest version of OSBot that @Alek pushed (.119). I have alerted him of the issue and they are working on a fix

I Only use injection, forgot to say that I'll add it to op.

I released OSBot 2.4.119 17 days ago, which should have been plenty of time for you guys to test it out before I forced the newest version. Unfortunately you will now have to wait until MGI can take a look and make a fix.

2 minutes ago, Alek said:

I released OSBot 2.4.119 17 days ago, which should have been plenty of time for you guys to test it out before I forced the newest version. Unfortunately you will now have to wait until MGI can take a look and make a fix.

Yeah, I downloaded it and had the same issue but I just assumed I had to enable some dev mode or something in order to get it to work so I just went back to the normal client.

 

Now I know better

 

2 minutes ago, sudoinit6 said:

Yeah, I downloaded it and had the same issue but I just assumed I had to enable some dev mode or something in order to get it to work so I just went back to the normal client.

 

Now I know better

 

That sucks! We take the development builds pretty seriously and although we cant really force all of our customers to test these versions, it certainly helps both us and the customer.

3 minutes ago, Alek said:

That sucks! We take the development builds pretty seriously and although we cant really force all of our customers to test these versions, it certainly helps both us and the customer.

Meh, I am still learning the ropes so no biggie, in the future I will definitely test and complain earlier

 

So I am in the states, does this mean that the fix probably wont be done "tonight"?

 

edit: Oh and if there is any other info you need about my setup to troubleshoot let me know.

Edited April 20, 20178 yr by sudoinit6

Using injection and proxy still broken, it's not just on mirror mode

Edited April 21, 20178 yr by sp3cpk

FYI = If I use the CLI and add the "-world" flag it works. If I take the flag off it breaks.

 

 

Strange times....

 

Thank god its not just me!

Once again you will have to unfortunately wait for a fix since the bot is now on stable release. I had the bot sit as an optional dev build for 17 days with no complaints.