> ## Documentation Index
> Fetch the complete documentation index at: https://www.octoparse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot access and blocking

> Diagnose common Octoparse access failures with evidence, targeted fixes, and data validation.

When a task cannot open a website or returns incomplete data, diagnose the page before changing settings. Capture the final URL, error text, screenshot, time, task environment, and several output rows. That evidence separates access failures from task-design or data-quality issues.

## Diagnose the issue

| Symptom                              | Likely checks                                    | First targeted action                                                    |
| ------------------------------------ | ------------------------------------------------ | ------------------------------------------------------------------------ |
| 403 or 429                           | IP path, request frequency, target rules         | Test a smaller run; then review [proxies](/docs/en/platform/proxy) and pacing |
| Blank or incomplete page             | Browser mode, JavaScript loading, wait condition | Add a targeted wait and validate the rendered page                       |
| Login reappears                      | Cookie state, session expiry, IP change          | Rebuild and test the permitted session                                   |
| CAPTCHA repeats                      | Challenge type, environment, retry behavior      | Use the supported manual or automatic path; avoid unbounded retries      |
| Cloudflare page persists             | Supported verification setting and final page    | Run a small controlled verification test                                 |
| Local and Cloud differ               | Location, session, browser mode, screenshot      | Compare one representative test in each environment                      |
| Data is missing after the page loads | Field selection, pagination, page state          | Verify several rows and the actual final page                            |

## Test one change at a time

1. Reproduce the issue with a small, representative scope.
2. Identify the first unexpected page state or failed action.
3. Change one relevant setting only.
4. Re-test the same scope and compare screenshot, final URL, fields, and record count.
5. Keep the change only when the result is reproducible; otherwise revert it and inspect the next likely cause.

## When to stop and contact support

Stop the run when a small, controlled test still returns an access, CAPTCHA, or login page. Also stop when retries add cost but do not return valid data.

When you contact Support, include:

* Whether the run was Local or Cloud, and when it ran
* The target URL and error message
* A screenshot and the relevant event-log excerpt, with secrets removed
* What you expected to happen and what happened instead