Skip to main content

Troubleshooting

When working with Aluvia proxies, you may encounter errors such as 403 Forbidden, Captchas, or connection issues. This guide lists the most common issues, their meaning, and exact fixes.

Common Error Codes & Fixes​

403 Forbidden​

What it means:
The target site rejected your request. Common causes include:

  • Invalid proxy credentials
  • Expired or inactive session
  • Request blocked due to missing headers or suspicious behavior

Fixes:

  • Re-check your proxy username and password in the Aluvia dashboard.
  • Regenerate proxy credentials if necessary.
  • Add a User-Agent header to mimic a real browser.
  • Use sticky sessions for login/session-based workflows.
  • Rotate IPs if the same one gets blocked.

407 Proxy Authentication Required​

What it means:
Your proxy credentials were not accepted by Aluvia.

Fixes:

  • Ensure you are passing username and password correctly.
  • Verify no spaces or typos in your credentials.
  • Test using curl:
curl -x http://username:password@us-mobile-proxy.aluvia.io:10000 https://ifconfig.me

429 Too Many Requests​

What it means:
Too many requests from the same IP or too quickly.

Fixes:

  • Reduce request frequency (add delays).
  • Rotate IPs more frequently.
  • For automation tasks, spread requests over time.

502 Bad Gateway / 503 Service Unavailable​

What it means:
The proxy server or the target website is temporarily unavailable.

Fixes:

  • Retry after a short delay.
  • Check the Aluvia status page (if provided).
  • Use backup proxies for failover.
  • Verify your network connection.

Captchas​

What it means:
The target website detected automation.

Fixes:

  • Rotate proxies more frequently.
  • Add headers (User-Agent, Accept-Language, etc.).
  • Use browser automation tools (Playwright, Puppeteer).
  • Add human-like delays between actions.
  • Avoid scraping login-protected areas unless necessary.

Aluvia-Specific Issues​

Invalid Proxy Credentials​

What it means:
The proxy username or password is incorrect.

Fixes:

  • Verify your credentials in the Aluvia Dashboard under “Proxy Settings”.
  • Generate a new set if necessary.

Session Expired​

What it means:
Your proxy session has timed out.

Fixes:

  • Generate fresh credentials before starting a new job.
  • Use sticky sessions only if you need persistence (e.g., logging in).
  • For large workloads, rotate credentials periodically.

Connection Timed Out​

What it means:
Your proxy session has timed out.

Fixes:

  • Verify you are using the correct hostname (us-mobile-proxy.aluvia.io) and port (10000).
  • Test connectivity with curl.
  • Switch to a different Aluvia proxy region if supported.

What it means:
You don’t have enough data balance to continue making requests.

Fixes:

  • Top up your account via the Billing & Top Ups menu.
  • Check your Usage Statistics to confirm consumption.
  • Enable alerts if your usage is nearing the limit.

Blocked by Target Website​

What it means:
Even though the proxy works, the target site is actively blocking the request.

Fixes:

  • Use Aluvia Intelligence Hostnames to get more trusted routes.
  • Rotate proxies frequently.
  • Randomize headers and request intervals.

Best Practices to Avoid Errors​

  • Always send a User-Agent header.
  • Add random delays between requests.
  • Use sticky sessions only when needed (logins).
  • Rotate IPs to avoid bans.
  • Monitor Usage Statistics in your dashboard to stay within limits.
  • For persistent problems, contact Aluvia Support with:
    • Error code
    • Request headers
    • Proxy credentials (masked)
    • Timestamp of issue