Errors explanation
Main errors explanation & fixes
Last updated
Main errors explanation & fixes
Last updated
Updater has stopped working
Launch Updater.exe and after relauch Encore
If this error persist, reinstall new version from discord
Failed to ini: Dll was not found
Click on the Updater.exe in your encore folder. Wait for encore to update. Reopen encore once done. If first suggestion doesn't work, check your firewall settings on you PC and turn it off or make exceptions to Encore software.
Invalid license!
Make sure to add your key in Settings
If error persist, make sure to complete key reset on
Discord rate limit hit
Change webhook and use server webhooks option in Settings
Not Found: 404 when you try to run tasks
Check your webhooks in Settings, make sure it is able to send data to and from. Create a new one if necessary.
Loading event failed: 403 or Detected Incapsulva Solved!
Your proxies is flagged or banned. Complete Proxies testing& test manually.
Error 403 (proxy) on carting
Description: This error occurs when one proxy is used for 2+ carts within a short period. How to fix: have enough backup proxies from .txt + set CartBlockDelay in Settings
Multiple proxy bans from a single subnet
Description: If you have many proxy bans from one subnet, TM may detect your subnet entirely.
Fix: Try to use some proxies from different subnets or use fast residential proxies.
Loading event failed 401
Try deleting your cookies on your account, then re-login to those accounts. Then re-run tasks.
Also you can try change your proxies and compare.
Redirect URL wasn't found: {"redirectUrl":null,"errorType":"phone_uniqueness_error"}
Means the number is on another account (one of the main reasons)
IMAP connection failed: Imap wasn't found.
Go to your module folder and add your master address mail to your Accounts
Incorrect provider
Make sure you input correctly SMS provider name in Accounts. For example, TextChest or Ejoin
Missing or invalid default region
Needs +country code infront of number. Phone should be added in that format: +18036238823.
US numbers usually begin with +1
No tasks!
Go to your module folder, then tasks folder and edit the tasks.csv
Blank CLI after selecting task file to launch in bot
Check your task file and make sure there are no empty columns, rows or misspelled headers (case sensitive). Min and max price needed (edited)
Your access to the queue has been restricted
Description: IP ban for entering the queue
Fix: Change proxies IP (or fully subnet) or use fast resi proxies instead. Also recommend to run 1 account = 1 Proxy.
Unexpected EOF error
Usually means that server closed connection before sending full response. Maybe it's getting overloaded with requests (mostly get it with resi). Maybe it could be the time it takes to load is slower than the delays set, so all data isn't loaded before the next refresh so could return this error.
Error description for Bad queue status
One of the reasons: If you rejoin queue from same account
Accounts logout after queue/before carting
This error occurs on both US and UK events, even though it has different names:
🇺🇸 error:
U307 - UG token is invalid for other reasons🇬🇧 error:
Failed to parse event config: null
Description: TM logs out your account if you join in multiple events from same account or run single account into different queues (events) from multiple instances at the same time (no matter soft/manual). This is why the errors occurs after passing through the queue.
How to fix: Run 1 account = 1 event. A less safe solution might be to try running instances with different events with a delay, so that the tokens do not get interrupted.
Cannot GET /1c3eede2de4f438&identity_redirect=1
Delete "&identity_redirect=1" from redirect URL and use new link
Error "UG reserve exceeded"
Turn OFF RestartAfterCart in tasks
U111 - TM error during selecting seats
Description: Appears only when selecting from the list on the right.
UG token expired
Reduce the check interval for the token ["QueueCheckDelay"] in Settings
E109 - Atlas error
This sometimes happens with specific tickets; the bot then adds them to the blacklist.
It's not you - it's us when open UK cart 🇬🇧
Description: When using a single account to cart multiple events at the same time, only the first cart will remain active. Any additional cart will get an error because only one active card is allowed per account at the same time.
Solution: To avoid this, create separate accounts for multiple events which happen simultaneously: 1 account = 1 event.
Sometime it can also means that cart you open already expired
In-bot full checkout link not working
Make sure you have Encore running to open inbot browser. If it doesn't open, launch one more instance of encore. Also make sure your internet connection is up in browser
Extension full url not working
Click on reset proxy on extension and reload
U001 error after trying buy via card
Most likely your payment card got filtered. Try to use lowkey providers
U103 after trying to checkout (fraud block)
Description: Fraud block - something on your account (card/billing) flagged and causing the cancel.
Fix: Call TM (fraud department) to unblock it. Most likely will need to provide account information
Account ban for joining the queue explanation
Description: TM blocks the account's ability to join the queue. You will get Account is probably banned error. Recommend to double check manually as well, as error may appear because of proxies.
Possible reasons & solutions to avoid :
Catchall accounts
Solution: Use accounts with hotmail or any others, as TM block catchall strictly after update.
Cracked accounts with active tickets (in upcoming events section)
Solution: There is no direct solution; when purchasing such an account, a ban will happen sooner or later. Check accounts when buying and purchase from trusted suppliers.
Multiple cart attempts in a short time & Restart After carting
Solution: Setup safety run delay for CartAttemptDelay for in Settings and turn OFF Restart after carting option in
Auto-changing proxy during carting when it temporary banned
Solution: Set false for CartChangeProxy in Settings
We recommend also finding out the reason for the ban directly from support (chat/call)
