{"schema_version":"1.2","total":4,"limit":30,"offset":0,"filters":{"category":"diagnostic"},"tools":[{"slug":"bright-data-proxy-connection-test","name":"Bright Data: proxy connection test failures","category":"diagnostic","provider_slug":"bright-data","publisher":"Bright Data","publisher_type":"official","website":"https://docs.brightdata.com/integrations/playwright","summary":"Check the diagnostic target and product access when a tool reports a Bright Data proxy error.","tools":["playwright"],"capabilities":["error-handling"],"outputs":["Diagnostic guidance"],"connection":"proxy","billing_basis":"Charges depend on the enabled proxy product; this is a setup diagnostic.","facts":[{"label":"Test target","value":"The guide recommends https://geo.brdtest.com/welcome.txt for connectivity checks.","source_ids":["docs"]},{"label":"Search-engine tests","value":"A tool using a search engine as its default test target can report an error because that target requires the SERP API.","source_ids":["docs"]},{"label":"Residential access","value":"The guide requires an approved business KYC check for residential proxy access.","source_ids":["docs"]}],"setup":["Check the tool's proxy-test URL and use the documented diagnostic endpoint.","Confirm the enabled product and access requirements in the account dashboard."],"limitations":["This checks documented setup requirements; no live connection was tested."],"sources":[{"id":"docs","label":"Bright Data Playwright integration prerequisites and connectivity checks","url":"https://docs.brightdata.com/integrations/playwright","checked_at":"2026-09-27"}],"checked_at":"2026-09-27","review_due":"2026-10-27","evidence":"documented","url":"https://workingproxysites.info/tools/bright-data-proxy-connection-test","provider_url":"https://workingproxysites.info/t/1-bright-data-proxies","review_overdue":false},{"slug":"browserbase-tunnel-connection-failed","name":"Browserbase: tunnel connection failed","category":"diagnostic","provider_slug":null,"publisher":"Browserbase","publisher_type":"official","website":"https://docs.browserbase.com/platform/identity/proxies","summary":"Check location selection and proxy connectivity when a Browserbase session reports ERR_TUNNEL_CONNECTION_FAILED.","tools":["playwright","puppeteer"],"capabilities":["error-handling"],"outputs":["Diagnostic guidance"],"connection":"cdp","billing_basis":"Browserbase plan and proxy usage charges apply; this reference does not estimate retry costs.","facts":[{"label":"Possible causes","value":"The documentation lists an unsupported site, unsupported city or temporary proxy issue.","source_ids":["docs"]},{"label":"Location check","value":"Retry without city targeting or choose another city.","source_ids":["docs"]},{"label":"Custom proxy check","value":"Custom proxy connectivity is validated when the session is created; unreachable endpoints or incorrect credentials can fail creation.","source_ids":["docs"]}],"setup":["Check the requested location and proxy configuration.","For a temporary issue, retry the session; consult the source for site restrictions."],"limitations":["The error alone cannot establish which cause applies."],"sources":[{"id":"docs","label":"Browserbase proxy troubleshooting and custom proxies","url":"https://docs.browserbase.com/platform/identity/proxies","checked_at":"2026-09-27"}],"checked_at":"2026-09-27","review_due":"2026-10-27","evidence":"documented","url":"https://workingproxysites.info/tools/browserbase-tunnel-connection-failed","provider_url":null,"review_overdue":false},{"slug":"http-407-proxy-authentication","name":"HTTP 407: proxy authentication","category":"diagnostic","provider_slug":null,"publisher":"IETF","publisher_type":"official","website":"https://www.rfc-editor.org/rfc/rfc9110.html#name-407-proxy-authentication-req","summary":"Identify a proxy authentication challenge and check the credentials sent to the proxy.","tools":[],"capabilities":["error-handling"],"outputs":["Diagnostic guidance"],"connection":"proxy","billing_basis":"Protocol reference; request charges depend on your provider.","facts":[{"label":"Meaning","value":"The proxy needs valid authentication credentials.","source_ids":["docs"]},{"label":"Challenge","value":"The response supplies a Proxy-Authenticate challenge.","source_ids":["docs"]},{"label":"Client response","value":"The client can retry with an appropriate Proxy-Authorization header.","source_ids":["docs"]}],"setup":["Inspect the proxy's authentication challenge.","Configure the proxy credentials in your client's proxy settings, then retry."],"limitations":["A 407 identifies an authentication problem, not its account-specific cause."],"sources":[{"id":"docs","label":"HTTP Semantics: 407 Proxy Authentication Required","url":"https://www.rfc-editor.org/rfc/rfc9110.html#name-407-proxy-authentication-req","checked_at":"2026-09-27"}],"checked_at":"2026-09-27","review_due":"2026-10-27","evidence":"documented","url":"https://workingproxysites.info/tools/http-407-proxy-authentication","provider_url":null,"review_overdue":false},{"slug":"zyte-api-response-errors","name":"Zyte API: response status and rate limits","category":"diagnostic","provider_slug":"zyte","publisher":"Zyte","publisher_type":"official","website":"https://docs.zyte.com/zyte-api/usage/errors.html","summary":"Separate the API response status from the target website's status and browser-action results.","tools":["python-requests","scrapy"],"capabilities":["error-handling"],"outputs":["Diagnostic guidance"],"connection":"http-api","billing_basis":"Zyte documents rate-limited and unsuccessful API responses as uncharged; a successful API response can still contain a target error.","facts":[{"label":"Two status layers","value":"An API HTTP 200 can carry a target website statusCode of 404.","source_ids":["docs"]},{"label":"Browser actions","value":"An unsuccessful action does not necessarily fail the API request; inspect the actions field.","source_ids":["docs"]},{"label":"Rate limits","value":"API HTTP 429 or 503 can indicate rate limiting. Inspect the response type to determine the limit.","source_ids":["docs"]}],"setup":["Inspect the HTTP response and JSON error type.","Check statusCode and action outcomes before treating returned data as usable."],"limitations":["Successful transport does not establish that the requested extraction meets your requirements."],"sources":[{"id":"docs","label":"Zyte API error handling","url":"https://docs.zyte.com/zyte-api/usage/errors.html","checked_at":"2026-09-27"}],"checked_at":"2026-09-27","review_due":"2026-10-27","evidence":"documented","url":"https://workingproxysites.info/tools/zyte-api-response-errors","provider_url":"https://workingproxysites.info/t/165-zyte-proxies","review_overdue":false}]}