Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Buy OSRS Gold

Sell OSRS Gold
TacoManStan

[Quick Tutorial] The "Maximum Instances" Issue

Recommended Posts

The "Maximum Instances" Issue - Explained

Ever get the following message when you try to start a script, or something similar?

FOz9jOs.png

From what I've seen, there isn't a single thread anywhere that is devoted entirely to explain why this happens. Sure, plenty of people explain how to fix it, but how many times has someone really taken the time to explain why it happens? Well, that's why I've made this thread. Instead of telling you to "just deal with it", I've decided to provide a bit of an explanation as to why it happens, and how to avoid it.

Explanation

While you are running a script, TRiBot continuously pings the server letting the server know a script is currently being run on your TRiBot account. This is how the Instance Manager works. When you stop the script or close the TRiBot client, TRiBot pings the server one last time to let the server know that the script is no longer running. Under normal circumstances, you can then immediately start up another (or the same) script.

However, if your TRiBot client is closed improperly (your computer crashed, TRiBot was terminated via Task Manager, etc), the server never receives the message indicating that the script has been stopped. As a result, you will see the infamous message shown above even when you don't even have TRiBot open anymore!

How to Solve It

This can obviously be incredibly frustrating. Luckily for you, you aren't out of options. If the server doesn't receive an "update ping" from the TRiBot client for 15 minutes, it will assume there was a problem, and automatically remove the instance from your Instance Manager. This means that if this ever happens to you, all you need to do is wait for 15 minutes for the instance to "time out" on the server, and you will be ready to start up another script once again!

Note: If you are VIP or VIP-E, you can instantly "Kill" an instance by using the Instance Manager mentioned above.

How to Prevent It

Especially because the solution to this problem oftentimes involves waiting for 15 minutes until you can do anything, the best solution to the problem is to prevent it entirely. While it is unfortunately true that the occasional computer crash is unavoidable, and that you sometimes have no choice but to use the Task Manager to terminate a frozen TRiBot client, you should avoid these situations whenever you can.

To help minimize the chances of unexpected "bad stuff" happening, make an effort to do the following:

  1. If you run your bots on a VPS, use the most stable and reliable VPS that you can find. Sometimes paying an extra dollar or 2 is worth avoiding the headache that constantly running into this problem can cause.
  2. If you run your bots on your own computer, ensure that you have enough RAM and CPU power to handle the number of bots that you are running. Just because "it's working right now" doesn't mean that it will stay that way. I would recommend staying below 80%-90% both CPU and RAM usage, and even less if you are using the computer for other things as well.
  3. Don't terminate TRiBot clients using the Task Manager unless you absolutely have to! While this oftentimes does work properly, as I have mentioned it above, it can also work very improperly. If you need to close a lot of clients at once, spend the extra 30 seconds to open each one and close the client as intended.
    Think of this like turning your computer off using the power button; it usually doesn't cause any problems, but it certainly can.

Conclusion

Well that's about all I have to say on this subject for the time being. If anyone has anything else they would like to add, just let me know, and if it isn't utter and complete nonsense, I will add it to this thread.

Good luck everyone, and happy botting!

Edited by TacoManStan
  • Like 4

Share this post


Link to post
Share on other sites
Just now, netgear said:

This is very unfortunate. 

I am experiencing occasional lag spikes because of my shitty connection. Every time this happens I get this message and the script shuts off. This needs to be fixed.

The lack of interest from the management of Tribot amazes me.

Read the thread again, and you will realize that there is nothing to "fix". The very purpose of the Instance Manager is to allow you to kill instances when you run into issues like the one you have just described.

Share this post


Link to post
Share on other sites
2 minutes ago, TacoManStan said:

Read the thread again, and you will realize that there is nothing to "fix". The very purpose of the Instance Manager is to allow you to kill instances when you run into issues like the one you have just described.

It requires you to have a very steady connection in order to not run into this problem. Instead of the bot retrying it shuts down completely, which is unfortunate. 

I have a paid VPN that runs into trouble with this system once or even twice every hour. 

Share this post


Link to post
Share on other sites

Hi, currently having this problem, maximum instances reached not allowing me to run tribot. I've had this happen before and I've always been able to either terminate the instance or just wait for the 15 minute timeout. But neither of those work, the instance manager shows no instances and it's been over 30 minutes since I last tried and I am still receiving the same message. Any ideas? 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Our picks

    • Hi everyone,

      I'd like to thank everyone for their patience in this transition period. Since last week, we've worked out the remaining bugs with this integration.

      Some users have still been having issues with connecting their forums account to their Auth0 account. To resolve this, we've imported all forums accounts into Auth0.

      Unfortunately, the accounts which were imported today were using an unsupported password hashing algorithm. Hence, random passwords were set during the import.

      What does this mean for me?

      If you've previously linked your forums account to your Auth0 account, you don't have to do anything. Nothing changes for you.


      If you haven't logged in via our new login yet,

      Try logging in with your forums email address and the last password you used


      If you are unable to login, please use the "Forgot password" tool on the login page:
      Follow the instructions to reset your password
       
        • Like
      • 1 reply
    • Hello everyone,

      Last week we tried to roll out Auth0 Login, but we lost that battle. Now it's time to win the war!

      Important changes

      When logging into the client, you'll now have to enter your Auth0 account credentials instead of your forums credentials

      Note: 2FA is still handled through your forums account (for the time being)



      Changes for existing users

      You'll have to link your Auth0 account to your forums account here: https://tribot.org/forums/settings/login/?service=11


      Auth0 accounts have been created for most existing users. Please use your forums email address and password to login.



      Important notes

      Make sure to verify your email address upon creating a new Auth0 account


      When we mention your Auth0 account, we mean your account used for auth.tribot.org as displayed below
      • 71 replies
    • To better support the upcoming changes (TRiBot X, new repository), we're switching our login handler to Auth0. Instead of logging in with the standard form, you'll now be required to login through our Auth0 application.

      All existing accounts which have been used within approximately the past year have been imported into Auth0 using the same email and password combination which has been stored on the forums.

      What does this mean for users?

      Your account credentials are now even more securely stored


      You'll be able to login via Facebook, Google, and others in the future


      Is there anything users have to do differently now?

      Existing users: You'll have to login with the standard login, open your Account Settings, then link your Auth0 account


      New users: You'll be redirected to our Auth0 app (auth.tribot.org) where you'll be able to create an account


      Why was this change made?

      The new apps we are creating (such as the new repository) aren't able to use the forums to handle user logins


      To centralize all user accounts in one area


      To ensure that the client login doesn't go down when the forums are having problems


      To speed up our development


      Other considerations

      There's no documentation or official support for using Invision Community combined with Auth0, so there are still a few kinks we're working out


      We're in the works of creating an account management panel specifically for Auth0 accounts (ETA August)


      It's not possible to change email addresses for the time being (this will be resolved this August)


      Changing passwords is a weird process for the time being. To change your password, you'll have to use the "Don't remember your password" tool on the Auth0 login page
        • Like
      • 11 replies
    • Over the past month, we've been working hard on TRiBot's new repository - a much needed update. This change has been deemed necessary for TRiBot X, and will allow us to really speed up development of all aspects of TRiBot.

      Today we are going to share what we've been working on!


      Now you must be wondering what kind of features the new repository will have.... well, you'll have to be patient for a little while longer. We're still figuring out various technical aspects so we can't provide answers to all possible questions. We're also focusing on development rather than writing about it so that everyone can get access to our latest developments at lightning speed. I will however answer a few users' questions.

      We're planning on a release of this early to mid August, giving users some goodies before TRiBot X's release.

      Thank you all for being patient. I hope everyone is excited as much as I am!
        • Like
      • 17 replies
    • Over the past few months, I’ve been working diligently on a new project - TRiBot X. Everything has been written from the ground up, with all of the best practices of software engineering. Every aspect of TRiBot has been re-imagined to support three main goals: flexibility, useability, and reliability.
        • Like
      • 50 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...