Troubleshooting

Connection Issues

Chrome Remote Debugging Not Working

Symptom: Bot fails to connect to Chrome with error about debugger address. Cause: Chrome instance not started with remote debugging enabled. Solution:

Close all Chrome instances completely
Open Command Prompt (CMD) as Administrator

Navigate to Chrome installation directory:

cd "C:\Program Files\Google\Chrome\Application"

Start Chrome with debugging for FIFA:

chrome.exe --remote-debugging-port=9250 --user-data-dir="C:/chromedriver2"

In a separate CMD window, start Chrome for WhatsApp:

chrome.exe --remote-debugging-port=9222 --user-data-dir="C:/chromedriver3"

Log into FIFA Web App in the first window
Log into WhatsApp Web in the second window
Run the bot script

Important: You must use different user-data-dir paths for each Chrome instance. Using the same path will cause conflicts.

”Element Not Found” Errors

Symptom: Bot crashes with NoSuchElementException or “element not found” errors. Common Causes:

1. EA Updated the Web App UI

Symptom: Bot suddenly stops working after an EA update.Solution:

XPath selectors may have changed
Inspect the element in Chrome DevTools (F12)
Update the XPath in the corresponding function

Example:

# Old XPath
driver.find_element_by_xpath("/html/body/main/section/...[old path]")

# Updated XPath after EA update
driver.find_element_by_xpath("/html/body/main/section/...[new path]")

Check the FIFA Bot community forums or Discord for updated XPaths after EA updates.

2. Page Not Fully Loaded

Symptom: Bot clicks too fast before elements appear.Solution:

Increase time.sleep() delays in the affected function

Use explicit waits instead of fixed sleeps:

from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC
from selenium.webdriver.common.by import By

# Wait up to 10 seconds for element
element = WebDriverWait(driver, 10).until(
    EC.presence_of_element_located((By.XPATH, "your_xpath_here"))
)
element.click()

3. Wrong Screen Context

Symptom: Bot tries to interact with element on wrong screen.Solution:

Add navigation checks before operations

Example:

# Verify we're on transfer market screen
if len(driver.find_elements_by_xpath("/html/body/main/section/nav/button[3]")) > 0:
    clickBuscar()
else:
    irMercadoTransferencias()
    clickBuscar()

4. Session Expired

Symptom: Bot can’t find elements because FIFA session logged out.Solution:

Bot should auto-detect and call reLogin()
If not working, manually trigger relogin:
- Update Firebase: {"comando": "RELOGIN"}
- Or restart bot after logging in manually

Update Password:

# In reLogin() function (line ~904)
input.send_keys("YourActualPassword")  # Change "Warewolf10"

Firebase Connection Issues

Symptom: Bot starts but remote control doesn’t work. Cause: Firebase authentication or database issues. Diagnostic Steps:

Check Firebase initialization:

# Should print "OK" without errors
db.update({"comando":"OK"})
print("Firebase connected successfully")

Verify Firebase config:

config = {
  "apiKey": "AIzaSyCO09JciLlqV3N4K7hV90qK_8XBvGBaCLI",
  "authDomain": "fifabot-e4c0b.firebaseapp.com",
  "databaseURL": "https://fifabot-e4c0b.firebaseio.com",
  "storageBucket": "fifabot-e4c0b.appspot.com"
}

Test database write:

db.child("test").set({"status": "working"})

Common Fixes:

API Key Invalid

Your Firebase project credentials may have changed
Go to Firebase Console → Project Settings → General
Copy the web app configuration
Replace config dictionary in the bot script

Database Rules Too Restrictive

Go to Firebase Console → Realtime Database → Rules

For testing, set to:

{
  "rules": {
    ".read": true,
    ".write": true
  }
}

These rules allow anyone to read/write. In production, implement proper authentication.

Network/Firewall Blocking

Check if firewall blocks port 443 (Firebase uses HTTPS)
Try disabling antivirus temporarily
Test with mobile hotspot to rule out network issues

WhatsApp Automation Issues

Messages Not Sending

Symptom: Bot runs but doesn’t send WhatsApp notifications. Checklist:

✅ WhatsApp Web is open in Chrome on port 9222
✅ eW checkbox is enabled in bot UI
✅ Target chat is first in WhatsApp sidebar (pin it)
✅ WhatsApp Web is not showing “Phone not connected” warning

XPath Issues: WhatsApp Web updates frequently break XPaths. Current XPaths (as of script):

# Chat selection
chat = driverWhatsapp.find_element_by_xpath(
    '//*[@id="pane-side"]/div[1]/div/div/div/div/div/div[2]/div[2]/div[1]/span/span'
)

# Message input
posicionar = driverWhatsapp.find_element_by_xpath(
    "//*[@id='main']/footer/div[1]/div[2]/div/div[2]"
)

# Send button
botonEnviar = driverWhatsapp.find_element_by_xpath(
    "//*[@id='main']/footer/div[1]/div[3]/button/span"
)

How to Find Updated XPaths:

Open WhatsApp Web in Chrome
Press F12 (Developer Tools)
Click the “Select Element” tool (Ctrl+Shift+C)
Click the element you want (chat, input box, send button)
In DevTools, right-click the highlighted HTML
Copy → Copy XPath
Update the bot script

Consider using CSS selectors instead of XPath for better stability:

chat = driverWhatsapp.find_element_by_css_selector('span[title="Contact Name"]')

Screenshots Not Sending

Symptom: Text messages work but screenshots fail. Possible Causes:

Clipboard Issues (Windows)

Solution:

Ensure win32clipboard is installed:
```
pip install pywin32
```
Restart Python after installing
Check if other apps are accessing clipboard

PIL/Pillow Not Working

Solution:

Reinstall Pillow:

pip uninstall Pillow
pip install Pillow

Verify screenshot.png is being created in bot directory

Image Send Button Changed

Solution:

WhatsApp changed the send button XPath

Current XPath:

botonEnviar = driverWhatsapp.find_element_by_xpath(
    "//*[@id='app']/div/div/div[2]/div[2]/span/div/span/div/div/div[2]/span/div/div"
)

If not working, inspect element and update

Bot Behavior Issues

Bot Stops Unexpectedly

Symptom: Bot runs for a while then stops without error. Common Causes:

1. Exception in Main Loop

Diagnostic:

Check console for “ALGO OCURRIO” messages
If recovery fails twice, bot exits

Solution:

Improve error handling in iniciar() function

Add logging to identify which operation fails:

try:
    print("About to click buscar")
    clickBuscar()
    print("Successfully clicked buscar")
except Exception as e:
    print(f"Failed: {e}")

2. Session Timeout

Symptom: Bot stops after 1-2 hoursSolution:

EA kicks you out after inactivity

Enable remote relogin:

# In Firebase, set:
{"comando": "RELOGIN"}

Or implement auto-relogin detection:

if len(driver.find_elements_by_xpath('//*[@id="btnLogin"]')) > 0:
    reLogin()

3. Rate Limiting

Symptom: Bot slows down or stops after many requestsSolution:

EA implements rate limiting

Increase delays between actions:

rapido.set(1)  # Use normal mode instead of fast

Increase itera value (e.g., from 10 to 20)

Add random delays:

import random
time.sleep(random.uniform(2, 5))

4. Transfer List Full

Symptom: Bot can’t list items, stops buyingSolution:

Increase itera frequency to clear sold items more often
Manually clear unsold items
Check if prices are too high (items not selling)

Not Finding Items to Buy

Symptom: Bot searches but never clicks items. Diagnostic:

# Add to clickEncontrado() function
print(f"Found {len(driver.find_elements_by_xpath('/html/body/main/section/section/div[2]/div/div/section[1]/div/ul/li/div'))} items")

Solutions:

1. Max Price Too Low

Market prices increased
Run revisarPrecio() or buscarRango() to find new range
Manually adjust maximo field upward

2. Filters Too Narrow

Loosen search criteria:
- Remove club/nationality filters
- Expand position to multiple roles
- Try different leagues
Click “Selecciones” to apply updated filters

3. High Competition

Other bots/snipers are faster
Solutions:
- Use fast mode (rapido=2)
- Target less popular items
- Search during off-peak hours

Buying But Not Selling

Symptom: Items bought successfully but stay in transfer list. Causes:

Prices Too High:
- Check if final price is competitive
- Compare to lowest market price
- Run buscarRango() to find realistic sell price
Item Type Changed:
- EA may have released new cards (TOTW, promos)
- Your card type is now outdated
- Check market manually and adjust strategy

definirPrecio() Failing:

Add logging:

def definirPrecio():
    if len(driver.find_elements_by_xpath("...")) > 0:
        print("Setting prices...")
        # existing code
    else:
        print("FALSA ALARMA - price fields not found")

Performance Issues

Bot Running Too Slowly

Symptom: Searches taking 10+ seconds each. Optimizations:

Enable Fast Mode:
```
rapido.set(2)  # In UI or code
```

Reduce Unnecessary Waits:

# Instead of:
time.sleep(5)

# Use:
time.sleep(2)

Disable Screenshots:
- Uncheck eSS checkbox
- Screenshots slow down execution significantly

Optimize Selenium:

from selenium.webdriver.chrome.options import Options
opts = Options()
opts.add_experimental_option('debuggerAddress', 'localhost:9250')
opts.add_argument('--disable-extensions')
opts.add_argument('--disable-gpu')
opts.add_argument('--no-sandbox')
driver = webdriver.Chrome(options=opts)

Faster execution increases ban risk. Balance speed with safety.

High CPU/Memory Usage

Symptom: Chrome using excessive resources. Solutions:

Close Unused Tabs:
- Only keep FIFA and WhatsApp tabs open
- Close extensions/background tabs
Restart Chrome Periodically:
- Close Chrome instances
- Clear user data directories:
  rmdir /s C:\chromedriver2\Default\Cache rmdir /s C:\chromedriver3\Default\Cache
- Restart debugging sessions

Limit Screenshot Frequency:

Only enable screenshots for errors:

def enviarScreenshot():
    if error_occurred:  # Only on errors
        driver.save_screenshot(...)

Security & Ban Prevention

Account Banned or Flagged

Symptom: FIFA account receives warnings or temporary bans. Prevention Strategies:

1. Humanize Bot Behavior

Add random delays:

import random
time.sleep(random.uniform(1, 3))

Vary search patterns (don’t repeat same item)
Take breaks (stop bot for 30 min every 2 hours)

2. Limit Daily Volume

Don’t buy/sell more than 50-100 items per day

Set cuantos limit:

if cuantos >= 100:
    enviarWhatsapp("Daily limit reached, stopping")
    switchoff()
    break

3. Avoid Peak Detection Times

EA monitors heavily during:
- New content drops (6PM UK time)
- Weekend League rewards (Thursdays)
- TOTS/major promos
Bot during off-peak hours (2-6 AM local time)

4. Use Realistic Prices

Don’t undercut market by huge margins
Follow market trends
Avoid suspicious patterns (same price repeatedly)

Disclaimer: Using bots violates EA’s Terms of Service. Your account may be permanently banned. Use at your own risk.

Advanced Troubleshooting

Enable Debug Logging

Add comprehensive logging to diagnose issues:

import logging

# Setup logging
logging.basicConfig(
    filename='fifa_bot.log',
    level=logging.DEBUG,
    format='%(asctime)s - %(levelname)s - %(message)s'
)

# In functions:
def clickBuscar():
    logging.info("Attempting to click Buscar button")
    try:
        driver.find_element_by_xpath("...").click()
        logging.info("Successfully clicked Buscar")
    except Exception as e:
        logging.error(f"Failed to click Buscar: {e}")
        raise

Log file will contain detailed execution trace for debugging.

Check Selenium Driver Version

Symptom: Selenium commands fail randomly. Solution: Ensure ChromeDriver matches Chrome version:

Check Chrome version:
- Open Chrome → Three dots → Help → About Google Chrome
- Note version (e.g., 120.0.6099.109)
Download matching ChromeDriver:
- Visit https://chromedriver.chromium.org/downloads
- Download version matching your Chrome

Replace old ChromeDriver:

# Windows
move chromedriver.exe C:\Windows\System32\chromedriver.exe

Verify:

from selenium import webdriver
driver = webdriver.Chrome()
print(driver.capabilities['browserVersion'])

Remote Debugging Not Releasing Ports

Symptom: “Port already in use” error when starting Chrome. Solution:

Find processes using the port:

netstat -ano | findstr :9250
netstat -ano | findstr :9222

Kill the process:
```
taskkill /PID <process_id> /F
```

Or use different ports:

opts.add_experimental_option('debuggerAddress', 'localhost:9251')

chrome.exe --remote-debugging-port=9251 --user-data-dir="C:/chromedriver2"

Getting Help

If you’re still experiencing issues:

Check the Logs:
- Console output
- fifa_bot.log if enabled
- Screenshots in bot directory
Gather Information:
- What function is failing?
- Error message (full traceback)
- Chrome/ChromeDriver versions
- When did it stop working?
Community Resources:
- GitHub Issues (if open source)
- Discord/Telegram bot communities
- Stack Overflow (selenium + fifa tags)

Provide Debug Info:

import sys
print(f"Python: {sys.version}")
print(f"Selenium: {selenium.__version__}")
print(f"Chrome: {driver.capabilities['browserVersion']}")

When asking for help, always include:

Python version
Selenium version
Chrome version
Full error message
Relevant code snippet

Get Started

Core Features

Guides

Reference

Connection Issues

Chrome Remote Debugging Not Working

”Element Not Found” Errors

Firebase Connection Issues

WhatsApp Automation Issues

Messages Not Sending

Screenshots Not Sending

Bot Behavior Issues

Bot Stops Unexpectedly

Not Finding Items to Buy

Buying But Not Selling

Performance Issues

Bot Running Too Slowly

High CPU/Memory Usage

Security & Ban Prevention

Account Banned or Flagged

Advanced Troubleshooting

Enable Debug Logging

Check Selenium Driver Version

Remote Debugging Not Releasing Ports

Getting Help

Build docs developers (and LLMs) love

Get Started

Core Features

Guides

Reference

​Connection Issues

​Chrome Remote Debugging Not Working

​”Element Not Found” Errors

​Firebase Connection Issues

​WhatsApp Automation Issues

​Messages Not Sending

​Screenshots Not Sending

​Bot Behavior Issues

​Bot Stops Unexpectedly

​Not Finding Items to Buy

​Buying But Not Selling

​Performance Issues

​Bot Running Too Slowly

​High CPU/Memory Usage

​Security & Ban Prevention

​Account Banned or Flagged

​Advanced Troubleshooting

​Enable Debug Logging

​Check Selenium Driver Version

​Remote Debugging Not Releasing Ports

​Getting Help

Build docs developers (and LLMs) love

Connection Issues

Chrome Remote Debugging Not Working

”Element Not Found” Errors

Firebase Connection Issues

WhatsApp Automation Issues

Messages Not Sending

Screenshots Not Sending

Bot Behavior Issues

Bot Stops Unexpectedly

Not Finding Items to Buy

Buying But Not Selling

Performance Issues

Bot Running Too Slowly

High CPU/Memory Usage

Security & Ban Prevention

Account Banned or Flagged

Advanced Troubleshooting

Enable Debug Logging

Check Selenium Driver Version

Remote Debugging Not Releasing Ports

Getting Help