Distill.io Not Working on Jio Network: Website Monitoring Fixes

If Distill.io is not working on a Jio network, start with the monitor’s Check Log and note the exact error. A failed check alone does not show that Jio is blocking Distill: the cause could be the target website, the check environment, authentication, the monitor URL, or a network path. Then compare a local check with a cloud check and follow the branch for the error you actually see.

Distill monitors website changes using checks that can run on your own device or in Distill’s cloud. Local checks need the browser or app to be open; cloud checks run on Distill’s servers. That difference helps narrow down where a failure occurs, but it does not by itself prove Jio is responsible. Distill’s troubleshooting documentation describes the errors and their possible causes.

1. Read the Check Log before changing anything

1. Open the affected monitor in Distill and view its Check Log.
2. Record the latest error name and any details shown, along with the time of the check.
3. Note whether this monitor uses a local or cloud check.
4. Check whether the page opens normally in a browser using the same connection. If possible, compare with another connection, such as a different Wi-Fi network or mobile data. This is a comparison, not proof of the cause.
5. Use the error-specific guidance below. Avoid changing DNS, proxy, or security settings at random: different errors point to different parts of the request path.

Distill says the last check determines the monitor’s state. The error is therefore more useful than the general observation that monitoring stopped.

2. Compare local and cloud checks

When available for the monitor, compare its behavior using local and cloud checks. Keep the target URL and other monitor settings the same while comparing, so the execution location is the main difference.

What you observe	What it suggests	What to do next
Local works, cloud fails	The target may respond differently to Distill’s cloud environment. Distill lists rejection of some IP addresses as one possible cause of cloud timeouts.	Check the logged error. If it is a timeout and the target is appropriate to access through a proxy, review Distill’s proxy option. A proxy can also fail.
Cloud works, local fails	The issue may involve the local device, browser or app state, background-tab behavior, or the local network path.	Keep the browser or app open for local checks, bring the page into the foreground if relevant, and check whether ordinary browsing on that device works.
Both fail with the same target	The URL, target website, authentication, or a shared setting may be involved.	Check the URL and the target’s access requirements, then use the exact error branch below.
Other internet use fails too	This points to a broader connection, router, or service issue, though it does not identify which one.	Use Jio’s official diagnostics for the connection type and location.

Local and cloud checks are different execution paths, not a definitive network test. A result can help narrow the investigation, but the Check Log and connection behavior still matter.

3. Fix the error shown in the log

E_NOT_FOUND: domain cannot be resolved or URL is invalid

• Open the monitor settings and verify the complete URL, including the domain and path.
• Check for a typo, an outdated hostname, or a URL that redirects to a different site.
• Try opening the same address in a browser. If the hostname itself does not resolve there either, investigate the target domain or general connectivity.

Distill describes this error as an invalid or unresolvable domain. It is not, by itself, evidence that Jio blocks Distill. Do not assume that changing DNS is a guaranteed fix.

E_CONNRESET: connection was reset

• Check whether the target site is reachable in a browser at the time of the failure.
• Look at whether the reset occurs only on local checks, only on cloud checks, or on both.
• If it is intermittent, review later Check Log entries before making persistent changes. A reset can relate to the server or network path.

If the page loads in a browser but repeated checks reset, use the local-versus-cloud comparison and check whether the site has access restrictions or behaves differently for automated requests. The error alone does not identify which network component reset the connection.

E_TIMEOUT: page contents did not load in time

• Confirm whether the target is slow or unavailable in a browser at the time of the check.
• Compare local and cloud execution. Distill lists slow responses, rejection of some cloud IP addresses, and local background-tab loading limitations among possible causes.
• For a local check, keep the browser or app open; if background loading is the issue, test with the page active.
• For a cloud check, a proxy may help in relevant cases. Follow Distill’s documentation for configuring it, and remember that the proxy itself may be blocked or unable to connect.
• For a webpage monitor in a relevant dynamic-page case, Distill documents setting its dynamic option to true. Apply that only when it matches the monitor and error context.

A timeout means the check did not load page contents in time; it does not establish that the connection provider is the cause. Avoid increasing waits or adding a proxy without checking which execution path failed.

E_REQUEST_FORBIDDEN: target refused or restricted access

• Check whether the page requires login, cookies, or another authenticated session.
• Verify that the monitor is configured with the required authentication where supported.
• Consider whether the target has a firewall or security setting that restricts the check environment.
• Distill suggests a proxy for some protected pages, but a proxy is not a way to guarantee access or bypass a site’s controls. Use only access you are authorized to use.

If the page opens for you in a normal browser but returns this error to a check, compare its authentication and access conditions with the check’s environment.

E_PROXY: selected proxy cannot connect

• Confirm that a proxy is configured for this monitor and that its connection details are correct.
• Check whether the proxy can reach the target and whether the target blocks that proxy’s IP address or location.
• If a proxy is necessary, try another permitted proxy endpoint according to Distill’s setup instructions. If it is not necessary, remove the proxy and compare the check again.

This error is about the configured proxy path. Changing Jio settings will not repair a proxy that cannot reach the target.

4. Check Jio connectivity when other sites fail too

If ordinary browsing or multiple unrelated services are also failing, check the connection independently of Distill. Jio’s FAQ directs users to the Run Diagnostics flow in the MyJio app for issues involving internet connectivity inside the home, router connection or health, and an existing outage. See Jio’s connectivity troubleshooting FAQ and its support portal.

1. Open MyJio and use Run Diagnostics for the relevant Jio service.
2. Follow the app’s findings for connectivity, router health, or a reported outage.
3. After the connection is stable, run the Distill monitor again and inspect its new Check Log entry.
4. If the issue is limited to Distill checks, return to the error-specific steps rather than treating it as a general Jio outage.

Use the support route that matches your service. The available information does not confirm a Jio-wide Distill block or a specific Jio-Distill compatibility defect.

5. Gather useful details if it still fails

Before contacting Distill or Jio support, collect details that distinguish the check path from the connection path:

• The exact error code and text from the latest Check Log entry.
• Whether the monitor uses local or cloud checks, and the result of comparing them.
• Whether the connection is Jio mobile data or JioFiber.
• Whether the target URL opens in a browser on the same connection.
• Whether unrelated websites or apps also fail.
• Whether the target requires login, cookies, or access through a proxy.
• The time the error occurred and whether later checks behave differently.

These details help route the problem. Without the exact error, access type, and check location, the individual cause cannot be identified reliably.

Common troubleshooting mistakes

• Assuming Jio is blocking Distill: A failed check does not establish that. First identify the error and compare local with cloud checks.
• Treating every failure as DNS: E_NOT_FOUND concerns an invalid or unresolvable domain; timeouts, resets, forbidden responses, and proxy errors have different explanations.
• Changing multiple settings at once: If the check starts working, it will be hard to know which change mattered. Change one relevant setting, then review the next log entry.
• Using a proxy as a universal fix: Distill documents proxies for some situations, but the proxy can fail or be blocked, and it does not guarantee access to a protected page.
• Comparing checks while also changing the target URL: Keep the URL and monitor settings stable when comparing local and cloud behavior.

Performance, reliability, and cost considerations

When a monitor times out, first decide whether the delay is in the target response or in the check environment. A page that loads slowly can miss a check’s available loading time; local background-tab behavior and cloud IP rejection are separate possibilities. Prefer the smallest relevant configuration change and watch subsequent Check Log entries for a repeatable result.

For reliability, note whether failures are consistent or intermittent, whether they affect one monitor or several, and whether local and cloud checks differ. The sources reviewed do not establish a Jio-specific outage, provide a Jio-Distill success rate, or identify a universal timing setting. Avoid treating an isolated failure as a confirmed service-wide issue.

No physical product is established as necessary for this software and network-path troubleshooting. Start with the monitor log and Jio’s diagnostics when connectivity broadly fails.

Or skip the browser setup

If your goal is to capture a page as an image or PDF while diagnosing how it renders, ScreenshotNeo is a website screenshot API and MCP server. Its one-call API returns a screenshot or PDF, with options for waiting, page capture, and browser configuration. See the ScreenshotNeo API documentation.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);

• Cookie and consent banners, newsletter popups, and chat widgets are removed before capture; each step can be turned off.
• Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed; responses say the page verdict and billing status.
• An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents.
• The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots. Every feature is on every plan.

Sign up free for 1,000 screenshots a month, no card required.

FAQ

Is Distill.io confirmed to be blocked on Jio?

No Jio-specific Distill block or compatibility issue is confirmed in the sources reviewed. Diagnose the exact error and check path before drawing that conclusion.

Should I switch DNS to fix Distill?

Not as a blanket remedy. Check the URL and domain for E_NOT_FOUND; other codes point to different issues.

Does a cloud check mean my Jio connection is irrelevant?

A cloud check runs on Distill’s servers, so it is a different path from a local check on your device. Comparing the two is useful evidence, but it does not establish the cause on its own.

What details should I include in a support request?

Include the exact Check Log error, local or cloud mode, Jio mobile data or JioFiber, whether the target opens in a browser, and whether other internet use fails.