app.bettersight.io/z_starting_files/brightdata_proxy_ca/New SSL certifcate - MUST B...
JasonFraser ad1d7f1815 Fix critical scrape-targeting bug and harden proxy, matching, and dashboard reliability
The highest-impact fix: run_research_job() only ever read entry['id'] from
confirmed competitors, silently discarding the Firecrawl-matched or
manually-swapped URL — every scrape fell back to the competitor's bare
root domain regardless of what was confirmed. This explains most of the
"unpredictable/wrong data" behavior seen against the old app.py. Threaded
confirmed_url through jobs.py -> analysis_service.py so the actually
confirmed page is what gets scraped.

Other fixes bundled in this pass:
- Proxy layer: Webshare rotating-gateway country code lowercased (was
  silently failing auth), Bright Data port corrected to 33335 (current
  cert), dedicated-IP candidate rotation added before falling back to the
  shared gateway/Bright Data escalation.
- Trip-intent matching: score_and_rank_urls() now hard-gates on
  destination keyword and excludes bare root-domain candidates, instead
  of letting duration/category signals alone push a wrong-country or
  homepage URL over the confidence threshold.
- force_refresh cache-bypass toggle added (opt-in, collapsed "Advanced
  options"), plus a "Skip this competitor" affordance for unmatched URLs.
- De-hardcoded "G Adventures" (the hackathon reference client) out of the
  extraction prompt — now uses the real tenant's company name.
- RunHistory/Apps-Script "latest results" queries filtered to
  triggered_by = "manual" so per-competitor content-hash bookkeeping rows
  no longer drown out real batch runs.
- Dashboard fixes: stuck-state bug on revisiting the Analyse page,
  AccountPage/BattlecardsPage restacked to single-column layout, Alerts
  moved to a header bell dropdown, invisible Export/Run Analysis icons
  (fill -> stroke), tour popup width mismatch, horizontal-scroll bug on
  cards (missing min-width: 0 in flex layout).
- New PocketBase migrations for scrape_runs (content_hash fields,
  tab_type, created_by_email) and products (departures, start_days).

335 backend tests passing.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-04 17:33:05 -04:00
..
BrightData SSL certificate (port 33335).crt Fix critical scrape-targeting bug and harden proxy, matching, and dashboard reliability 2026-07-04 17:33:05 -04:00
BrightData_SSL_Certificate_Installer_signed.exe Fix critical scrape-targeting bug and harden proxy, matching, and dashboard reliability 2026-07-04 17:33:05 -04:00
README.txt Fix critical scrape-targeting bug and harden proxy, matching, and dashboard reliability 2026-07-04 17:33:05 -04:00

README.txt

This is the *new* SSL certificate, effective from September 2024. Please use this certificate for all new projects and avoid using the previous certificate.

IMPORTANT: to use this certificate, you must use port 33335 when connecting to Bright Data's proxy network, even if documentation and sample codes provided mention port 22225. Documentation will gradually be updated to port 33335 as the old certificate is being phased out.

You have a few options to use this certificate:

- If you write code, you can simply load it into your existing code.
- If you are using Windows and third-party tools that allow you to configure proxy settings (like AdsPower, Proxifier, Multilogin, Undetectable etc.) you can install the certificate on your computer using the installer.

Again, remember: you MUST use port 33335 when connecting to Bright Data's proxy network, even if documentation and sample codes provided mention port 22225. 

Full information regarding how to use the SSL certificate is available on https://docs.brightdata.com/general/account/ssl-certificate